Sending mail from the app
Sign-up confirmations, receipts, and a note to yourself. The server decides who receives it.
What it is for
Three kinds of mail cover almost everything: confirm this address, here is your receipt, someone just ordered.
Each one is a template you register once. The app fills in the values.
Splitting them into mail that goes to the customer and mail that comes to you makes the list easy to write.
What you need
A Resend account, a sending domain you have verified, and the API key saved in Project secrets.
Verifying the domain is done with your DNS provider. Without it, mail from your address is treated as suspicious.
- A sending address on your own domain
- One template per purpose — sign-up confirmation, receipt, order notice
- One API key from Resend
The order to do it in
Verify the domain first, then register the templates, then wire them to events in the app.
Verification can take a day or two, so start it before you build the screens.
A message may be scheduled for later and cancelled before it goes.
How to check it worked
Every message carries a status: queued, accepted, delivered, bounced, complained, suppressed, failed.
A bounce usually means the address was wrong or the domain is not fully verified yet.
The recipient address is never kept in readable form next to the record.
What it will not do
- The recipient is either a fixed address or the person currently signed in. The browser cannot name a third one.
- Free text is not sent. Only registered templates with filled-in values.
- Up to 200 notifications per project per day.
- It is not a newsletter tool. For a mailing list, use a service built for that.