AI workers for Resend
Ready-made AI workers that send email through Resend: clean transactional messages from a verified domain, with no sending infrastructure to stand up first.
- Appointment Reminder Texter
Texts your clients a day-before reminder for their appointments, cutting no-shows dramatically.
What is an AI worker for Resend?
An AI worker using Resend is an AI agent that can send email through your Resend account, a modern sending service teams choose when they want reliable transactional delivery without assembling a mail stack. It sends from your verified domain, and only where your permissions and contact rules allow.
What these workers do
Confirm something is ready
Emails the confirmation the moment a request reaches the state the person was waiting for, from your own domain.
Deliver a daily or weekly summary
Sends a recurring digest built from your connected systems to the small list of people who need it.
Send a promised follow up
Delivers the message that was agreed in a conversation, at the time it was agreed for.
Notify a customer of a change
Reaches out when something they care about has moved, with the specifics rather than a prompt to log in and check.
How an AI worker runs in Resend
Short path from nothing to sending properly
Verified domain, recognisable sender
Small, expected, transactional
Resend questions, answered.
What address will messages come from?
A domain you have verified in your own Resend account, so recipients see your business as the sender. That verification is what stops an automated message from landing as an unfamiliar and untrusted address.
How is this different from sending through my mailbox?
A mailbox connection sends as a person, from their inbox, and the message sits in their sent folder. This sends as your product or service, which is the right identity for a confirmation or a system notification that no individual should appear to have typed.
Can a worker email anyone it decides to?
No. Recipients are checked against your contact rules as the message is sent, and a blocked address is refused at that boundary regardless of what the worker concluded it should do. The rules are enforced outside the worker, which is what makes opting somebody out actually stop messages reaching them.
Is it suitable for bulk email?
Workers here are built for transactional messages a recipient expects, not for campaigns. Anything involving marketing consent and unsubscribe management at scale belongs in a system designed for exactly that.
What AI workers can do in Resend
The tools a worker can be granted in Resend once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.
Send Message
Send a message through Messaging behind the WorkerKit firewall. Recipients are checked against the token's contact rules and the suppression/opt-out list before anything is sent (blocked → RECIPIENT_SUPPRESSED); the sender/channel must be permitted for this token. Provider support varies: scheduledAt and idempotencyKey are RESEND-only, mediaUrls TWILIO/RESEND-only, and 'from' is required for email providers — check providerCapabilities in the capabilities manifest.
Send Template Message
Send a Messaging template message with variable substitution. Discover template IDs with messaging_list_templates. The same firewall gates as messaging_send_message apply.
Dry-Run Send
Validate a Messaging send WITHOUT sending: runs every firewall gate (permissions, sender/channel scope, recipient contact rules, suppression list) and reports the verdict. Use before a real send to surface blocks early.
Preview Message
Preview a Messaging send WITHOUT sending: builds the message (template variables applied) and runs the same firewall gates as a real send, returning what would happen. Prefer messaging_dry_run_send when only the gate verdict matters.
Get Message Status
Get the delivery status of a Messaging message by the messageId returned from a send (status, recipient, timestamps, failure reason).
List Activity
List recent Messaging send activity (message metadata + delivery status; bodies are masked per the token's field visibility).
Get Stats
Get aggregate Messaging sending stats (volumes and outcome counters for the recent period). TWILIO and SENDGRID only; RESEND has no stats API.
List Senders
List the sender identities this Messaging connection can send from (a sender identity the connection can send from (see messaging_list_senders)). Use one of these as 'from'.
List Templates
List Messaging message templates available to this connection.
Get Template
Get a single Messaging template by ID.
Validate Recipient
Check whether a recipient address/number is valid and reachable via Messaging before sending. TWILIO only (Lookup).
Check Opt-Out
Check whether a recipient has opted out / is suppressed on Messaging. Sends to suppressed recipients are blocked automatically. SENDGRID only in v1.
List Suppressions
List recipients on the Messaging suppression list (opted-out / unsubscribed). SENDGRID only in v1.
Suppress Recipient
Add a recipient to the Messaging suppression list so future sends to them are blocked (records an opt-out). SENDGRID only in v1.
Unsuppress Recipient
Remove a recipient from the Messaging suppression list (higher-trust: only do this when the recipient asked to receive messages again). SENDGRID only in v1.
Cancel Scheduled Message
Cancel a scheduled Messaging message that has not been delivered yet, by the messageId the send returned. RESEND only in v1.
Send Resend Message
Send a message through Resend behind the WorkerKit firewall. Recipients are checked against the token's contact rules and the suppression/opt-out list before anything is sent (blocked → RECIPIENT_SUPPRESSED); the sender/channel must be permitted for this token. Attachment URLs are fetched by Resend (must be publicly reachable).
Send Resend Template Message
Send a Resend template message with variable substitution. Discover template IDs with resend_list_templates. The same firewall gates as resend_send_message apply. Only PUBLISHED Resend templates can send — drafts fail with a template error.
Dry-Run Resend Send
Validate a Resend send WITHOUT sending: runs every firewall gate (permissions, sender/channel scope, recipient contact rules, suppression list) and reports the verdict. Use before a real send to surface blocks early.
Preview Resend Message
Preview a Resend send WITHOUT sending: builds the message (template variables applied) and runs the same firewall gates as a real send, returning what would happen. Prefer resend_dry_run_send when only the gate verdict matters.
Get Resend Message Status
Get the delivery status of a Resend message by the messageId returned from a send (status, recipient, timestamps, failure reason).
List Resend Activity
List recent Resend send activity (message metadata + delivery status; bodies are masked per the token's field visibility). Rows carry no message body; fetch a single message with resend_get_message_status for content.
List Resend Senders
List the sender identities this Resend connection can send from (an address on a verified domain, optionally as "Name <email@domain>" (see resend_list_senders)). Use one of these as 'from'.
List Resend Templates
List Resend message templates available to this connection.
Get Resend Template
Get a single Resend template by ID.
Cancel Scheduled Resend Message
Cancel a scheduled Resend message that has not been delivered yet, by the messageId the send returned.