Waymaker
Waymaker Host

Transactional Email

Learn about Transactional Email in WaymakerOS.

EmailSendingDNS

Your app sends its own email: receipts, password resets, a weekly report. Each app sends from its own address, and each send is charged in credits to the Solution that owns the app.

Every app gets an address that works straight away

You don't need to set up DNS. The first time an app sends, Waymaker gives it a ready-made address:

noreply@{your-app}.{your-organization}.waymakermail.com

Waymaker owns that domain and looks after its records, so there is nothing for you or your IT team to publish. The email shows your app's name as the sender, and you can change the part before the @ on each send, for example receipts@… or bookings@….

To see the address before the first send:

  1. Open Host → Tools → Transactional Email
  2. Click Set up address
  3. Choose the app, leave the domain blank, and click Show ready-made address

Host shows the address the app will use. Nothing is set up until the app's first send: then it appears as Ready-made · no DNS and is verified within a minute or two.

Optional: send from your own domain

If you'd rather mail came from your own domain (for example mail.yourcompany.com):

  1. Click Set up address, choose the app, and enter your domain
  2. Waymaker shows you a few CNAME records. Add them at your DNS provider, or send them to whoever manages your DNS.
  3. Click Verify. DNS changes can take anything from a few minutes to a few hours to be seen.

Every record you're asked to add is a CNAME that points to a Waymaker hostname. You never publish keys or third-party values, and if anything needs to change later, Waymaker changes it on its side.

Use a subdomain you don't already use for email (such as mail. or appmail.), so these records can't clash with the mail your staff send.

One address per app. Each app sends only from its own address, so one app's sending history can't affect another's.

Limits that protect your address

  • A new address starts gently. It can send 100 emails on its first day, and the daily limit doubles each day up to 10,000. Mailbox providers trust a new address more when its volume grows steadily, which keeps your mail out of spam folders.
  • Transactional email only. Receipts, notifications and account email that someone expects. Newsletters and marketing go through Journeys, where people can unsubscribe.
  • People who bounce or complain are not mailed again. If an address doesn't exist (a hard bounce) or the person marks your app's mail as spam, your app stops sending to that address. The attempt is recorded, nothing is sent, and nothing is charged.
  • Automatic pause. If too much of an app's mail bounces or is marked as spam, Waymaker pauses that app's sending, so one app can't damage delivery for everyone else. The limits are 4% hard bounces or 0.1% spam complaints over 7 days, once at least 100 messages have gone. The organization owner and Waymaker are both emailed when it happens.
  • Paused sending. A paused app's sends are refused with a message saying so, and nothing is charged. Check who you're sending to and what, then contact support to resume it. Sending never resumes on its own.

Sending health

Under each address, Host → Tools → Transactional Email shows the last 7 days: the bounce and spam-complaint rates against the limits above, whether sending is paused and why, and how many recipients your app no longer mails.

Credits

Each accepted send is charged in credits to the Solution that owns the app. See Usage & Billing.

Your app's sending key

Under each address, App sending key gives the app a key that can send its own email and nothing else. Create in app env puts it in the app's settings as WAYMAKER_EMAIL_KEY without showing it to anyone — the app picks it up the next time it deploys. Show once instead is for an app whose server runs somewhere else: copy it then, because it is never shown again. Rotate replaces it (the old key stops working at once, so redeploy the app), and Revoke stops it. You need to be an owner or releaser of the app's Solution.

A key lasts only as long as the access of the person who created it. If they leave your organisation or stop being an owner or releaser of the Solution, a key that was shown to them stops working, and a key kept in the app's settings is replaced with a new one. The old one keeps working for 72 hours, so redeploy the app within that time. Your organisation's owners get an email either way.

Developers

To send from code, the CLI or an AI assistant, see the Transactional Email developer guide.