Sending emails from your app

Add operational emails with the shared sender, or connect your own provider for marketing and custom sender addresses.

Ask the builder to add operational emails such as sign-up confirmations, order receipts or contact-form notifications. The shared sender needs no separate provider account and defaults to 100 emails per day per workspace.

For example: “Email me when someone submits the contact form.” Test the result with your own address before enabling it for customers.

See what your app sends

Open Dashboard → Emails in the editor. It lists every email your app sends by itself, what triggers each one, and the address it is sent from. Click an email to read it. An email that isn't on your published app yet says Sends once you publish.

The list is read from your app. It doesn't show what has been sent. When a build adds or changes an email, the finished build in the chat names it; click the name to open that email.

To add one, click Ask for an email. To change one, open it and click Change this email. Both write the request into the chat for you to send.

Sender address and replies

Shared-sender emails use an allowed address such as [email protected]. The server helper accepts a replyTo address and a display name in from, but the underlying address must still be allowed.

The built-in custom-domain path requires bare email addresses and rejects display names. For a branded sender name on that path, connect a provider that supports it.

Ask the builder which sending path your app uses. Send a test to yourself and reply to check both destinations.

Use your own provider

Connect your own Resend, SendGrid or Postmark account and verify your domain there. Then ask the builder to use the verified sender, such as [email protected].

See Sending from your own domain, or Connecting another email provider.

Birthday greetings and marketing

Birthday and anniversary greetings are marketing, even without a discount. Use your own provider's marketing or broadcast setup and follow its subscription, unsubscribe and sending-limit rules.

Do not use the shared transactional sender for campaigns. Its allowance is shared across the workspace and is needed for operational messages. Scheduling a message does not make it transactional.

For example, Postmark uses Broadcast Message Streams for marketing.

Test and schedule emails

Preview sends real emails and uses the same daily allowance. Use your own recipient address; check spam if a test does not arrive.

For reminders or summaries, see Scheduling emails. Password resets and sign-in emails are handled by the app's sign-in flow.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Integrations

Why was my email sending paused or throttled?

Why an email from your app was refused — the shared sender's daily cap, an unverified sender address, or a platform-wide limit — and how to fix each one.

Scheduling automatic updates

Make your app do something on a schedule — every hour, every Monday, the 1st of the month. Without anyone clicking anything.

Understanding your email sending limits

How email sending limits work — the built-in shared sender's daily cap, when it resets, and how to send more through your own provider.

Still need help?

If this didn't answer your question, our team is one click away.