Emails from your app that actually arrive.
Email your app sends as itself (receipts, sign-in links, notifications) from its own sending domain.
Part of a Solution. Built, released and secured together with the rest of your app: one place, one release.
What it does
What you get with Transactional Email
Sends as your brand
Each app sends from its own domain, not a shared address.
Reputation kept separate
One app’s sending never affects another’s deliverability.
Built to reach the inbox
Guided DKIM setup and verification for every sending domain.
Every message tracked
Delivery status for each send, from your app or an Ambassador.
Use cases
What people build with it
Receipts and invoices
Sent the moment the order completes, from your app’s own domain.
Sign-in links
Magic links and codes for your app’s users, from an address they recognise.
Notifications from an Ambassador
A scheduled function emails the weekly summary and records whether it was delivered.
The technical detail
Commands, limits and step-by-step setup for Transactional Email live on the Docs site.
Read the docsQuestions
Can I send marketing campaigns with it?
No. Transactional Email is for messages your app sends because a user did something: receipts, sign-in links, notifications. Campaigns belong in Journeys, so that unsubscribing from marketing never stops a receipt arriving.
Why does each app send from its own domain?
So reputation is kept separate. One app’s sending can never affect another app’s deliverability.