Claude Resend connectorWhat Claude can do in your Resend account.
The Claude Resend connector exposes 85 tools. 28 read your emails, contacts, domains and logs, 43 send, create, change or remove things, and 14 are documented nowhere. Below: what Claude reads, what it sends, and what to check first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach Resend
Resend is an email platform for developers: transactional emails, marketing broadcasts, contacts, domains and the logs behind them. The connector hands Claude most of it, so you can ask in plain words to check why an email failed, build a template, clean a segment or send a campaign. That reach is wide: 43 tools change your account, including sends and deletions.
Find out why an email failed. list-logs and get-log show your app's API calls with full request and response bodies, and get-domain shows the sender domain's settings.
Build and ship campaigns. create-template, create-broadcast and send-broadcast take a newsletter from draft to audience, while get-tiptap-json-content lets Claude read what you are editing in the dashboard.
Keep the audience tidy. create-contact-import, add-contact-to-segment and update-contact-topics handle imports, segments and subscriptions.
What the connector does not do: the Inboxes feature Resend describes is in beta and needs access from Resend, and 14 tools have no read or write sense on record, most with no description at all. Claude itself runs nothing on a schedule. Automations you create do send on their own, but that is Resend doing it. For flows that span several apps, with data moving on every event, see our Resend Make integration page.
Five words before you connect
The vocabulary Claude uses around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude chooses the tools it needs by itself, and the directory lists them by name.
- Authorization
- The Resend sign-in screen where you hand Claude the access it will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it does something that changes your account, shown in the chat at the right moment.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Resend.
Connect Resend to Claude in three steps
- 01
Find Resend in Claude
Open Claude's settings, go to Customize then Connectors, and look for Resend in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first; each member then signs in on their own.
- 02
Start the connection
Click Connect on the Resend row, then sign in to Resend in the window the service opens itself, not inside Claude. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Check what the screen lists before you accept. It belongs to Resend, not to Claude, and it sets what the access covers. You can also withdraw that access later from your Resend account.
The 85 tools, split by what they do
Resend gives Claude 85 tools: 28 that read your account, 43 that change something in it, and 14 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay as Claude shows them.
- 28 read
- 43 write
- 14 not documented
What Claude can read in Resend
28 tools28 tools that read emails, contacts, templates, domains, webhooks and logs.
get-automation
Opens one automation in Resend so Claude can explain in plain words how it is set up.
get-automation-runs
Shows the runs of an automation, the record of each time it fired, so Claude can tell you what happened for a given contact and when.
get-broadcast
Fetches one broadcast campaign with its content, its schedule, its personalization placeholders and its preview text, the line people see before opening.
get-contact
Opens one contact in your Resend audience, with the custom properties you track on it, so Claude can answer questions about that person.
get-contact-property
Reads the definition of one custom contact attribute, the extra field stored on every contact, such as a plan name or a signup source.
get-domain
Fetches one domain registered in Resend, with its tracking, TLS and inbound or outbound settings, so Claude can explain its state.
get-email
Fetches one outgoing email from your account, so Claude can check its content, its recipients and its current status.
get-log
Opens one API request log in full, including the request and response bodies your app exchanged with Resend.
get-received-email
Reads one inbound email that reached a Resend receiving address, so Claude can summarize it or pull out what matters.
get-received-email-attachment
Downloads one attachment from an inbound email, so Claude can work with the file itself rather than a description of it.
get-segment
Opens one audience segment, the group of contacts a broadcast can target, so Claude can tell you who is in it.
get-template
Pulls up one email template with its content and its triple-brace variable placeholders, so Claude can read it back or check it.
get-tiptap-json-content
Reads the content of a draft open in Resend's visual editor while you collaborate on a broadcast or a template with Claude.
get-topic
Opens one subscription topic, the theme contacts can opt into or out of, with what it covers.
get-webhook
Fetches one webhook, the address Resend notifies when an email event happens, with its configuration.
list-api-keys
Lists the API keys on your Resend account, the credentials your apps use to talk to Resend.
list-broadcasts
Lists your broadcast campaigns, past and planned, so Claude can give you an overview of what reached customers and what is queued.
list-contact-properties
Lists the custom attributes defined on your contacts, the extra fields your audience carries beyond name and email.
list-contacts
Lists the contacts in your Resend audience, so Claude can count, filter or look through them for you.
list-domains
Lists the domains registered in your Resend account and their status, so Claude can tell you which are ready and which are not.
list-emails
Lists the outgoing emails of your account, so Claude can trace what a given customer received and when.
list-logs
Lists your API request logs, the trace of every call your apps made to Resend, so Claude can spot failures and patterns.
list-received-email-attachments
Lists the attachments of one inbound email, with enough detail for Claude to pick the right file.
list-received-emails
Gathers the inbound emails that reached your Resend addresses, so Claude can triage or summarize them in one pass.
list-segments
Lists your audience segments, the named groups of contacts your campaigns can target.
list-templates
Lists your email templates, drafts and published ones, so Claude can find the one you have in mind.
list-topics
Lists your subscription topics, the themes contacts can opt into, so Claude can review your preference options.
list-webhooks
Lists the webhooks that notify your systems of email events, with the address each one calls.
What Claude can change in Resend
43 tools43 tools that send, create, update or remove. No source gives any of them a confirmation of its own.
add-contact-to-segment
Approval: see the rulePuts a contact into an audience segment, part of what Resend calls managing segment memberships.
cancel-email
Approval: see the ruleCancels an email that is scheduled but not yet sent.
create-api-key
Approval: see the ruleCreates a new API key on your Resend account.
create-automation
Approval: see the ruleBuilds a new automation, which Resend then runs on its own when an event sent for a contact triggers it.
create-broadcast
Approval: see the ruleSets up a new broadcast campaign, with scheduling, personalization placeholders and preview text.
create-contact
Approval: see the ruleAdds a contact to your Resend audience, with any custom properties you define.
create-contact-import
Approval: see the ruleStarts a CSV import of contacts, one of the contact tasks Resend's page names.
create-contact-property
Approval: see the ruleDefines a new custom attribute that every contact can carry.
create-domain
Approval: see the ruleAdds a new sender domain to Resend, the first step before sending from it.
create-domain-claim
Approval: see the ruleOpens a claim on a domain, which Resend lists alongside domain verification.
create-segment
Approval: see the ruleGroups contacts into a new audience segment to group contacts for broadcasts, a list you can then target.
create-template
Approval: see the ruleProduces a new email template, with content and triple-brace variable placeholders.
create-topic
Approval: see the ruleAdds a subscription topic contacts can choose to follow.
create-webhook
Approval: see the ruleRegisters a new webhook so Resend notifies one of your systems of email events.
duplicate-template
Approval: see the ruleCopies an existing template so you can start a variant from it.
publish-template
Approval: see the rulePublishes a template, the step that makes it the live version.
remove-api-key
Approval: see the ruleRemoves an API key from your Resend account.
remove-automation
Approval: see the ruleDeletes an automation from Resend.
remove-broadcast
Approval: see the ruleDeletes a broadcast campaign.
remove-contact
Approval: see the ruleDeletes a contact from your audience.
remove-contact-from-segment
Approval: see the ruleTakes a contact out of a segment without deleting the contact.
remove-contact-property
Approval: see the ruleDeletes a custom contact attribute definition.
remove-domain
Approval: see the ruleDeletes a sender domain from Resend.
remove-segment
Approval: see the ruleDeletes an audience segment.
remove-template
Approval: see the ruleDeletes an email template.
remove-topic
Approval: see the ruleDeletes a subscription topic.
remove-webhook
Approval: see the ruleDeletes a webhook, so Resend stops notifying that address about email events.
send-batch-emails
Approval: see the ruleSends several emails in one go through your Resend account.
send-broadcast
Approval: see the ruleSends a broadcast campaign to its audience.
send-email
Approval: see the ruleSends one email from your verified domain, with HTML or plain text, attachments, CC and BCC, reply-to, tags and optional scheduling.
send-event
Approval: see the ruleSends an event for a contact, which can trigger the automations waiting for it.
update-automation
Approval: see the ruleChanges an automation that already exists in Resend.
update-broadcast
Approval: see the ruleEdits a broadcast before it goes out, content, schedule or preview text.
update-contact
Approval: see the ruleEdits a contact's details or the custom properties stored on it.
update-contact-property
Approval: see the ruleChanges the definition of a custom contact attribute.
update-contact-topics
Approval: see the ruleChanges which subscription topics a contact follows, part of managing topic subscriptions.
update-domain
Approval: see the ruleAdjusts a sender domain's settings, such as tracking, TLS or sending and receiving.
update-email
Approval: see the ruleChanges a scheduled email, for example to reschedule it.
update-template
Approval: see the ruleEdits an existing email template.
update-topic
Approval: see the ruleEdits a subscription topic, such as the way it is named.
update-webhook
Approval: see the ruleChanges a webhook, for example the address it notifies.
verify-domain
Approval: see the ruleRuns the verification of a sender domain in Resend.
verify-domain-claim
Approval: see the ruleCompletes the verification of a domain claim.
Not documented
14 tools14 names the directory publishes with no description. Undocumented means no source says what they do.
compose-broadcast
No official source describes this tool: the directory publishes its name and nothing else. We do not read a purpose into the name, however clear it may look, and this note stops there.
compose-template
Only the name of this one is public, with no sentence from the publisher or from Anthropic behind it. Resend's page lists templates by what they let you do, and this entry is not one of the items it describes, so nothing here says what it produces.
connect-to-editor
The publisher's documentation, as read for this page, never mentions this entry. Resend's page speaks of working in its visual editor in general terms, but no source ties that sentence to this tool or says whether it changes anything.
disconnect-from-editor
This tool shows up in the directory list without a single line of description. Like its counterpart for joining the editor, it has no sense of reading or writing on record, and no source describes what it does to a draft.
get-contact-import
No source documents this one: the directory gives its name, and the publisher's article stays silent. The import itself is documented through create-contact-import; this entry has no description of its own, so any status it may report is not described here.
get-domain-claim
Its name is listed on the directory sheet; its behavior is documented nowhere. Resend documents creating and verifying domain claims, not this entry, and says little about how claims work, so no description is offered for it.
get-sent-email-attachment
There is no official text on this entry beyond the fact that it exists. Without a documented description, any account of what it returns would be a guess presented as a fact, and this page does not publish guesses.
list-contact-imports
We found no source for this one, neither in the publisher's help pages nor in Claude's. If Resend documents it later, this note will say what it does; until a source describes it, it stays blank on purpose.
list-contact-segments
Anthropic's sheet names it, the publisher's article skips it, and that is the whole record. Segment membership is described through add-contact-to-segment and remove-contact-from-segment; no text describes this entry beside them.
list-contact-topics
A listed name, an empty description: that is all the public record holds for this tool. Topic subscriptions are documented through update-contact-topics; this entry has no sentence of its own in any source.
list-oauth-grants
Neither documentation covers this entry, so its purpose stays unknown here. Relying on it means relying on behavior no documentation has written down, worth keeping in mind before trusting an answer built on it.
list-sent-email-attachments
This page has no sourced sentence to offer on this tool, only its listing. Sitting in the list next to documented email tools does not make it documented, so no capability is attributed to it here.
manage-events
Unlike its neighbours in the list, this one has never been described officially. Resend's page mentions sending events and managing event definitions in general terms, but no source ties those words to this entry.
revoke-oauth-grant
The sources behind this page stop short of this tool entirely. Until the publisher documents it, the safest reading is none at all: when a request involves it, ask Claude which tool it plans to call.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. No source adds a Resend-specific rule, not even for sends or deletions.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked each time. They can also limit what a connector may do for the whole organization, for example leaving reads open and closing writes. Nobody overrides that from a personal account. Claude also works with the rights of the person who connected, nothing more: the access comes from the Resend login and approval you complete when connecting.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state of this one, check the Resend sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when an email bounces or a contact signs up.
Everything here comes from Resend's documentation and the directory sheet: no Claude help page covers this connector. The badge in the directory is not a security audit, and Anthropic says on each sheet that it neither picks a publisher's tools nor guarantees their behavior. Connect it because you already trust Resend with your sender reputation, and keep in mind that no documented tool recalls a campaign once it has gone out. Other email apps are in our Integrations hub.
Need help connecting Resend to Claude?
A person reads every message.
