Post-Purchase Actions
Post-purchase actions run automatically when a payment has been confirmed. They can send a receipt, activate a course on Kajabi or Systeme.io, send a webhook to an external system, or send a customisable email to the customer.
Where Actions Can Be Configured
Actions are defined at three levels:
- Product — actions run whenever the product is included in an order
- Offer — actions run when an order is placed through this offer
- Checkout — actions run on all orders in the checkout
The same order can have actions from all three levels at once.
Action Types
Send Receipt by Email
Sends the customer an order confirmation by email. No additional settings required — the receipt is generated automatically from the order data.
Available at the checkout level.
A receipt is only sent if this action is active in the checkout's post-purchase actions. The action is added automatically when a new checkout is created, but it is not enabled by default — remember to activate it in the checkout settings.
Grant Kajabi Offer
Activates a Kajabi Offer for the customer by sending the customer's details to the offer's webhook URL.
Available at the product, offer, and checkout levels.
| Asetus | Kuvaus |
|---|---|
| Name | Internal name for the action. Only visible in the dashboard. |
| Webhook URL | The Kajabi integration webhook URL, found in the Kajabi dashboard. |
| Send offer grant email | When enabled, Kajabi sends the customer an email confirming the offer has been activated. |
| Hide last name | When enabled, only the first letter of the customer's last name is sent to Kajabi. Useful if customers interact in the Kajabi community and may not realise their full name is visible to others. |
Kajabi must be enabled in Settings → Integrations → Course Platforms before this action is available.
For detailed setup instructions, see: Kajabi Integration
Grant Systeme.io Access
Adds the customer as a contact in Systeme.io and applies one or more tags, triggering your Systeme.io automations to activate the course.
Available at the product, offer, and checkout levels.
| Asetus | Kuvaus |
|---|---|
| Name | Internal name for the action. Only visible in the dashboard. |
| Tags | The Systeme.io tags to add to the customer's contact after purchase. Each tag can trigger a separate automation. |
Systeme.io must be enabled with an API key in Settings → Integrations → Course Platforms before this action is available.
For detailed setup instructions, see: Systeme.io Integration
Webhook
Sends an HTTP POST request to a URL of your choice with the order data. Suitable for CRM systems, automation tools, or your own backend.
Available at the product, offer, and checkout levels.
| Asetus | Kuvaus |
|---|---|
| Name | Internal name for the action. Only visible in the dashboard. |
| URL | The endpoint to send the webhook request to. |
| Secret | An HMAC signing key you can use to verify the authenticity of incoming requests. Generated automatically. |
Send Email
Sends a customisable email to the customer after purchase.
Available at the product, offer, and checkout levels.
The subject and content are configured separately for each language supported by the checkout.
| Asetus | Kuvaus |
|---|---|
| Name | Internal name for the action. Only visible in the dashboard. |
| Subject | The email's subject line. |
| Email content | The email body, built from image, rich-text, and banner blocks. |
If the order's language has no configured content, the email is sent using the checkout's first supported language. If that language also has no content, the email is skipped and the action is still marked Succeeded — make sure every supported language has a subject and body to avoid silent skips.
Action Status
The execution status of each action is visible in the order details in the dashboard. Possible statuses:
- Pending — the action has not yet been executed
- Running — the action is currently being executed
- Succeeded — the action completed successfully
- Failed — the action execution failed
Re-running Individual Actions
Each action row in the order sheet has a re-run button. This lets you re-trigger a single action without touching the others — useful when a customer needs the receipt resent, or when a single integration call failed and you want to retry it after fixing the configuration.
Open an order, expand the Post-purchase Actions section, and click the re-run icon next to the action you want to fire again. A dialog will appear summarising what is about to happen.
Use Latest Template
The dialog has a Use latest template option. When enabled, the action's stored snapshot is replaced with the current template configuration before re-running. This is the right choice when you fixed a setting (e.g. the Kajabi offer URL or a webhook endpoint) and want the re-run to use the new value.
When disabled, the action runs with the configuration that was captured at the time of the original purchase.
Replacing the snapshot is permanent — the previous configuration is overwritten and cannot be recovered.
Re-running a Successful Action
You can also re-run actions that already succeeded. The dialog shows a warning when this is the case, because the action's side effects will fire again — for example, the customer will receive a second receipt email or your webhook endpoint will be called again. Use this when a customer asks for the receipt to be resent, or when downstream systems lost the original delivery.
Force Re-run
If an action is stuck in the Running state — typically because the previous run crashed mid-execution and never recorded a final outcome — the re-run button changes to a Force re-run affordance with a stronger warning. Force re-run bypasses the in-progress safeguard. Use it only when you are confident the previous run is no longer active, since two simultaneous executions could produce duplicate side effects.
Re-running an action does not change the order's status by itself, but if the re-run was the last failing piece, the order will automatically transition to Completed.