Mattering Automations Resend integration
Connect Resend to Mattering Automations: transactional and batch sends, scheduled-send control, sending domains and DNS verification, contacts, segments, broadcasts, and suppressions as workflow steps, authenticated with a Resend API key.
The Mattering Automations Resend integration adds Resend to your automation canvas: send transactional email one message at a time or up to 100 distinct messages per batch, reschedule or cancel a queued message before it goes out, read what happened to a message you already sent, pull account-level deliverability metrics, register sending domains and watch their DNS verification, manage contacts and segments, compose and send broadcasts, and run the suppression list.
Setup takes a few minutes on the Mattering side: create an API key in Resend, attach it as a credential, and test the connection. The part that takes longer is outside both products. Sending requires a domain that Resend has verified, which means publishing the DKIM and SPF records it gives you in your own DNS and waiting for them to propagate. This guide walks through each step and ends with the full node reference.
The sending model is stated plainly rather than hidden in a footnote. Three nodes put real mail in real inboxes: Resend: Send Email (Sends Real Email), Resend: Send Batch Emails (Sends Real Email), and Resend: Send Broadcast (Sends Real Email). Once Resend accepts the request the message cannot be unsent, and there is no sandbox or test mode anywhere in the API to practise against. What there is instead is a real undo window: schedule the send a few minutes out, verify it, then let it go or stop it with Resend: Cancel Scheduled Email. Verify this integration with read nodes only.
Before you start
- A Resend account, and a domain you control that you can publish DNS records for. Nothing sends until a domain reaches verified status, and that DNS work is the one step no node can do for you.
- A Resend API key created with the full_access permission (resend.com/api-keys). A sending_access key can send email but returns 401 restricted_api_key on every management endpoint in this integration.
- A Mattering workspace with access to the Automations app.
- For broadcast flows: at least one segment with contacts in it, since a broadcast is addressed to a segment rather than to a list of recipients.
Create a Resend API key
Mattering authenticates to Resend with an API key, sent as a bearer credential on every request. Keys are created in the Resend dashboard and look like re_ followed by a secret. There is no OAuth flow involved and no region-specific host to choose, because Resend sets the sending region per domain rather than per account.
Connect Resend to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Resend section should list the query and action nodes. Drop Resend: List Domains onto the canvas and run a test step. It takes no parameters, sends nothing, and is the same call the connection test makes; a successful response lists every sending domain with its status, region, and capabilities. Note which domains read verified, because those are the only ones a from address can use.
To confirm the rest of the surface, run Resend: List Segments for the marketing side, Resend: List Suppressions for deliverability hygiene, and Resend: List Sent Emails to see recent activity with each message's latest delivery event. Every node in this verify path is a safe read. Nothing here touches Resend: Send Email (Sends Real Email) or the other two send nodes, which are the only ones that put mail in an inbox.
Node reference
36 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 16
Resend: Get Broadcast
resend_get_broadcast
Read one broadcast in full: sender, subject, HTML and text bodies, target segment, topic, status and schedule. Works for broadcasts created in the dashboard as well as by API.
Resend: Get Broadcast Metrics
resend_get_broadcast_metrics
Aggregate results for one broadcast: how many were sent, delivered, opened, clicked, unsubscribed, bounced, complained and suppressed, each with a percentage, plus the most clicked links. Read it a while after sending; a broadcast still going out reports a non-zero remaining count.
Resend: Get Contact
resend_get_contact
Read one contact by id or by email address, including any custom properties and the unsubscribed flag. Looking a contact up by email is the usual way to check subscription state before an automation emails somebody.
Resend: Get Domain
resend_get_domain
Read one sending domain, including the full DNS record set (SPF, DKIM and any tracking CNAME) with the current status of each record. Use it to check whether DNS has propagated before an automation starts sending from that domain.
Resend: Get Email Metrics
resend_get_email_metrics
Account-level sending statistics over a date range: volumes (sent, delivered, opened, clicked, bounced, complained, unsubscribed, suppressed, failed) and the derived rates, optionally bucketed by period, domain or individual email. Use it for a deliverability digest or to alert when the bounce rate climbs.
Resend: Get Segment
resend_get_segment
Read one segment by id: its name and creation time. Use it to confirm a segment still exists before pointing a broadcast at it.
Resend: Get Sent Email
resend_get_email
Read one sent email in full: recipients, subject, HTML and text bodies, tags, schedule, and last_event, which is the delivery state (sent, delivered, opened, clicked, bounced, complained). This is how an automation checks what actually happened to a message it sent earlier.
Resend: Get Suppression
resend_get_suppression
Look up one suppression by id or by email address. Because the email form works, this is the cheap pre-send check: if the address is suppressed, sending to it will not reach anyone.
Resend: List API Keys
resend_list_api_keys
List the API keys on this Resend team as METADATA ONLY: id, name, created_at and last_used_at. Resend shows a key's secret value exactly once, at creation, and never again, so nothing sensitive appears in this output. Useful for spotting keys that have not been used in months before rotating them. If this returns 401 with error code restricted_api_key, the connector credential was created with sending_access permission (email sending only). Management endpoints need a full_access key.
Resend: List Broadcasts
resend_list_broadcasts
List the broadcasts on this account with their status (draft, scheduled, sent), target segment and timestamps. Cursor paginated: pass the last item's id as after to walk forward, or the first item's id as before to walk back. Use one or the other, never both.
Resend: List Contacts
resend_list_contacts
List the marketing contacts on this Resend account, optionally narrowed to one segment. Each row carries the email, name and the global unsubscribed flag. Cursor paginated: pass the last item's id as after to walk forward, or the first item's id as before to walk back. Use one or the other, never both.
Resend: List Domains
resend_list_domains
List the sending domains on this Resend account with their verification status, region and sending or receiving capabilities. Needs no configuration at all, returns no credential material, and 401s on a bad key, so it doubles as the connector health check: run it first to confirm which domains you are actually allowed to send from. If this returns 401 with error code restricted_api_key, the connector credential was created with sending_access permission (email sending only). Management endpoints need a full_access key.
Resend: List Segment Contacts
resend_list_segment_contacts
List the contacts inside one segment, a page at a time. Use it to size a broadcast before sending it, or to sync segment membership into another system. Cursor paginated: pass the last item's id as after to walk forward, or the first item's id as before to walk back. Use one or the other, never both.
Resend: List Segments
resend_list_segments
List the contact segments on this Resend account. Segments are the groups a broadcast is addressed to, and they replace the deprecated Audiences API. Cursor paginated: pass the last item's id as after to walk forward, or the first item's id as before to walk back. Use one or the other, never both.
Resend: List Sent Emails
resend_list_emails
List emails this team has sent, newest first, with recipients, subject, schedule and the latest delivery event per message. The message body is not included here; use Resend: Get Sent Email for that. Cursor paginated: pass the last item's id as after to walk forward, or the first item's id as before to walk back. Use one or the other, never both.
Resend: List Suppressions
resend_list_suppressions
List the addresses Resend will not deliver to, with why each one was suppressed (a hard bounce, a spam complaint, or a manual entry) and the id of the email that triggered it. This is the deliverability hygiene read: a growing bounce-origin list means the address source needs attention. Cursor paginated: pass the last item's id as after to walk forward, or the first item's id as before to walk back. Use one or the other, never both.
Action nodes 20
Resend: Add Suppression
resend_add_suppression
Block all future delivery to one address. Use it the moment somebody opts out anywhere in your own product, so a mistake elsewhere in an automation cannot email them again. Sends nothing. Reversible with Resend: Remove Suppression, but reversing it is a consent decision, not a technical one.
Resend: Cancel Scheduled Email
resend_cancel_email
Stop a scheduled email from going out. This is the undo for Resend: Send Email whenever scheduled_at was used, and the reason scheduling a few minutes ahead is the recommended safe pattern for automated sending. It only works while the message is still scheduled; a message already sent cannot be recalled. Note a cancelled email cannot be rescheduled: send a new one instead.
Resend: Create Broadcast (Draft)
resend_create_broadcast
Compose a broadcast to a segment and leave it as a DRAFT. Nothing is delivered by this node: sending is a separate, deliberate step through Resend: Send Broadcast, and a draft can be reviewed in the Resend dashboard first. The API's own send-on-create switch is not exposed here on purpose. One caveat: extra_body is a passthrough, so putting "send": true in it WOULD send real email to the whole segment immediately. Include the unsubscribe link placeholder in the HTML.
Resend: Create Contact
resend_create_contact
Add a marketing contact, optionally placing it into segments and setting topic subscriptions in the same call. Creating a contact sends no email of any kind. Only broadcasts consider the contact list; transactional sends through Resend: Send Email do not.
Resend: Create Domain
resend_create_domain
Register a sending domain and get back the DNS records that must be published before it will verify. Creating the domain sends nothing and enables nothing on its own: the domain stays at status not_started until the DNS records exist and Resend: Verify Domain succeeds. Reversible with Resend: Delete Domain.
Resend: Create Segment
resend_create_segment
Create a contact segment to group contacts and address broadcasts to. Takes a name only; add contacts with Resend: Create Contact (its segments field) afterwards. Reversible with Resend: Delete Segment.
Resend: Delete API Key (Destructive)
resend_delete_api_key
DESTRUCTIVE: permanently revoke an API key. Every system using that key starts failing with 401 immediately, and the secret cannot be recovered or re-issued, only replaced with a new key created in the Resend dashboard. Check the id twice: deleting the key this connector itself uses takes every Resend node in the workspace down with it. This cannot be undone from the API: there is no restore endpoint.
Resend: Delete Broadcast (Destructive)
resend_delete_broadcast
DESTRUCTIVE: permanently remove a broadcast and its content. This cannot be undone from the API: there is no restore endpoint. Only draft and scheduled broadcasts can be deleted; one already sent cannot. Deleting a SCHEDULED broadcast also cancels the delivery, which makes this the stop button for Resend: Send Broadcast, at the cost of losing the draft too.
Resend: Delete Contact (Destructive)
resend_delete_contact
DESTRUCTIVE: permanently remove a contact, by id or email address, along with its properties and segment memberships. This cannot be undone from the API: there is no restore endpoint. If the goal is to stop emailing somebody, prefer Resend: Update Contact with unsubscribed true, or Resend: Add Suppression, both of which keep the record of their choice. Deleting instead means a future import can silently re-subscribe them.
Resend: Delete Domain (Destructive)
resend_delete_domain
DESTRUCTIVE: permanently remove a sending domain. Every automation that sends from an address on this domain stops working immediately, and Resend documents a second consequence: removing a domain that had a custom tracking subdomain also removes the Resend-provisioned proxy, which BREAKS EVERY LINK already sent in past emails that used that subdomain. This cannot be undone from the API: there is no restore endpoint. Re-adding the domain means publishing fresh DNS records and verifying again.
Resend: Delete Segment (Destructive)
resend_delete_segment
DESTRUCTIVE: permanently remove a segment and the membership information that went with it. This cannot be undone from the API: there is no restore endpoint. Any broadcast still pointing at this segment loses its audience. The docs do not state whether the member contacts themselves survive, so assume the worst and check with Resend: List Contacts before deleting a segment you care about.
Resend: Remove Suppression
resend_remove_suppression
Lift a suppression so email can reach that address again, by suppression id or by email address. Mechanically reversible (re-add it and delivery stops again), which is why this is not flagged destructive. CAUTION all the same: a suppression with origin complaint or bounce exists because the recipient marked mail as spam or the address rejected it. Only lift one you have a documented, lawful basis to email again.
Resend: Reschedule Email
resend_update_email
Move a scheduled email to a different time before it goes out. Only scheduled_at can be changed; the content is fixed once the message is queued, and an email that has already been sent cannot be changed. Reschedule as often as you like, up to 30 days ahead.
Resend: Send Batch Emails (Sends Real Email)
resend_send_batch_emails
SENDS REAL EMAIL to real inboxes. Once Resend accepts the request the message cannot be unsent, and it draws down the account's daily and monthly sending quota. Send up to 100 DIFFERENT messages in one request, each with its own sender, recipients, subject and body: the way to fan a personalised message out to a list without a loop. The response is an array of ids in the same order as the input. Attachments are not supported on this endpoint. Safe ways to test: (1) set scheduled_at a few minutes out and keep Resend: Cancel Scheduled Email handy, since a scheduled send can be cancelled or rescheduled by API right up until it goes out; (2) send to Resend's reserved test recipients, which reach no human but do still use quota: delivered@resend.dev (simulates delivery), bounced@resend.dev (simulates a hard bounce), complained@resend.dev (simulates a spam complaint) and suppressed@resend.dev; (3) send to your own address first. Resend has no sandbox mode that accepts a message without delivering it.
Resend: Send Broadcast (Sends Real Email)
resend_send_broadcast
SENDS REAL EMAIL to real inboxes. Once Resend accepts the request the message cannot be unsent, and it draws down the account's daily and monthly sending quota. This one goes to EVERY contact in the broadcast's segment at once, so it is the highest blast radius node in the connector: check the recipient count with Resend: List Segment Contacts before wiring it into anything automatic. Safe path: set scheduled_at (natural language or ISO 8601), which leaves the broadcast in scheduled state, and cancel it before that time by deleting it with Resend: Delete Broadcast, which the docs confirm also cancels the scheduled delivery. Only broadcasts created through the API can be sent through the API.
Resend: Send Email (Sends Real Email)
resend_send_email
SENDS REAL EMAIL to real inboxes. Once Resend accepts the request the message cannot be unsent, and it draws down the account's daily and monthly sending quota. Send one transactional message with HTML, plain text, or a saved Resend template. Safe ways to test: (1) set scheduled_at a few minutes out and keep Resend: Cancel Scheduled Email handy, since a scheduled send can be cancelled or rescheduled by API right up until it goes out; (2) send to Resend's reserved test recipients, which reach no human but do still use quota: delivered@resend.dev (simulates delivery), bounced@resend.dev (simulates a hard bounce), complained@resend.dev (simulates a spam complaint) and suppressed@resend.dev; (3) send to your own address first. Resend has no sandbox mode that accepts a message without delivering it. The response carries only the new email's id; delivery outcome arrives later through Resend: Get Sent Email or a webhook. The from address must be on a domain verified in this Resend account, or the send is rejected with a validation_error. Check with Resend: List Domains.
Resend: Update Broadcast
resend_update_broadcast
Edit a broadcast that has not been sent yet: content, subject, sender, target segment or topic. Only the fields you fill in are sent. Delivers nothing on its own.
Resend: Update Contact
resend_update_contact
Update a contact by id or email address. Only the fields you fill in are sent. The common automation is flipping unsubscribed to true when someone opts out in your own product, which stops all future broadcasts to them.
Resend: Update Domain
resend_update_domain
Change a domain's tracking, TLS policy or sending and receiving capabilities. Only the fields you fill in are sent. Two things are one-way: a tracking_subdomain cannot be removed once set, and at least one of sending or receiving must stay enabled.
Resend: Verify Domain
resend_verify_domain
Ask Resend to re-check the domain's DNS records. Verification is asynchronous: the call returns straight away, the domain moves to pending, and the result arrives later (visible via Resend: Get Domain, or as a domain.updated webhook). Safe to run repeatedly; it sends no email and changes no records.
Using the integration
On the automation canvas
Resend nodes chain with every other node: a scheduled Resend: Get Email Metrics read can open a task in Mattering Productivity when the bounce rate climbs, a support record marked closed can trigger a follow-up message, and a hard bounce found through Resend: List Suppressions can update the customer record it came from. Reads are cursor paginated with a limit that defaults to 20 and caps at 100: pass the last item's id as after to walk forward, or the first item's id as before to walk back, and never both at once. The API allows 10 requests per second per team across all of that team's keys, so pace large sweeps.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can check whether a domain is verified, look up what happened to a message with Resend: Get Sent Email, report on a campaign with Resend: Get Broadcast Metrics, and check whether an address is suppressed, through the same nodes your workflows use. The 16 read nodes are the safe surface to hand an assistant. The three send nodes are not, and their labels are written so that a person reviewing an agent's plan can see them at a glance.
The send nodes and the documented safe path
Resend: Send Email (Sends Real Email) sends one transactional message to up to 50 recipients. Resend: Send Batch Emails (Sends Real Email) sends up to 100 different messages in one request and returns their ids in input order. Resend: Send Broadcast (Sends Real Email) reaches every contact in a segment at once, which makes it the highest blast radius node here; size the segment with Resend: List Segment Contacts before wiring it into anything automatic. There is no sandbox and no test mode in this API, so use the safe path in this order. First, set scheduled_at, which takes natural language such as in 5 min or an ISO 8601 timestamp up to 30 days ahead, and keep Resend: Cancel Scheduled Email or Resend: Reschedule Email on the canvas; for a broadcast the equivalent stop button is Resend: Delete Broadcast (Destructive), which also cancels a scheduled delivery. Second, use Resend's reserved test recipients at resend.dev (delivered@ simulates delivery, bounced@ a hard bounce, complained@ a spam complaint, suppressed@ a suppressed address); they reach no human, but they still draw down your sending quota, so they are cheap rather than free. Third, send to your own address on a domain you control. A send response carries only the new message id, never a delivery outcome; that arrives later from Resend: Get Sent Email and its last_event field.
What goes into a send: idempotency keys and attachments
Both single and batch sends expose an Idempotency-Key of up to 256 characters that Resend remembers for 24 hours. Derive it from something stable in the trigger, such as an order id, rather than generating it randomly: that way a retried workflow run produces the same key and Resend replays the original result instead of sending a second message. In an engine that retries failed steps, this is the field that makes automated email safe. Attachments are input only on Resend: Send Email (Sends Real Email) and are steered toward the path form, a hosted URL that Resend fetches, with a documented ceiling of 40 MB per email; the inline base64 content form works but bloats every execution record, so keep it for small files. Batch sends do not support attachments at all, and the attachment read endpoints are deliberately not built because their output is base64 file content.
Domains, DNS, and the verification loop
Resend: Create Domain registers a domain and returns the DNS records that must be published before it will verify; creating it enables nothing on its own and the domain sits at not_started until the records exist. Resend: Verify Domain asks Resend to re-check, but verification is asynchronous: the call returns immediately with the domain at pending, so poll Resend: Get Domain for the record-by-record status. Resend: Update Domain changes tracking, TLS policy, and sending or receiving capability, with two one-way doors: a tracking_subdomain cannot be removed once set, and at least one of sending or receiving must stay enabled. The connector always sends the User-Agent header Resend requires on every request, so that is one piece of setup nobody has to think about.
Contacts, segments, suppressions, and the five permanent deletes
Segments replace Resend's deprecated Audiences API, so Resend: Create Segment and Resend: List Segments are where groups live, and Resend: Create Contact places a contact into segments at creation. To stop emailing somebody, prefer Resend: Update Contact with unsubscribed set true, or Resend: Add Suppression, both of which preserve the record of their choice. Resend: Remove Suppression is not flagged destructive, because re-adding the suppression restores the state exactly, but treat it as a consent decision rather than a toggle: a suppression with a bounce or complaint origin exists because that address rejected mail or someone marked it as spam, and lifting it means you will email that person again. Five nodes are permanent, because the API documents no restore endpoint anywhere: Resend: Delete Domain (Destructive), Resend: Delete API Key (Destructive), Resend: Delete Contact (Destructive), Resend: Delete Segment (Destructive), and Resend: Delete Broadcast (Destructive). Three of them carry a hazard worth naming out loud: deleting a domain that had a custom tracking subdomain also removes the proxy behind it and breaks every link inside email you have already sent; deleting an API key can revoke the very credential this connector uses and take every Resend node in the workspace down; and deleting a scheduled broadcast cancels its delivery as well as losing the draft.
Troubleshooting
Test Connection fails, or every node returns 401 with the error code restricted_api_key
Test Connection fails with a plain 401 and no restricted_api_key code
A send is rejected with a validation_error mentioning the from address
There are no Audiences nodes, and an older tutorial's contact paths return 404
Resend: Cancel Scheduled Email is refused, or the message went out anyway
Requests start failing with 429
A broadcast exists but Resend: Send Broadcast (Sends Real Email) refuses it
Links inside email sent months ago stopped working
Related
The Resend MCP
What connecting Resend unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Resend is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.