Transactional email overview
Transactional emails are one-to-one emails triggered by something happening: an order confirmation, a password reset, a double opt-in confirmation. They are not marketing. SmartMailing treats them as a separate system with its own sending stream, its own rules, and its own pages in the dashboard.
Default transactional emails
Every brand can generate a default set of brand-styled lifecycle emails that the platform sends automatically. There are three:
Custom events
An event is a named transactional email of your own, like an order confirmation or a booking reminder. You build the email once in the normal email builder, then wrap it in an event with a key like order_confirmation. From then on, your app or a trigger sends it by that key.
Send with the API
If you have a developer, the send API is the direct way to fire a custom event from your website or app. This page is the one place in these docs written for that developer.
Triggers and the send log
A trigger is a webhook URL that sends one of your custom events without any code on your side. You paste the URL into an outside tool (Stripe, Shopify, Zapier, or your own system). When that tool POSTs a payload to the URL, SmartMailing reads the recipient and the variables out of it using a mapping you set up once, with clicks.