Customer email from your own domain, via Resend

MadMax can send email with nothing connected, through its own sender. Resend is for when the mail has to come from you: your verified domain, your from-address, your Resend logs and deliverability. Connect a key and any workflow sends as billing@yourdomain.com, with a body an AI agent wrote a step earlier and, where it matters, a person who read it before the customer did. Describe it in plain English and MadMax wires the step with your default from-address and previews the exact email (from, to, subject, body) during the build without sending it, so the first real email goes out only after you activate.

What teams build

• A Stripe payment succeeded event hits a webhook, an AI agent turns the line items into two friendly sentences, and send_email delivers the receipt from receipts@yourdomain.com.
• An email trigger receives a support question, an agent bound to a knowledge base drafts the answer, and an approval shows it to the support lead in Slack; on approve, Resend sends it from your support address, and on reject the draft goes back to the thread for edits.
• A daily schedule gets the store rows still missing reminded_at, a loop sends one reminder each from your domain, and a store upsert marks them so tomorrow's run skips them.

How it connects

Create an API key in Resend (it starts with re_) and paste it in. Optionally set a default from address, which must be a verified sender on your Resend account; it is used whenever a step leaves from empty, so most steps only need a recipient, a subject and a body. The step takes a single recipient, so for several people loop over the list. The key is stored encrypted and rotating it is a reconnect on the same connection. If the sender does not matter, the built-in send email step needs no connection at all. See managing connections.

Related

• Email in MadMax
• Send email step
• Approval step
• Managing connections
• Stripe