Communication

Resend

by Resend

Overview

Resend's connector MCP server gives your AI agent native access to the full Resend platform through a single integration. You can manage all aspects of your email infrastructure using natural language. Emails: Send, list, get, cancel, update, and batch send emails. Supports HTML, plain text, attachments (local file, URL, or base64), CC/BCC, reply-to, scheduling, tags, and topic-based sending. Received Emails: List and read inbound emails. List and download received email attachments. Templates: Create, list, get, update, publish, duplicate, and remove email templates. Supports composing template content and {{{VARIABLE}}} placeholders. Contacts: Create, list, get, update, and remove contacts. Manage segment memberships, topic subscriptions, and CSV contact imports. Supports custom contact properties. Broadcasts: Create, send, list, get, update, and remove broadcast campaigns. Supports scheduling, personalization placeholders, and preview text. Automations: Create, list, get, update, and remove automations. Review the runs of an automation. Events: Send events to trigger automations for a contact. Create, update, and remove event definitions. Domains: Create, list, get, update, remove, and verify sender domains. Configure tracking, TLS, and sending/receiving capabilities. Create and verify domain claims. Segments: Create, list, get, and remove audience segments. Topics: Create, list, get, update, and remove subscription topics. Contact Properties: Create, list, get, update, and remove custom contact attributes. API Keys: Create, list, and remove API keys. Webhooks: Create, list, get, update, and remove webhooks for event notifications. Logs: List and inspect API request logs, including full request and response bodies. Editor: Connect to (and disconnect from) the visual editor in the Resend dashboard, and read a draft's content while collaborating on broadcasts and templates.

Tools

add-contact-to-segment

ChatGPT

Add a contact to a segment in Resend (by contact ID or email).

cancel-email

ChatGPT

Cancel a scheduled email that has not yet been sent. Only works for emails that were scheduled using the scheduledAt parameter.

compose-broadcast

ChatGPT

Purpose: Set the TipTap JSON content of a broadcast, enabling it to be edited visually in the Resend dashboard editor. Automatically connects and disconnects from the editor. Can also update metadata (subject, preview text, name) in the same call. This is the recommended way to set email content. Content set via compose-broadcast can be visually edited by the user in the dashboard. Use this for newsletters and any broadcast where the user may want to refine the content. Workflow: get-tiptap-json-content (with include_schema: true) → compose-broadcast When to use: - After create-broadcast, to set the email body - When the user wants to write, edit, or style email content - When the user wants to collaborate on the email in the dashboard editor Important: Always call get-tiptap-json-content first to retrieve the existing TipTap JSON, then build your changes on top of it. Skipping this will overwrite all existing content. Note: Switching between compose (TipTap) and update (raw HTML) modes is lossy — some content or formatting may be lost. If the broadcast already has HTML content, ask the user before switching to compose mode.

compose-template

ChatGPT

Purpose: Set the TipTap JSON content of a template, enabling it to be edited visually in the Resend dashboard editor. Automatically connects and disconnects from the editor. Can also update metadata (subject, name) in the same call. This is the recommended way to set email content. Content set via compose-template can be visually edited by the user in the dashboard. Workflow: get-tiptap-json-content (with include_schema: true) → compose-template When to use: - After create-template, to set the email body - When the user wants to write, edit, or style email content - When the user wants to collaborate on the email in the dashboard editor Important: Always call get-tiptap-json-content first to retrieve the existing TipTap JSON, then build your changes on top of it. Skipping this will overwrite all existing content. Note: Switching between compose (TipTap) and update (raw HTML) modes is lossy — some content or formatting may be lost. If the template already has HTML content, ask the user before switching to compose mode.

connect-to-editor

ChatGPT

Purpose: Show agent presence in the Resend dashboard editor. Users will see an agent avatar while connected. When to use: - To signal to dashboard users that an AI agent is working on the content outside of compose workflows - Not needed before compose-broadcast or compose-template — get-tiptap-json-content connects automatically, and compose tools disconnect when done. Returns: Connection token and room ID.

create-api-key

ChatGPT

Create a new API key in Resend. The token is only shown once upon creation, so you MUST display it to the user.

create-automation

ChatGPT

Purpose: Create an automation workflow that triggers on events and executes a sequence of steps. When to use: - User wants to set up automated email sequences (welcome series, drip campaigns, re-engagement) - User wants to automate actions based on events (update contacts, add to segments) Workflow: manage-events (create event, if needed) → list-templates (to get template IDs) → get-template (to check if template has "from" and "subject" — if not, use list-domains to pick a verified domain for the step config) → create-automation → send-event (to test) Returns: Automation ID and dashboard link. The workflow is a JSON object with one key: "steps" — an array of step objects. Each step has: key (unique string), type, config, and either "next" (string|null) or "branches" (for branching steps). Use keys like: "trigger", "send_email_1", "delay_1", "condition_1", "wait_event_1". Step types trigger — starts the automation when an event fires (required, exactly one) config: { "eventName": "<event_name>" } Uses "next". send_email — send an email using a published template config: { "template": { "id": "<template_id>", "variables": { "<key>": "<value>" } }, "from": "Name <sender@example.com>", "subject": "Email subject", "replyTo": "<address>" } "from" and "subject" are resolved from the step config first, then fall back to the template. If neither provides a "from", the email will silently fail to send. If neither provides a "subject", the run will error. Best practice: always set "from" and "subject" on the step config so the automation is self-contained. Use list-domains to find verified domains for "from". "replyTo" and "variables" are optional. Variables can use { "var": "event.<field>" } or { "var": "contact.<field>" } for dynamic values. Uses "next". delay — pause the workflow config: { "duration": "<human-readable>" } Examples: "30 minutes", "1 hour", "2 days", "1 week". Max 30 days. Uses "next". condition — conditional split based on contact or event data config: A condition rule object: Single rule: { "type": "rule", "field": "event.<field>" or "contact.<field>", "operator": "<op>", "value": <value> } Compound: { "type": "and"|"or", "rules": [<rule>, ...] } Operators: eq, neq, gt, gte, lt, lte, contains, starts_with, ends_with, exists, is_empty. exists/is_empty do not require a value. Uses "branches": { "condition_met": "<step_key>", "condition_not_met": "<step_key_or_null>" } wait_for_event — pause until a specific event arrives or timeout config: { "eventName": "<event_name>", "timeout": "<human-readable>", "filterRule": <optional condition rule> } For email lifecycle events use "resend:email.<opened|clicked|bounced|delivered|complained|failed|suppressed>". Uses "branches": { "event_received": "<step_key>", "timeout": "<step_key_or_null>" } contact_update — update contact fields config: { "firstName": "<value>", "lastName": "<value>", "unsubscribed": true|false, "properties": { "<key>": "<value>" } } All fields optional. Values can use { "var": "event.<field>" } for dynamic data. Uses "next". contact_delete — remove the contact from the audience config: {} Uses "next". add_to_segment — add contact to a segment config: { "segmentId": "<segment_id>" } Uses "next". Rules 1. Every step must be reachable from the trigger via next/branches. 2. Terminal steps have "next": null (or null branch values). 3. The workflow must be tree-shaped — no merging branches back together. Example: Linear drip campaign { "steps": [ { "key": "trigger", "type": "trigger", "config": { "eventName": "user.created" }, "next": "send_email_1" }, { "key": "send_email_1", "type": "send_email", "config": { "template": { "id": "tmpl_123" }, "from": "Welcome <hello@example.com>", "subject": "Welcome!" }, "next": "delay_1" }, { "key": "delay_1", "type": "delay", "config": { "duration": "3 days" }, "next": "send_email_2" }, { "key": "send_email_2", "type": "send_email", "config": { "template": { "id": "tmpl_456" }, "from": "Welcome <hello@example.com>", "subject": "Getting started" }, "next": null …

create-broadcast

ChatGPT

Purpose: Create a broadcast campaign (one email sent to an entire segment). Defines subject, body, and segment; does NOT send yet. Use send-broadcast to send it. NOT for: Sending a one-off email to specific people (use send-email). Not for adding contacts (use create-contact). Returns: Broadcast ID. Use this ID with send-broadcast to send, or get-broadcast/update-broadcast to manage. When to use: - User wants to "email my list", "send a newsletter", "broadcast to my segment", "email all contacts in X" - Newsletter, announcement, or bulk message to one segment - Supports personalization: {{{FIRST_NAME}}}, {{{LAST_NAME}}}, {{{EMAIL}}}, {{{RESEND_UNSUBSCRIBE_URL}}} "All contacts" note: Broadcasts require a segment. There is no "all contacts" option in the API. If the user wants to send to all contacts, check list-segments for an existing segment that covers everyone. If none exists, suggest creating one with create-segment. Workflow: list-segments (if needed) → create-broadcast → get-tiptap-json-content (with include_schema: true) → compose-broadcast → send-broadcast. Content options after creating: - compose-broadcast (recommended): Sets TipTap content that the user can visually edit in the Resend dashboard. Use this when the user wants to collaborate on or refine the email in the editor. - update-broadcast with html/text: Sets static HTML/text content. Use this only when the user explicitly wants to set raw HTML. Switching between compose and html/text modes is lossy — some content or formatting may be lost. Ask the user before switching.

create-contact

ChatGPT

Create a new contact in Resend. Optionally assign to segments and configure topic subscriptions.

create-contact-import

ChatGPT

Bulk-import contacts from a CSV file into Resend. The import is processed asynchronously: this returns an import ID immediately, then use get-contact-import to poll its status and counts. Provide the CSV as raw text via content. Max file size 100MB.

create-contact-property

ChatGPT

Create a new contact property in Resend. A contact property is a custom attribute (e.g. "company_name", "plan_tier") that can be attached to contacts.

create-domain

ChatGPT

Create a new domain in Resend. Returns DNS records that must be configured with your DNS provider for verification. You MUST display the DNS records to the user so they can set them up.

create-domain-claim

ChatGPT

Start a claim for a domain another Resend account has already verified. The domain is recreated under your account with brand-new DKIM keys, so the previous account's DNS records cannot be reused. Returns a TXT record that MUST be added to your DNS to prove ownership. You MUST display the TXT record to the user. After they add it, use verify-domain-claim, then poll get-domain-claim until status is "completed".

create-segment

ChatGPT

Create a new segment in Resend. A segment is a group of contacts that can be used to target specific broadcasts.

create-template

ChatGPT

Create a new email template in Resend. Templates are created in draft status. Use publish-template to make them available for sending. Variables use triple-brace syntax in HTML: {{{VAR_NAME}}}. Workflow: create-template → get-tiptap-json-content (with include_schema: true) → compose-template → publish-template. Content options after creating: - compose-template (recommended): Sets TipTap content that the user can visually edit in the Resend dashboard. Use this when the user wants to collaborate on or refine the template in the editor. - update-template with html/text: Sets static HTML/text content. Use this only when the user explicitly wants to set raw HTML. Switching between compose and html/text modes is lossy — some content or formatting may be lost. Ask the user before switching.

create-topic

ChatGPT

Create a new topic in Resend. Topics allow contacts to manage their subscription preferences for different types of emails.

create-webhook

ChatGPT

Create a new webhook in Resend. A webhook allows you to receive notifications at a specified URL when certain events occur (e.g. email.sent, email.delivered, email.bounced).

disconnect-from-editor

ChatGPT

Remove agent presence from the Resend dashboard editor. Call this when done editing.

duplicate-template

ChatGPT

Duplicate an existing email template in Resend. Creates a new draft copy of the template with a new ID. Accepts a template ID, alias, or Resend dashboard URL.

get-automation

ChatGPT

Purpose: Get details of a specific automation (with its workflow) or list all automations. Modes: - With id: Returns full automation details including the workflow definition. - Without id: Lists all automations with optional status filter and pagination. When to use: - User asks "show me my automations" or "what automations do I have?" - User wants to inspect a specific automation's workflow - Before update-automation, to see the current workflow

get-automation-runs

ChatGPT

Purpose: List runs for an automation, or get details of a specific run. Modes: - With runId: Returns detailed run info with step-by-step execution status, outputs, and errors. - Without runId: Lists runs for the automation with optional status filter. When to use: - User wants to see if an automation is working - User wants to debug a failed automation run - User asks "why did this automation fail?" or "show me recent runs" Run statuses: running, completed, failed, cancelled Step statuses: pending, running, completed, failed, skipped, waiting

get-broadcast

ChatGPT

Retrieve full details of a specific broadcast by ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>), including HTML and plain text content.

get-contact

ChatGPT

Get a contact by ID or email from Resend.

get-contact-import

ChatGPT

Get the status and counts of a contact import by ID. Use after create-contact-import to track progress (queued, in_progress, completed, failed).

get-contact-property

ChatGPT

Get a contact property by ID from Resend.

get-domain

ChatGPT

Get a domain by ID from Resend. Returns full domain details including DNS records needed for verification.

get-domain-claim

ChatGPT

Retrieve the latest claim for a domain by its placeholder Domain ID (the domain_id from create-domain-claim). Returns claim status and the TXT record needed to prove ownership. Poll until status is "completed".

get-email

ChatGPT

Retrieve full details of a specific sent transactional email by ID, including HTML and plain text content.

get-log

ChatGPT

Purpose: Get detailed information about a specific API request log, including the full request and response bodies. Returns: Log details: id, created_at, endpoint, method, response_status, user_agent, request_body, response_body. When to use: - User wants to inspect a specific API request - Debugging a particular API call - User says "show me that log", "what was in that request?"

get-received-email

ChatGPT

Retrieve full details of a specific received email by ID, including HTML and plain text content, headers, and raw email download URL.

get-received-email-attachment

ChatGPT

Retrieve details of a specific attachment from a received email, including a time-limited download URL.

get-segment

ChatGPT

Get a segment by ID from Resend.

get-sent-email-attachment

ChatGPT

Retrieve details of a specific attachment from a sent email, including a time-limited download URL.

get-template

ChatGPT

Get an email template by ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>) from Resend. Returns full template details including HTML content, variables, and publish status.

get-tiptap-json-content

ChatGPT

Purpose: Retrieve the existing TipTap JSON content of a broadcast or template, optionally bundled with the TipTap schema reference. Also connects the agent to the editor so the avatar is visible while content is being generated. When to use: - Always call this before compose-broadcast or compose-template to fetch the current document state — even if you expect it to be empty, the resource may have content set via the dashboard - When the user asks to edit, tweak, or modify existing email content - To inspect the current TipTap structure of a resource Returns: The TipTap JSON content object for the resource, and optionally the TipTap schema. Use the content as the base for modifications, then pass the updated JSON to compose-broadcast or compose-template. Note: This tool automatically connects the agent to the editor. The subsequent compose-broadcast or compose-template call will disconnect when done. Tip: Set include_schema to true to get both the existing content and the schema in one call.

get-topic

ChatGPT

Get a topic by ID from Resend.

get-webhook

ChatGPT

Get a webhook by ID from Resend.

list-api-keys

ChatGPT

List all API keys from Resend. Returns API key names, IDs, and creation dates. Don't bother telling the user the IDs or creation dates unless they ask for them.

list-broadcasts

ChatGPT

Purpose: List all broadcast campaigns (newsletters/bulk emails to audiences) with ID, name, audience, status, timestamps. NOT for: Listing transactional emails (use list-emails). Not for listing segments or contacts (use list-segments, list-contacts). Returns: For each broadcast: id, name, segment_id, status, created_at, scheduled_at, sent_at. When to use: User asks "show my broadcasts", "what newsletters did I send?", "list campaigns". Use get-broadcast for full details of one.

list-contact-imports

ChatGPT

List contact imports from Resend. Optionally filter by status. Use to discover import IDs or review past imports.

list-contact-properties

ChatGPT

List all contact properties from Resend. This tool is useful for getting property IDs and seeing which custom attributes are configured. If you need a contact property ID, you MUST use this tool to get all available properties and then ask the user to select the one they want. Don't bother telling the user the IDs or creation dates unless they ask for them.

list-contact-segments

ChatGPT

List all segments a contact belongs to in Resend (by contact ID or email). Don't bother telling the user the IDs or creation dates unless they ask for them.

list-contact-topics

ChatGPT

List all topic subscriptions for a contact in Resend (by contact ID or email). Don't bother telling the user the IDs unless they ask for them.

list-contacts

ChatGPT

Purpose: List contacts from Resend. Optionally filter by segment. Use to discover contact IDs or emails. NOT for: Listing segments (use list-segments). Not for listing sent emails (use list-emails) or broadcasts (use list-broadcasts). Returns: For each contact: id, email, first_name, last_name, unsubscribed, created_at. When to use: User asks "who's in this list?", "show contacts", "who did I add?" Don't bother telling the user the IDs, unsubscribe statuses, or creation dates unless they ask for them.

list-domains

ChatGPT

List all domains from Resend. Returns domain names, statuses, regions, and capabilities. Don't bother telling the user the IDs unless they ask for them.

list-emails

ChatGPT

Purpose: List recently sent emails (transactional emails sent via send-email) with metadata: recipient, subject, status, timestamps. NOT for: Listing broadcast campaigns (use list-broadcasts). Not for composing or sending. Returns: Paginated list with to, subject, status, created_at, and ID per email. When to use: - User asks "what emails were sent?", "show recent emails", "did my email go out?" - Checking delivery status of sent messages - Finding an email ID to fetch full content (then use get-email) Workflow: list-emails → get-email( id ) when user needs full body or details.

list-logs

ChatGPT

Purpose: List API request logs for the account. Use to review recent API activity, debug issues, or audit API usage. Returns: For each log: id, created_at, endpoint, method, response_status, user_agent. Use pagination (limit, after/before) for large lists. When to use: - User wants to see recent API activity - Debugging API issues or checking request history - User says "show my logs", "what API calls were made?", "check recent requests"

list-oauth-grants

ChatGPT

List OAuth grants for the team — the apps authorized to act on the team's behalf. Returns every grant, active and revoked; a grant with a non-null revoked_at is no longer active. Each grant includes the client (app) name, scopes, and creation date. Don't bother telling the user the IDs unless they ask for them.

list-received-email-attachments

ChatGPT

List all attachments from a specific received (inbox) email. Returns attachment metadata including filename, size, content type, and a time-limited download URL. Use for emails listed by list-received-emails.

list-received-emails

ChatGPT

Purpose: List emails received (inbox) by your Resend receiving address. Use for "show my inbox", "what emails did I get?", "list incoming mail". NOT for: Listing emails you sent (use list-emails). Not for listing broadcasts (use list-broadcasts). Returns: Paginated metadata: from, to, subject, received time. Use get-received-email with an ID for full content.

list-segments

ChatGPT

Purpose: List all segments in the account. Use to get segment IDs required by create-contact, create-broadcast, list-contacts. NOT for: Listing contacts inside a segment (use list-contacts with segmentId). Not for listing broadcasts (use list-broadcasts). Returns: For each segment: name, id, created_at. Use pagination (limit, after/before) for large lists. When to use: User says "show my segments", "what lists do I have?", or before create-contact/create-broadcast when segmentId is unknown.

list-sent-email-attachments

ChatGPT

List all attachments from a specific sent email (from send-email or list-emails). Returns attachment metadata including filename, size, content type, and a time-limited download URL.

list-templates

ChatGPT

List all email templates from Resend. Returns template names, statuses, and aliases. Don't bother telling the user the IDs unless they ask for them.

list-topics

ChatGPT

List all topics from Resend. This tool is useful for getting topic IDs to use with other tools like send-email.

list-webhooks

ChatGPT

List all webhooks from Resend. Use to get webhook IDs and see which endpoints and events are configured. Not for listing emails, segments, or broadcasts.

manage-events

ChatGPT

Purpose: Create, list, get, update, or remove event definitions in Resend. Events define named triggers that your application sends to start automations. Each event can have an optional schema that validates payload data. Actions: - create: Define a new event with a name and optional schema. - list: List all event definitions (paginated). - get: Get event details by ID or name. - update: Update an event's schema. - remove: Delete an event. You MUST confirm with the user before removing. Workflow: manage-events (create) → create-automation → send-event Schema types: string, number, boolean, date

publish-template

ChatGPT

Publish an email template in Resend. Templates must be published before they can be used for sending emails. Re-publishing a previously published template makes the latest changes live. Accepts a template ID, alias, or Resend dashboard URL.

remove-api-key

ChatGPT

Remove an API key by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this API key. Reference the NAME of the API key when double-checking, and warn the user that removing an API key is irreversible and any services using it will lose access. You may only use this tool if the user explicitly confirms they want to remove the API key after you double-check.

remove-automation

ChatGPT

Remove an automation by ID or Resend dashboard URL. Before using this tool, you MUST double-check with the user that they want to remove this automation. Reference the NAME of the automation when confirming, and warn the user that removal is irreversible and will stop all future runs. You may only use this tool if the user explicitly confirms.

remove-broadcast

ChatGPT

Remove a broadcast by ID or Resend dashboard URL. Before using this tool, you MUST double-check with the user that they want to remove this broadcast. Reference the NAME of the broadcast when double-checking, and warn the user that removing a broadcast is irreversible. You may only use this tool if the user explicitly confirms they want to remove the broadcast after you double-check.

remove-contact

ChatGPT

Remove a contact from Resend (by ID or email). Before using this tool, you MUST double-check with the user that they want to remove this contact. Reference the contact's name (if present) and email address when double-checking, and warn the user that removing a contact is irreversible. You may only use this tool if the user explicitly confirms they want to remove the contact after you double-check.

remove-contact-from-segment

ChatGPT

Remove a contact from a segment in Resend (by contact ID or email). Before using this tool, you MUST double-check with the user that they want to remove the contact from the segment.

remove-contact-property

ChatGPT

Remove a contact property by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this contact property. Reference the KEY of the property when double-checking, and warn the user that removing a contact property is irreversible and will remove the property from all contacts. You may only use this tool if the user explicitly confirms they want to remove the contact property after you double-check.

remove-domain

ChatGPT

Remove a domain by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this domain. Reference the NAME of the domain when double-checking, and warn the user that removing a domain is irreversible and will stop all email sending/receiving for that domain. You may only use this tool if the user explicitly confirms they want to remove the domain after you double-check.

remove-segment

ChatGPT

Remove a segment by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this segment. Reference the NAME of the segment when double-checking, and warn the user that removing a segment is irreversible. You may only use this tool if the user explicitly confirms they want to remove the segment after you double-check.

remove-template

ChatGPT

Remove an email template by ID, alias, or Resend dashboard URL from Resend. Before using this tool, you MUST double-check with the user that they want to remove this template. Reference the NAME of the template when double-checking, and warn the user that removing a template is irreversible. You may only use this tool if the user explicitly confirms they want to remove the template after you double-check.

remove-topic

ChatGPT

Remove a topic by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this topic. Reference the NAME of the topic when double-checking, and warn the user that removing a topic is irreversible. You may only use this tool if the user explicitly confirms they want to remove the topic after you double-check.

remove-webhook

ChatGPT

Remove a webhook by ID from Resend. Before using this tool, you MUST double-check with the user that they want to remove this webhook. Reference the ENDPOINT of the webhook when double-checking, and warn the user that removing a webhook is irreversible. You may only use this tool if the user explicitly confirms they want to remove the webhook after you double-check.

revoke-oauth-grant

ChatGPT

Revoke an OAuth grant by ID. Before using this tool, you MUST double-check with the user that they want to revoke this grant. Reference the NAME of the app (client) when double-checking, and warn the user that revocation is immediate and irreversible — every access and refresh token issued under the grant stops working, and the app would need to be re-authorized to regain access. You may only use this tool if the user explicitly confirms they want to revoke the grant after you double-check.

send-batch-emails

ChatGPT

Purpose: Send up to 100 transactional emails in one API call. Each item has the same fields as send-email (to, subject, text, from, etc.). NOT for: Sending one email (use send-email) or the same content to a segment (use create-broadcast + send-broadcast). When to use: User wants to send many individual emails in bulk (e.g. 50 password resets, 100 receipts). Not for one-to-many broadcasts.

send-broadcast

ChatGPT

Purpose: Send (or schedule) an existing broadcast by ID. The broadcast must have been created with create-broadcast first. NOT for: Sending a new one-off email (use send-email). Not for creating the broadcast content (use create-broadcast). Returns: Send confirmation and broadcast ID. When to use: - User has created a broadcast and says "send it", "go ahead and send", "schedule this for tomorrow" - After create-broadcast; call send-broadcast with the returned ID to deliver to the audience - Optional scheduledAt: natural language or ISO 8601 for scheduled send Workflow: create-broadcast → send-broadcast. Use list-broadcasts to find existing draft/sent broadcasts.

send-email

ChatGPT

Purpose: Send a single transactional email to one or more recipients immediately (or schedule it). Use for one-off messages, notifications, and direct replies. NOT for: Sending the same email to a whole list/audience (use create-broadcast + send-broadcast). Not for managing contacts or audiences. Returns: Send confirmation and email ID. When to use: - User wants to "send an email" to specific people (names or addresses) - One-off messages: password reset, order confirmation, receipt, alert - User says "email this to X", "notify them", "send a message to..." - Scheduling a single email for later Workflow: Get recipient(s) and content from user → send-email. Use list-emails or get-email to check delivery status afterward. Key trigger phrases: "Send an email", "Email this to", "Notify", "Send a message", "Reply to them", "Schedule an email"

send-event

ChatGPT

Purpose: Fire an event to trigger automations for a specific contact. When to use: - User wants to trigger an automation workflow for a contact - Testing an automation by sending a test event Workflow: create-event (if needed) → create-automation (if needed) → send-event Important: - The event name must match the trigger event name in an automation for it to fire. - Identify the contact by either contactId OR email, not both. - The payload is optional and can contain any key-value data that the automation steps can reference via event.* variables.

update-automation

ChatGPT

Purpose: Update an automation's name, status, or workflow. When to use: - User wants to rename an automation - User wants to enable or disable an automation (use status: "disabled" to stop it) - User wants to modify the workflow steps Important: - To disable/stop an automation, set status to "disabled". Existing runs will continue to completion. - When updating the workflow, provide the complete new workflow — it replaces the existing one. - Use get-automation first to see the current workflow before making changes. The workflow is a JSON object with one key: "steps" — an array of step objects. Each step has: key (unique string), type, config, and either "next" (string|null) or "branches" (for branching steps). Use keys like: "trigger", "send_email_1", "delay_1", "condition_1", "wait_event_1". Step types trigger — starts the automation when an event fires (required, exactly one) config: { "eventName": "<event_name>" } Uses "next". send_email — send an email using a published template config: { "template": { "id": "<template_id>", "variables": { "<key>": "<value>" } }, "from": "Name <sender@example.com>", "subject": "Email subject", "replyTo": "<address>" } "from" and "subject" are resolved from the step config first, then fall back to the template. If neither provides a "from", the email will silently fail to send. If neither provides a "subject", the run will error. Best practice: always set "from" and "subject" on the step config so the automation is self-contained. Use list-domains to find verified domains for "from". "replyTo" and "variables" are optional. Variables can use { "var": "event.<field>" } or { "var": "contact.<field>" } for dynamic values. Uses "next". delay — pause the workflow config: { "duration": "<human-readable>" } Examples: "30 minutes", "1 hour", "2 days", "1 week". Max 30 days. Uses "next". condition — conditional split based on contact or event data config: A condition rule object: Single rule: { "type": "rule", "field": "event.<field>" or "contact.<field>", "operator": "<op>", "value": <value> } Compound: { "type": "and"|"or", "rules": [<rule>, ...] } Operators: eq, neq, gt, gte, lt, lte, contains, starts_with, ends_with, exists, is_empty. exists/is_empty do not require a value. Uses "branches": { "condition_met": "<step_key>", "condition_not_met": "<step_key_or_null>" } wait_for_event — pause until a specific event arrives or timeout config: { "eventName": "<event_name>", "timeout": "<human-readable>", "filterRule": <optional condition rule> } For email lifecycle events use "resend:email.<opened|clicked|bounced|delivered|complained|failed|suppressed>". Uses "branches": { "event_received": "<step_key>", "timeout": "<step_key_or_null>" } contact_update — update contact fields config: { "firstName": "<value>", "lastName": "<value>", "unsubscribed": true|false, "properties": { "<key>": "<value>" } } All fields optional. Values can use { "var": "event.<field>" } for dynamic data. Uses "next". contact_delete — remove the contact from the audience config: {} Uses "next". add_to_segment — add contact to a segment config: { "segmentId": "<segment_id>" } Uses "next". Rules 1. Every step must be reachable from the trigger via next/branches. 2. Terminal steps have "next": null (or null branch values). 3. The workflow must be tree-shaped — no merging branches back together. Example: Linear drip campaign { "steps": [ { "key": "trigger", "type": "trigger", "config": { "eventName": "user.created" }, "next": "send_email_1" }, { "key": "send_email_1", "type": "send_email", "config": { "template": { "id": "tmpl_123" }, "from": "Welcome <hello@example.com>", "subject": "Welcome!" }, "next": "delay_1" }, { "key": "delay_1", "type": "delay", "config": { "duration": "3 days" }, "next": "send_email_2" }, { "key": "send_email_2", "type": "send_email", "config": { "template": { "id": "tmpl_456" }, "from": "Welcome <hello@example.com>", "subject": "Getting started" }, "next": null } ] } Example: Re-engagement with wait_for_event { "steps": [ { "key": "trigger",…

update-broadcast

ChatGPT

Update broadcast metadata by ID or Resend dashboard URL (name, subject, from, html, text, segment, preview text, reply-to). To edit TipTap content, use compose-broadcast instead. Important: The API requires from and segmentId to be set on the broadcast. If the broadcast was created from the dashboard, these may be empty. Always call get-broadcast first to check, and include from and segmentId in your update if they are not already set. Use list-domains to find verified domains for the from address, and list-segments to find segment IDs. Note on html/text fields: Setting html or text via this tool replaces any content previously set via compose-broadcast. This switch is lossy — some content or formatting may be lost. Prefer compose-broadcast for content changes. If the broadcast was composed with TipTap content, ask the user before overwriting it with raw HTML.

update-contact

ChatGPT

Update a contact in Resend (by ID or email).

update-contact-property

ChatGPT

Update an existing contact property in Resend. Only the fallback value can be changed — the key and type cannot be modified after creation.

update-contact-topics

ChatGPT

Update topic subscriptions for a contact in Resend (by contact ID or email).

update-domain

ChatGPT

Update an existing domain in Resend. Allows changing tracking settings, TLS mode, and capabilities.

update-email

ChatGPT

Reschedule a scheduled email by updating its scheduled send time. Only works for emails that were scheduled and have not yet been sent.

update-template

ChatGPT

Update template metadata by ID, alias, or Resend dashboard URL (name, subject, from, html, variables, etc.). After updating a published template, use publish-template again to make the changes live. To edit TipTap content, use compose-template instead. Note on html/text fields: Setting html or text via this tool replaces any content previously set via compose-template. This switch is lossy — some content or formatting may be lost. Prefer compose-template for content changes. If the template was composed with TipTap content, ask the user before overwriting it with raw HTML.

update-topic

ChatGPT

Update an existing topic in Resend. Note: defaultSubscription cannot be modified after creation.

update-webhook

ChatGPT

Update an existing webhook in Resend. You can change the endpoint URL, subscribed events, or enable/disable the webhook.

verify-domain

ChatGPT

Trigger domain verification in Resend. This starts an asynchronous verification process that checks if the DNS records are correctly configured. The domain status will temporarily show as "pending" during verification.

verify-domain-claim

ChatGPT

Trigger asynchronous DNS verification and ownership transfer for a domain claim, using the placeholder Domain ID. The claim stays "pending" while verification runs; poll get-domain-claim for status. Once "completed", the transferred domain has NEW DKIM records — fetch them with get-domain, add them to DNS, then run verify-domain.

add-contact-to-segment

Claude

cancel-email

Claude

compose-broadcast

Claude

compose-template

Claude

connect-to-editor

Claude

create-api-key

Claude

create-automation

Claude

create-broadcast

Claude

create-contact

Claude

create-contact-import

Claude

create-contact-property

Claude

create-domain

Claude

create-domain-claim

Claude

create-segment

Claude

create-template

Claude

create-topic

Claude

create-webhook

Claude

disconnect-from-editor

Claude

duplicate-template

Claude

get-automation

Claude

get-automation-runs

Claude

get-broadcast

Claude

get-contact

Claude

get-contact-import

Claude

get-contact-property

Claude

get-domain

Claude

get-domain-claim

Claude

get-email

Claude

get-log

Claude

get-received-email

Claude

get-received-email-attachment

Claude

get-segment

Claude

get-sent-email-attachment

Claude

get-template

Claude

get-tiptap-json-content

Claude

get-topic

Claude

get-webhook

Claude

list-api-keys

Claude

list-broadcasts

Claude

list-contact-imports

Claude

list-contact-properties

Claude

list-contact-segments

Claude

list-contact-topics

Claude

list-contacts

Claude

list-domains

Claude

list-emails

Claude

list-logs

Claude

list-oauth-grants

Claude

list-received-email-attachments

Claude

list-received-emails

Claude

list-segments

Claude

list-sent-email-attachments

Claude

list-templates

Claude

list-topics

Claude

list-webhooks

Claude

manage-events

Claude

publish-template

Claude

remove-api-key

Claude

remove-automation

Claude

remove-broadcast

Claude

remove-contact

Claude

remove-contact-from-segment

Claude

remove-contact-property

Claude

remove-domain

Claude

remove-segment

Claude

remove-template

Claude

remove-topic

Claude

remove-webhook

Claude

revoke-oauth-grant

Claude

send-batch-emails

Claude

send-broadcast

Claude

send-email

Claude

send-event

Claude

update-automation

Claude

update-broadcast

Claude

update-contact

Claude

update-contact-property

Claude

update-contact-topics

Claude

update-domain

Claude

update-email

Claude

update-template

Claude

update-topic

Claude

update-webhook

Claude

verify-domain

Claude

verify-domain-claim

Claude

Links

Documentation ↗Privacy Policy ↗

App Stats

170

Tools

ChatGPT, Claude

Platforms