Skip to main content
Apps that need to email their users get real transactional sending: welcome messages, booking confirmations, password-adjacent notifications, receipts. Each project sends from its own platform-managed address by default, with the authentication records (DKIM/SPF) that keep mail out of spam folders handled for you.

What your app can do

  • Send one-off transactional emails (HTML and plain-text bodies), with an optional reply-to address.
  • Check its own sending health — how much was sent recently and whether anything bounced.
  • Verify a custom sending domain: if you want mail to come from hello@yourcompany.com, the platform gives you a short list of DNS records to add at your domain registrar; once they propagate (usually minutes), verification completes automatically.

Sending starts restricted — by design

New projects send in a restricted mode: modest daily volume, suitable for development and early testing. This is standard email-infrastructure practice — sending reputation is earned. When your app is ready for full production volume, contact support to have production sending enabled for your project.

Good to know

  • This is transactional email — messages triggered by something a user did. It is not a bulk-campaign tool; connect a dedicated marketing platform for newsletters and campaigns.
  • Bounced addresses are automatically suppressed by the mail infrastructure; repeatedly re-sending to a bounced address damages deliverability, so the agent won’t do it.
  • Sign-up confirmation and password-reset emails for your app’s authentication are delivered by the identity provider itself — they work without any email capability configured.