Email & notifications

Receipts and notifications: how a form overrides the workspace's email settings, what a new form starts with, the placeholders you can use, and how delivery is tracked.

Receipt emails and notification rules

Customise the receipt email sent to buyers and per-form notification rules. Email settings are configured per workspace, and any form can override them (subject, body, receipt on/off, merchant notify) with a “use workspace default” option — resolution order is form → workspace → built-in default.

Every new form also starts with a default notification to you: a payment form notifies on sale.paid, a response form on response.submitted (its message uses the responder's name and email, because a response has no sale).

Dynamic placeholders

The subject and body support dynamic placeholders — {{ref_code}}, {{amount}}, {{items}}, {{buyer_name}}, {{form_url}}, {{date}} and any {{field_id}} — replaced with the real value for that sale or submission when the email is sent. The Placeholders reference lists every one, including the {admin_email} recipient token and the placeholders that carry no value on a response form.

Delivery tracking

Track delivery for every message: sent → delivered → opened → clicked. The status is per email, so a receipt that never arrived can be told apart from one that was never sent.

Addresses that should never be mailed are held on the platform's suppression list — see the email suppression list page for what gets on it and how an address comes off.

Related: the placeholders reference, the email suppression list and the MCP tool reference for the email settings tools.