Menu
Mattering Automations connector

A Resend MCP that never pretends a sent email can be unsent

Connect one Resend API key and sending, schedule control, domains, contacts, segments, broadcasts, and suppressions become workflow steps for visual automations and AI agents. Three nodes put real mail in real inboxes and carry that in their own labels. Every send also carries a schedule-then-cancel window and an Idempotency-Key, so a retried run cannot double-send.

36 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Resend MCP connector does

The Resend connector for Mattering Automations is 36 nodes across the REST API: transactional sending one message at a time or up to 100 distinct messages per batch, schedule control that can reschedule or cancel a queued message before it goes out, reads on what was actually sent plus account-level deliverability metrics, sending domains and their DNS verification, contacts and segments, broadcasts from draft through send with their metrics, the suppression list, and API key metadata. It is a curated surface rather than a mirror: the API now runs to roughly 80 endpoints, and templates, topics, webhooks, logs, received email, and the whole OAuth surface are deliberately left out.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer whether a domain is verified, what happened to a message sent last Tuesday, how a broadcast performed, and whether an address is suppressed, without anyone opening the Resend dashboard.

Because Mattering is a work platform rather than middleware, email work lands somewhere useful by default: a scheduled metrics read can open a task when the bounce rate climbs, a hard bounce can suppress the address and update the record it came from, and a broadcast draft can wait on an approval task before anyone sends it, all on one canvas next to the rest of the work.

Sending is the boundary, and the connector says so out loud rather than in a footnote. Three nodes put real mail in real inboxes, and their labels carry it: Resend: Send Email (Sends Real Email), Resend: Send Batch Emails (Sends Real Email), and Resend: Send Broadcast (Sends Real Email). Each description opens with the words SENDS REAL EMAIL. Once Resend accepts the request the message cannot be unsent, and it draws down the account's daily and monthly sending quota. So the safe path lives on the nodes themselves, in order: schedule a few minutes out and keep the cancel node handy, then use Resend's reserved test recipients, then send to your own address first.

One connection, three surfaces

  • Visual automations. Drag Resend nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Resend node, ready to drop on the canvas

36 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 16

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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)

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

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

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

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)

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)

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)

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)

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)

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

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

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)

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)

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)

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

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

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

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

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.

Connecting Resend takes one credential

Resend issues API keys from resend.com/api-keys. Keys look like re_ followed by a secret, and Mattering sends the key as a bearer credential on every request. The one choice that matters is permission: a key is created with either full_access or sending_access. Create the connector credential with full_access, because a sending_access key can send email but returns 401 with the error code restricted_api_key on every management endpoint in this connector.

1

In Resend, open API Keys (resend.com/api-keys) and create a key with Full access permission. Resend shows the secret exactly once, at creation, and never again, so copy it now.

2

In Mattering Automations, open Connectors, click Add Connector, choose Resend, and create a credential with that key.

3

Click Test Connection. Mattering calls Resend's domains endpoint, which takes no parameters, returns no credential material, and fails with a 401 on a bad or under-scoped key.

4

All 36 Resend nodes appear in the canvas palette. Run Resend: List Domains first: nothing can send until a domain on the account reaches verified status, and that step is DNS work only you can do.

Common uses for the Resend MCP

Transactional email that cannot double-send

Resend: Send Email (Sends Real Email) sends one transactional message as HTML, plain text, or a saved Resend template, to up to 50 recipients per call. Both send nodes expose an Idempotency-Key that Resend remembers for 24 hours, so a workflow that fails halfway and gets retried replays the original result instead of mailing the same person twice. Derive the key from something stable in the trigger, such as the order id, and retries stop being a hazard.

A genuine undo window on automated sending

The scheduled_at field takes natural language such as in 5 min, or ISO 8601, up to 30 days ahead. A scheduled message waits in the queue where Resend: Reschedule Email can move it and Resend: Cancel Scheduled Email can stop it entirely. That window is the closest thing email has to an undo, and it is the recommended pattern for anything automated: schedule, verify, then let it go or cancel it. A cancelled email cannot be rescheduled, so send a fresh one instead.

Personalised fan-out without a loop

Resend: Send Batch Emails (Sends Real Email) takes up to 100 different messages in one request, each with its own sender, recipients, subject, and body, and returns an array of ids in the same order as the input. It is how you fan a personalised message across a list without building a loop on the canvas. Attachments are not supported on this endpoint; single sends take them, steered toward the hosted-URL path form with a documented ceiling of 40 MB per email.

Sending domains and the DNS that gates them

Resend: Create Domain registers a domain and returns the DNS records that have to be published before anything can send from it. Resend: Verify Domain asks for a re-check and returns immediately, because verification is asynchronous, so poll Resend: Get Domain for the record-by-record status, or survey the whole estate with Resend: List Domains. A from address on an unverified domain is rejected outright.

Deliverability you notice before your customers do

Resend: Get Email Metrics returns account-level volumes and derived rates over a date range, optionally bucketed by period, domain, or individual email. Resend: List Suppressions shows every address Resend will not deliver to and why each one landed there, whether a hard bounce, a spam complaint, or a manual entry. Run both on a schedule and route a climbing bounce rate into a task instead of finding out from a customer.

Broadcasts that are drafted, sized, then sent

Resend: Create Broadcast (Draft) composes to a segment and delivers nothing at all; sending is a separate, deliberate step. Check the recipient count with Resend: List Segment Contacts first, because Resend: Send Broadcast (Sends Real Email) reaches every contact in the segment at once and is the highest blast radius node in the connector. Segments replace Resend's deprecated Audiences API, so Resend: List Segments is where the groups live now, and Resend: Get Broadcast Metrics reports how the send actually landed.

Example: An order confirmation that is checked, scheduled, and only then allowed to leave

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a form submission or a record change in a Mattering database supplies the recipient address, the subject, and the order id.

2

Resend: Get Suppression looks the address up by email. If it is suppressed the workflow stops here, because sending would reach nobody and would still draw down the quota.

3

Resend: List Domains confirms the sending domain is verified, since a from address on an unverified domain is rejected with a validation_error.

4

Resend: Send Email (Sends Real Email) queues the message with scheduled_at set a few minutes out and an Idempotency-Key derived from the order id, so a retried run replays the original result rather than sending twice.

5

A review step in Mattering Productivity holds the returned email id while a person looks at it. Resend: Cancel Scheduled Email stops the message before it leaves if anything is wrong, and Resend: Reschedule Email moves it if the timing is the only problem.

6

Once the message has gone, Resend: Get Sent Email reads last_event to record whether it was delivered, opened, clicked, bounced, or complained, and a bounce adds the address through Resend: Add Suppression so nothing mails it again.

Resend MCP questions, answered

What Resend operations are supported?

36 nodes: sending domains (create, read, update, verify, delete), transactional sending one at a time or up to 100 per batch, sent-email reads plus reschedule and cancel on queued messages, account-level email metrics, API key metadata and revocation, contacts, segments and segment membership, broadcasts from draft through update, send, metrics and delete, and the suppression list. Deliberately not shipped: creating API keys, the attachment read endpoints, received email, webhook configuration, templates, topics, contact properties, domain claims, request logs, the OAuth surface, batch suppressions, and the deprecated Audiences family. The API is now roughly 80 endpoints; this is a curated 36, and each omission has a reason rather than a backlog ticket.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. The 16 read nodes are the safe surface to hand an agent; the three send nodes are the ones to gate behind a person.

Can this connector send real email by accident?

It can send real email, and the connector is built so nobody can be surprised by which nodes do it. Three nodes send: Resend: Send Email (Sends Real Email), Resend: Send Batch Emails (Sends Real Email), and Resend: Send Broadcast (Sends Real Email). The label says it, the description opens with SENDS REAL EMAIL, and a sent message cannot be unsent by any means. Resend: Create Broadcast (Draft) deliberately does not expose the API's send-on-create switch, so composing and sending stay two steps. Put a condition, an approval task, or a manual run in front of a send node, and prefer scheduling it so the cancel node is still an option.

Is there a sandbox or test mode?

No. Unlike SendGrid, Resend has no sandbox_mode equivalent: nothing in the API accepts a message and declines to deliver it. That absence is exactly why the schedule-then-cancel path matters. What Resend does offer, in the order worth using it: set scheduled_at a few minutes out and keep Resend: Cancel Scheduled Email ready; send to Resend's reserved test recipients at resend.dev, which reach no human but still consume your sending quota (delivered@resend.dev simulates delivery, bounced@resend.dev a hard bounce, complained@resend.dev a spam complaint, and suppressed@resend.dev a suppressed address); and send to your own address first, on a domain you control.

What stops a retried workflow from sending the same email twice?

An Idempotency-Key, exposed on both send nodes and remembered by Resend for 24 hours. Set it to something derived from the trigger rather than something random, so the retry produces the same key: an order id, an invoice number, a record id. Within that window Resend replays the original response instead of accepting a second send. For an automation engine that retries failed steps, this is the single most useful field on the node.

Where are the Audiences nodes?

There are none, on purpose. Resend has deprecated Audiences in favour of Segments and says the old endpoints will be removed. Contacts moved with them: they are no longer under an audience path but a top-level collection filtered by segment, and broadcasts are now addressed by segment id. Shipping Audiences would mean shipping a node family with a known expiry date and two names for one thing, so this connector ships Segments only. If you arrived from an older tutorial that talks about audiences, read segment everywhere it says audience and use Resend: List Segments.

Sending works but every other node returns 401. Why?

The key was created with sending_access rather than full_access. Resend keys carry one of those two permissions, and a sending_access key is restricted to sending: every management endpoint answers 401 with the error code restricted_api_key, which at the status-code level looks exactly like a bad key. Permission is fixed at creation and cannot be edited, so create a new key with Full access in the Resend dashboard and update the credential on the connector.

Can an automation create a Resend API key?

No, and that is deliberate. Resend's documented response body for key creation contains the new key's plaintext token, so a key-minting node would write live credential material into execution records and node outputs. It is not built. What does ship is Resend: List API Keys, which returns metadata only (id, name, created and last-used timestamps, since Resend shows a secret exactly once at creation), and Resend: Delete API Key (Destructive), which permanently revokes a key. Check that id twice: deleting the key this connector uses takes every Resend node in the workspace down with it, and the API documents no way to restore anything.

36 nodes waiting on the canvas

Put Resend to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Resend is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products