The Resend MCP connector routes your AI agent's tool calls to Resend's own MCP server through Scalekit. Each user connects their own Resend access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 94 tools.
- Tools
- 94
- What they doRead · write · destructive
- 38 · 37 · 1938 read37 write19 destructive
- Users sign in with
- Access token
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Resend MCP connection
In AgentKit > Connections, create a Resend MCP connection. The name you give it is the
connection_nameyour code passes. See Configure connections.Authorize a user and make your first call
quickstart.mts import { ScalekitClient } from '@scalekit-sdk/node'import 'dotenv/config'import { createInterface } from 'node:readline/promises'const scalekit = new ScalekitClient(process.env.SCALEKIT_ENVIRONMENT_URL,process.env.SCALEKIT_CLIENT_ID,process.env.SCALEKIT_CLIENT_SECRET,)const actions = scalekit.actionsconst connector = 'resendmcp'const identifier = 'user_123'// Generate an authorization link for the userconst { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })console.log('Authorize Resend MCP:', link)const rl = createInterface({ input: process.stdin, output: process.stdout })await rl.question('Press Enter after authorizing...')rl.close()// Make your first callconst result = await actions.executeTool({connector,identifier,toolName: 'resendmcp_get_automation',toolInput: {},})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_dotenv()scalekit_client = ScalekitClient(env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),client_id=os.getenv("SCALEKIT_CLIENT_ID"),client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),)actions = scalekit_client.actionsconnection_name = "resendmcp"identifier = "user_123"# Generate an authorization link for the userlink_response = actions.get_authorization_link(connection_name=connection_name,identifier=identifier,)print("Authorize Resend MCP:", link_response.link)input("Press Enter after authorizing...")# Make your first callresult = actions.execute_tool(tool_input={},tool_name="resendmcp_get_automation",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user opens the link once and enters their Resend credentials there. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_toolresendmcp_get_automation**Purpose:** Get details of a specific automation (with its workflow) or list all automations.Read-onlyGet Automation
**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
Inputs
afterstring- Cursor for forward pagination (for list mode).
beforestring- Cursor for backward pagination (for list mode).
idstring- Automation ID or Resend dashboard URL (e.g. https://resend.com/automations/<id>). If omitted, lists all automations.
limitnumber- Number of automations to retrieve (for list mode).
statusstring- Filter by status (for list mode only).one of
enableddisabled
resendmcp_get_automation_runs**Purpose:** List runs for an automation, or get details of a specific run.Read-onlyGet Automation Runs
**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
Inputs
automationIdstringrequired- The automation ID or Resend dashboard URL (e.g. https://resend.com/automations/<id>)
afterstring- Cursor for forward pagination (for list mode).
beforestring- Cursor for backward pagination (for list mode).
limitnumber- Number of runs to retrieve (for list mode).
runIdstring- Specific run ID to get details for. If omitted, lists all runs.
statusstring- Filter runs by status (for list mode only).one of
runningcompletedfailedcancelled
resendmcp_get_broadcastRetrieve full details of a specific broadcast by ID or Resend dashboard URL (e.g.Read-onlyGet Broadcast
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.
Inputs
broadcastIdstringrequired- Broadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)
resendmcp_get_contactGet a contact by ID or email from Resend.Read-onlyGet Contact
Get a contact by ID or email from Resend.
Inputs
emailstring- Contact email address
idstring- Contact ID
resendmcp_get_contact_importGet the status and counts of a contact import by ID.Read-onlyGet Contact Import
Get the status and counts of a contact import by ID. Use after create-contact-import to track progress (queued, in_progress, completed, failed).
Inputs
idstringrequired- Contact import ID
resendmcp_get_contact_propertyGet a contact property by ID from Resend.Read-onlyGet Contact Property
Get a contact property by ID from Resend.
Inputs
contactPropertyIdstringrequired- Contact property ID
resendmcp_get_domainGet a domain by ID from Resend.Read-onlyGet Domain
Get a domain by ID from Resend. Returns full domain details including DNS records needed for verification.
Inputs
idstringrequired- Domain ID
resendmcp_get_domain_claimRetrieve the latest claim for a domain by its placeholder Domain ID (the domain_id from create-domain-claim).Read-onlyGet Domain Claim
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".
Inputs
idstringrequired- The placeholder Domain ID created by the claim
resendmcp_get_emailRetrieve full details of a specific sent transactional email by ID, including message_id, HTML and plain text content.Read-onlyGet Email
Retrieve full details of a specific sent transactional email by ID, including message_id, HTML and plain text content.
Inputs
idstringrequired- The email ID to retrieve
resendmcp_get_log**Purpose:** Get detailed information about a specific API request log, including the full request and response bodies.Read-onlyGet Log
**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?"
Inputs
logIdstringrequired- The Log ID to retrieve
resendmcp_get_received_emailRetrieve full details of a specific received email by ID, including HTML and plain text content, headers, and raw email download URL.Read-onlyGet Received Email
Retrieve full details of a specific received email by ID, including HTML and plain text content, headers, and raw email download URL.
Inputs
idstringrequired- The received email ID to retrieve
resendmcp_get_received_email_attachmentRetrieve details of a specific attachment from a received email, including a time-limited download URL.Read-onlyGet Received Email Attachment
Retrieve details of a specific attachment from a received email, including a time-limited download URL.
Inputs
emailIdstringrequired- The received email ID
idstringrequired- The attachment ID
resendmcp_get_segmentGet a segment by ID from Resend.Read-onlyGet Segment
Get a segment by ID from Resend.
Inputs
idstringrequired- Segment ID
resendmcp_get_sent_email_attachmentRetrieve details of a specific attachment from a sent email, including a time-limited download URL.Read-onlyGet Sent Email Attachment
Retrieve details of a specific attachment from a sent email, including a time-limited download URL.
Inputs
emailIdstringrequired- The sent email ID
idstringrequired- The attachment ID
resendmcp_get_suppressionGet a suppression list entry by ID or email address from Resend.Read-onlyGet Suppression
Get a suppression list entry by ID or email address from Resend. Use this to check whether a specific address is suppressed and why (origin: bounce, complaint, or manual).
Inputs
idOrEmailstringrequired- Suppression ID or email address
resendmcp_get_templateGet an email template by ID, alias, or Resend dashboard URL (e.g.Read-onlyGet Template
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.
Inputs
idstringrequired- The template ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>)
resendmcp_get_tiptap_json_content**Purpose:** Retrieve the existing TipTap JSON content of a broadcast or template, optionally bundled with the TipTap schema reference.Read-onlyGet TipTap JSON Content
**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.
Inputs
resource_idstringrequired- The broadcast ID (UUID), template identifier (UUID or alias), or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id> or https://resend.com/templates/<id>)
resource_typestringrequired- Type of resource to fetch content forone of
broadcasttemplate include_schemaboolean- Returns the TipTap schema reference alongside the content. Required for producing valid TipTap JSON. Set to false only if you already have the schema.default
true
resendmcp_get_topicGet a topic by ID from Resend.Read-onlyGet Topic
Get a topic by ID from Resend.
Inputs
idstringrequired- Topic ID
resendmcp_get_webhookGet a webhook by ID from Resend.Read-onlyGet Webhook
Get a webhook by ID from Resend.
Inputs
webhookIdstringrequired- Webhook ID
resendmcp_list_api_keysList all API keys from Resend.Read-onlyList API Keys
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.
Inputs
afterstring- API key ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- API key ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of API keys to retrieve. Max: 100, Min: 1
resendmcp_list_broadcasts**Purpose:** List all broadcast campaigns (newsletters/bulk emails to audiences) with ID, name, audience, status, timestamps.Read-onlyList Broadcasts
**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.
Inputs
This tool takes no inputs.
resendmcp_list_contact_importsList contact imports from Resend.Read-onlyList Contact Imports
List contact imports from Resend. Optionally filter by status. Use to discover import IDs or review past imports.
Inputs
afterstring- Contact import ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Contact import ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of contact imports to retrieve. Default: 10, Max: 100, Min: 1
statusstring- Filter imports by status.one of
queuedin_progresscompletedfailed
resendmcp_list_contact_propertiesList all contact properties from Resend.Read-onlyList Contact Properties
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.
Inputs
afterstring- Contact property ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Contact property ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of contact properties to retrieve. Default: 20, Max: 100, Min: 1
resendmcp_list_contact_segmentsList all segments a contact belongs to in Resend (by contact ID or email).Read-onlyList Contact Segments
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.
Inputs
afterstring- Segment ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Segment ID before which to retrieve more (for backward pagination). Cannot be used with "after".
contactIdstring- Contact ID
emailstring- Contact email address
limitnumber- Number of segments to retrieve. Max: 100, Min: 1. If omitted, all segments are returned.
resendmcp_list_contact_topicsList all topic subscriptions for a contact in Resend (by contact ID or email).Read-onlyList Contact Topics
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.
Inputs
afterstring- Topic ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Topic ID before which to retrieve more (for backward pagination). Cannot be used with "after".
emailstring- Contact email address
idstring- Contact ID
limitnumber- Number of topics to retrieve. Default: 20, Max: 100, Min: 1default
20
resendmcp_list_contacts**Purpose:** List contacts from Resend.Read-onlyList Contacts
**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.
Inputs
afterstring- Contact ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Contact ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of contacts to retrieve. Default: 20, Max: 100, Min: 1default
20 segmentIdstring- Segment ID to filter by. If provided, only contacts in this segment will be returned.
resendmcp_list_domainsList all domains from Resend.Read-onlyList Domains
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.
Inputs
afterstring- Domain ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Domain ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of domains to retrieve. Default: 20, Max: 100, Min: 1default
20
resendmcp_list_emails**Purpose:** List recently sent emails (transactional emails sent via send-email) with metadata: recipient, subject, status, timestamps.Read-onlyList Emails
**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, message_id, 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.
Inputs
afterstring- Email ID after which to retrieve more emails (for forward pagination). Cannot be used with "before".
beforestring- Email ID before which to retrieve more emails (for backward pagination). Cannot be used with "after".
limitnumber- Number of emails to retrieve. Default: 20, Max: 100, Min: 1default
20
resendmcp_list_logs**Purpose:** List API request logs for the account.Read-onlyList Logs
**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"
Inputs
afterstring- Log ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Log ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of logs to retrieve. Default: 20, Max: 100, Min: 1
resendmcp_list_oauth_grantsList OAuth grants for the team — the apps authorized to act on the team's behalf.Read-onlyList OAuth Grants
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.
Inputs
afterstring- OAuth grant ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- OAuth grant ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of OAuth grants to retrieve. Max: 100, Min: 1
resendmcp_list_received_email_attachmentsList all attachments from a specific received (inbox) email.Read-onlyList Received Email Attachments
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.
Inputs
emailIdstringrequired- The received email ID
afterstring- Attachment ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Attachment ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of attachments to retrieve. Default: 20, Max: 100, Min: 1
resendmcp_list_received_emails**Purpose:** List emails received (inbox) by your Resend receiving address.Read-onlyList Received Emails
**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, message_id, received time. Use get-received-email with an ID for full content.
Inputs
afterstring- Email ID after which to retrieve more emails (for forward pagination). Cannot be used with "before".
beforestring- Email ID before which to retrieve more emails (for backward pagination). Cannot be used with "after".
limitnumber- Number of emails to retrieve. Default: 20, Max: 100, Min: 1
resendmcp_list_segments**Purpose:** List all segments in the account.Read-onlyList Segments
**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.
Inputs
afterstring- Segment ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Segment ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of segments to retrieve. Default: 20, Max: 100, Min: 1
resendmcp_list_sent_email_attachmentsList all attachments from a specific sent email (from send-email or list-emails).Read-onlyList Sent Email Attachments
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.
Inputs
emailIdstringrequired- The sent email ID
afterstring- Attachment ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Attachment ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of attachments to retrieve. Default: 20, Max: 100, Min: 1
resendmcp_list_suppressions**Purpose:** List email addresses on the suppression list.Read-onlyList Suppressions
**Purpose:** List email addresses on the suppression list. Suppressed addresses never receive emails from the account. Optionally filter by origin: "bounce" (added automatically after a hard bounce), "complaint" (added automatically after a spam complaint), or "manual" (added via the API or dashboard). **NOT for:** Checking a single address (use get-suppression). Not for listing contacts (use list-contacts). **Returns:** For each suppression: email, id, origin, source_id (when present), created_at. Use pagination (limit, after/before) for large lists. **When to use:** User says "show my suppression list", "who is suppressed?", or "why isn't this person receiving emails?" combined with a broad look at suppressed addresses.
Inputs
afterstring- Suppression ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Suppression ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of suppressions to retrieve. Default: 20, Max: 100, Min: 1
originstring- Only return suppressions with this origin: "bounce", "complaint", or "manual".one of
bouncecomplaintmanual
resendmcp_list_templatesList all email templates from Resend.Read-onlyList Templates
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.
Inputs
afterstring- Template ID after which to retrieve more (for forward pagination). Cannot be used with "before".
beforestring- Template ID before which to retrieve more (for backward pagination). Cannot be used with "after".
limitnumber- Number of templates to retrieve. Default: 20, Max: 100, Min: 1
resendmcp_list_topicsList all topics from Resend.Read-onlyList Topics
List all topics from Resend. This tool is useful for getting topic IDs to use with other tools like send-email.
Inputs
This tool takes no inputs.
resendmcp_list_webhooksList all webhooks from Resend.Read-onlyList Webhooks
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.
Inputs
This tool takes no inputs.
resendmcp_add_contact_to_segmentAdd a contact to a segment in Resend (by contact ID or email).WriteAdd Contact To Segment
Add a contact to a segment in Resend (by contact ID or email).
Inputs
segmentIdstringrequired- Segment ID to add the contact to
contactIdstring- Contact ID
emailstring- Contact email address
resendmcp_add_suppressionAdd an email address to the suppression list in Resend.WriteAdd Suppression
Add an email address to the suppression list in Resend. Suppressed addresses never receive emails from the account, even when included as recipients. Hard bounces and spam complaints are added to the suppression list automatically; use this tool to manually suppress an address when needed, e.g. to honor a do-not-contact request. To suppress many addresses at once, use batch-add-suppressions instead.
Inputs
emailstringrequired- Email address to suppress
resendmcp_batch_add_suppressionsAdd multiple email addresses to the suppression list in Resend in a single call.WriteBatch Add Suppressions
Add multiple email addresses to the suppression list in Resend in a single call. Suppressed addresses never receive emails from the account. Hard bounces and spam complaints are added to the suppression list automatically; use this tool to manually suppress addresses when needed, e.g. to honor do-not-contact requests. For a single address, use add-suppression instead.
Inputs
emailsarrayrequired- Email addresses to suppress
resendmcp_compose_broadcast**Purpose:** Set the TipTap JSON content of a broadcast, enabling it to be edited visually in the Resend dashboard editor.WriteCompose Broadcast
**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.
Inputs
broadcastIdstringrequired- Broadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)
contentobject- TipTap JSON content. Call get-tiptap-json-content (with include_schema: true) first to get the existing content and the schema reference.
namestring- Update the broadcast name (internal label).
previewTextstring- Update the preview text (shown in inbox before opening the email).
subjectstring- Update the email subject line.
resendmcp_compose_template**Purpose:** Set the TipTap JSON content of a template, enabling it to be edited visually in the Resend dashboard editor.WriteCompose Template
**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.
Inputs
idstringrequired- The template ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>)
contentobject- TipTap JSON content. Call get-tiptap-json-content (with include_schema: true) first to get the existing content and the schema reference.
namestring- Update the template name.
subjectstring- Update the default email subject.
resendmcp_connect_to_editor**Purpose:** Show agent presence in the Resend dashboard editor.WriteConnect To Editor
**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. **Note:** This establishes a live, stateful editor session for the agent — call disconnect-from-editor when done to remove the agent's presence from the dashboard.
Inputs
resource_idstringrequired- ID of the resource or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id> or https://resend.com/templates/<id>)
resource_typestringrequired- Type of resource to connect toone of
broadcasttemplate agent_namestring- Display name for the agent avatar
resendmcp_create_api_keyCreate a new API key in Resend.WriteCreate API Key
Create a new API key in Resend. The token is only shown once upon creation, so you MUST display it to the user.
Inputs
namestringrequired- API key name
domainIdstring- Restrict API key to send emails from a specific domain. Only applicable when permission is "sending_access".
permissionstring- Access level. "full_access" grants complete resource management. "sending_access" restricts to email delivery only.one of
full_accesssending_access
resendmcp_create_automation**Purpose:** Create an automation workflow that triggers on events and executes a sequence of steps.WriteCreate Automation
**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 } ] } ## Example: Re-engagement with wait_for_event { "steps": [ { "key": "trigger", "type": "trigger", "config": { "eventName": "user.created" }, "next": "send_email_1" }, { "key": "send_email_1", "type": "send_email", "config": { "template": { "id": "tmpl_789" }, "from": "Team <team@example.com>", "subject": "Welcome" }, "next": "wait_event_1" }, { "key": "wait_event_1", "type": "wait_for_event", "config": { "eventName": "resend:email.opened", "timeout": "3 days" }, "branches": { "event_received": null, "timeout": "send_email_2" } }, { "key": "send_email_2", "type": "send_email", "config": { "template": { "id": "tmpl_abc" }, "from": "Team <team@example.com>", "subject": "Did you miss this?" }, "next": null } ] } ## Example: Condition branch { "steps": [ { "key": "trigger", "type": "trigger", "config": { "eventName": "trial.ended" }, "next": "condition_1" }, { "key": "condition_1", "type": "condition", "config": { "type": "rule", "field": "event.converted", "operator": "eq", "value": true }, "branches": { "condition_met": "send_email_1", "condition_not_met": "send_email_2" } }, { "key": "send_email_1", "type": "send_email", "config": { "template": { "id": "tmpl_thanks" }, "from": "Team <team@example.com>", "subject": "Thanks for upgrading!" }, "next": null }, { "key": "send_email_2", "type": "send_email", "config": { "template": { "id": "tmpl_win_back" }, "from": "Team <team@example.com>", "subject": "We'd love to have you back" }, "next": null } ] }
Inputs
namestringrequired- Name for the automation (e.g., "Welcome Series")
workflowobjectrequired- The workflow definition. See the tool description for the full schema and examples.
statusstring- Initial status. Default: disabled. Use "enabled" to activate immediately.one of
enableddisabled
resendmcp_create_broadcast**Purpose:** Create a broadcast campaign (one email sent to an entire segment).WriteCreate Broadcast
**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.
Inputs
fromstringrequired- From email address (e.g. "onboarding@resend.com" or "Resend <onboarding@resend.com>")
namestringrequired- Name for the broadcast. If the user does not provide a name, go ahead and create a descriptive name for them, based on the email subject/content and the context of your conversation.
segmentIdstringrequired- Segment ID to send to
subjectstringrequired- Email subject
textstringrequired- Plain text version of the email content. The following placeholders may be used to personalize the email content: {{{FIRST_NAME|fallback}}}, {{{LAST_NAME|fallback}}}, {{{EMAIL}}}, {{{RESEND_UNSUBSCRIBE_URL}}}
htmlstring- HTML version of the email content. Placeholders: {{{FIRST_NAME|fallback}}}, {{{LAST_NAME|fallback}}}, {{{EMAIL}}}, {{{RESEND_UNSUBSCRIBE_URL}}}. Email HTML requirements - follow all of these without exception: STRUCTURE - Always include <!DOCTYPE html>, <html>, <head>, <body> - Layout must be table-based: <table>, <tr>, <td> - never use <div> for layout - Outer wrapper table at width="100%", inner content table at max 600px wide - Every table must have cellpadding="0" cellspacing="0" border="0" CSS - All styles must be inline (style="...") - no <style> tag, no external stylesheets - No flexbox, no grid, no CSS variables, no CSS shorthand (use padding-top not padding) - font-family must always include web-safe fallbacks (Arial, Helvetica, Georgia, sans-serif) - Always set font-size, line-height, and color explicitly on every text element IMAGES - Always set width, height, border="0", display:block on every <img> - Use absolute URLs only - no relative paths - Always include alt text LINKS & BUTTONS - Never use <button> - use <a> styled as a button inside a <td> - No <video>, <form>, or <input> elements - No JavaScript of any kind OUTLOOK COMPATIBILITY - Use bgcolor attribute on <td> alongside CSS background-color - No CSS background-image (poor Outlook support) - Add <!--[if mso]> conditionals where needed for Outlook rendering META (in <head>) - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta http-equiv="X-UA-Compatible" content="IE=edge">
previewTextstring- Preview text for the email
replyToarray- Reply-to email address(es)
resendmcp_create_contactCreate a new contact in Resend.WriteCreate Contact
Create a new contact in Resend. Optionally assign to segments and configure topic subscriptions.
Inputs
emailstringrequired- Contact email address
firstNamestring- Contact first name
lastNamestring- Contact last name
propertiesobject- Custom property key-value pairs for the contact (e.g. { "company_name": "Acme" })
segmentIdsarray- Array of segment IDs to assign this contact to
topicsarray- Array of topic subscription configurations
unsubscribedboolean- Whether the contact is unsubscribed from all broadcasts
resendmcp_create_contact_importBulk-import contacts from a CSV file into Resend.WriteCreate Contact Import
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.
Inputs
contentstringrequired- Raw CSV text to upload (e.g. "email,first_name\na@b.com,Ada").
columnMapobject- Maps contact fields to CSV header names. When omitted, headers are matched case-sensitively to "email", "first_name", and "last_name".
filenamestring- Name for the uploaded file. Defaults to "contacts.csv".
onConflictstring- How to handle contacts that already exist: "upsert" updates them, "skip" leaves them unchanged. Defaults to "upsert".one of
upsertskip segmentIdsarray- Array of segment IDs to assign the imported contacts to.
topicsarray- Topic subscription configurations applied to the imported contacts.
resendmcp_create_contact_propertyCreate a new contact property in Resend.WriteCreate Contact Property
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.
Inputs
keystringrequired- The property key. Max 50 characters, only alphanumeric characters and underscores allowed.
typestringrequired- The property type: "string" or "number".one of
stringnumber fallbackValuestring- Default value when the property is not set for a contact. Must match the specified type.
resendmcp_create_domainCreate a new domain in Resend.WriteCreate Domain
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.
Inputs
namestringrequired- The domain name (e.g., example.com)
capabilitiesobject- Domain capabilities configuration.
clickTrackingboolean- Enable click tracking in HTML emails.
customReturnPathstring- Subdomain for the Return-Path address. Defaults to "send".default
send openTrackingboolean- Enable email open rate tracking.
regionstring- Deployment region. Defaults to "us-east-1".one of
us-east-1eu-west-1sa-east-1ap-northeast-1defaultus-east-1 tlsstring- TLS mode. "opportunistic" attempts secure connection with fallback. "enforced" requires TLS or fails. Defaults to "opportunistic".one of
opportunisticenforceddefaultopportunistic trackingSubdomainstring- Custom subdomain for tracking links (e.g., "track" for track.example.com). When set, click and open tracking URLs will use this subdomain instead of the default.
resendmcp_create_domain_claimStart a claim for a domain another Resend account has already verified.WriteCreate Domain Claim
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".
Inputs
namestringrequired- The domain name to claim (e.g., example.com)
clickTrackingboolean- Enable click tracking in HTML emails.
customReturnPathstring- Subdomain for the Return-Path address. Defaults to "send".default
send openTrackingboolean- Enable email open rate tracking.
regionstring- Deployment region. Defaults to "us-east-1".one of
us-east-1eu-west-1sa-east-1ap-northeast-1defaultus-east-1 trackingSubdomainstring- Custom subdomain for tracking links (e.g., "track" for track.example.com).
resendmcp_create_segmentCreate a new segment in Resend.WriteCreate Segment
Create a new segment in Resend. A segment is a group of contacts that can be used to target specific broadcasts.
Inputs
namestringrequired- Name for the new segment
resendmcp_create_templateCreate a new email template in Resend.WriteCreate Template
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.
Inputs
htmlstringrequired- The HTML content of the template. Use triple-brace syntax for variables: {{{VARIABLE_NAME}}}. Email HTML requirements — follow all of these without exception: STRUCTURE - Always include <!DOCTYPE html>, <html>, <head>, <body> - Layout must be table-based: <table>, <tr>, <td> — never use <div> for layout - Outer wrapper table at width="100%", inner content table at max 600px wide - Every table must have cellpadding="0" cellspacing="0" border="0" CSS - All styles must be inline (style="...") — no <style> tag, no external stylesheets - No flexbox, no grid, no CSS variables, no CSS shorthand (use padding-top not padding) - font-family must always include web-safe fallbacks (Arial, Helvetica, Georgia, sans-serif) - Always set font-size, line-height, and color explicitly on every text element IMAGES - Always set width, height, border="0", display:block on every <img> - Use absolute URLs only — no relative paths - Always include alt text LINKS & BUTTONS - Never use <button> — use <a> styled as a button inside a <td> - No <video>, <form>, or <input> elements - No JavaScript of any kind OUTLOOK COMPATIBILITY - Use bgcolor attribute on <td> alongside CSS background-color - No CSS background-image (poor Outlook support) - Add <!--[if mso]> conditionals where needed for Outlook rendering META (in <head>) - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta http-equiv="X-UA-Compatible" content="IE=edge">
namestringrequired- The name of the template.
aliasstring- An alias for the template. Can be used instead of the ID to reference the template.
fromstring- Sender email address (e.g., "Your Name <sender@example.com>"). Can be overridden when sending.
replyTostring- Default Reply-to email address(es). Can be overridden when sending.
subjectstring- Default email subject. Can be overridden when sending.
textstring- Plain text version of the message. If not provided, HTML will be used to generate it.
variablesarray- Array of template variables (up to 50 per template).
resendmcp_create_topicCreate a new topic in Resend.WriteCreate Topic
Create a new topic in Resend. Topics allow contacts to manage their subscription preferences for different types of emails.
Inputs
defaultSubscriptionstringrequired- Default subscription preference for new contacts. Cannot be modified after creation.one of
opt_inopt_out namestringrequired- Topic name (max 50 characters)
descriptionstring- Topic description (max 200 characters)
resendmcp_create_webhookCreate a new webhook in Resend.WriteCreate Webhook
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).
Inputs
endpointstringrequired- The URL where webhook events will be sent
eventsarrayrequired- Array of event types to subscribe to
resendmcp_disconnect_from_editorRemove agent presence from the Resend dashboard editor.WriteDisconnect From Editor
Remove agent presence from the Resend dashboard editor. Call this when done editing.
Inputs
This tool takes no inputs.
resendmcp_duplicate_automationDuplicate an existing automation by ID or Resend dashboard URL.WriteDuplicate Automation
Duplicate an existing automation by ID or Resend dashboard URL. Creates a copy with its own ID, including the steps and connections of the original. Use this when the user wants a new automation based on one they already have, instead of rebuilding the workflow from scratch. Use update-automation on the new ID to rename it or change its workflow.
Inputs
idstringrequired- Automation ID or Resend dashboard URL (e.g. https://resend.com/automations/<id>) of the automation to duplicate
resendmcp_duplicate_templateDuplicate an existing email template in Resend.WriteDuplicate Template
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.
Inputs
idstringrequired- The ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>) of the template to duplicate.
resendmcp_manage_events**Purpose:** Create, list, get, update, or remove event definitions in Resend.WriteManage Events
**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
Inputs
actionstringrequired- The operation to perform.one of
createlistgetupdateremove afterstring- Cursor for forward pagination (for list).
beforestring- Cursor for backward pagination (for list).
identifierstring- Event ID or name (for get, update, remove).
limitnumber- Number of events to retrieve (for list). Default: 20.
namestring- Event name (for create). Use dot notation like "user.created". Cannot start with "resend:".
schemastring- Event payload schema (for create, update). Maps field names to types. Pass null to remove the schema.
resendmcp_publish_templatePublish an email template in Resend.WritePublish Template
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.
- Idempotent
Inputs
idstringrequired- The template ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>)
resendmcp_send_event**Purpose:** Fire an event to trigger automations for a specific contact.WriteSend Event
**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.
Inputs
eventstringrequired- The event name (e.g., "user.created", "payment.failed")
contactIdstring- The contact ID to associate with the event. Use either contactId or email, not both.
emailstring- The contact email to associate with the event. Use either contactId or email, not both.
payloadobject- Optional key-value data passed to the automation. Accessible in steps via event.* variables.
resendmcp_update_api_keyRename an existing API key in Resend.WriteUpdate API Key
Rename an existing API key in Resend. Only the name can be changed — permission and domain restrictions are fixed at creation and cannot be updated.
Inputs
idstringrequired- API key ID
namestringrequired- New API key name
resendmcp_update_automation**Purpose:** Update an automation's name, status, or workflow.WriteUpdate Automation
**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", "type": "trigger", "config": { "eventName": "user.created" }, "next": "send_email_1" }, { "key": "send_email_1", "type": "send_email", "config": { "template": { "id": "tmpl_789" }, "from": "Team <team@example.com>", "subject": "Welcome" }, "next": "wait_event_1" }, { "key": "wait_event_1", "type": "wait_for_event", "config": { "eventName": "resend:email.opened", "timeout": "3 days" }, "branches": { "event_received": null, "timeout": "send_email_2" } }, { "key": "send_email_2", "type": "send_email", "config": { "template": { "id": "tmpl_abc" }, "from": "Team <team@example.com>", "subject": "Did you miss this?" }, "next": null } ] } ## Example: Condition branch { "steps": [ { "key": "trigger", "type": "trigger", "config": { "eventName": "trial.ended" }, "next": "condition_1" }, { "key": "condition_1", "type": "condition", "config": { "type": "rule", "field": "event.converted", "operator": "eq", "value": true }, "branches": { "condition_met": "send_email_1", "condition_not_met": "send_email_2" } }, { "key": "send_email_1", "type": "send_email", "config": { "template": { "id": "tmpl_thanks" }, "from": "Team <team@example.com>", "subject": "Thanks for upgrading!" }, "next": null }, { "key": "send_email_2", "type": "send_email", "config": { "template": { "id": "tmpl_win_back" }, "from": "Team <team@example.com>", "subject": "We'd love to have you back" }, "next": null } ] }
Inputs
idstringrequired- Automation ID or Resend dashboard URL (e.g. https://resend.com/automations/<id>)
namestring- New name for the automation.
statusstring- New status. Use "disabled" to stop the automation (prevents new runs).one of
enableddisabled workflowobject- New workflow definition. Replaces the existing workflow entirely.
resendmcp_update_broadcastUpdate broadcast metadata by ID or Resend dashboard URL (name, subject, from, html, text, segment, preview text, reply-to).WriteUpdate Broadcast
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.
Inputs
broadcastIdstringrequired- Broadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)
fromstring- From email address (e.g. "onboarding@resend.com" or "Resend <onboarding@resend.com>")
htmlstring- HTML content of the email. Email HTML requirements — follow all of these without exception: STRUCTURE - Always include <!DOCTYPE html>, <html>, <head>, <body> - Layout must be table-based: <table>, <tr>, <td> — never use <div> for layout - Outer wrapper table at width="100%", inner content table at max 600px wide - Every table must have cellpadding="0" cellspacing="0" border="0" CSS - All styles must be inline (style="...") — no <style> tag, no external stylesheets - No flexbox, no grid, no CSS variables, no CSS shorthand (use padding-top not padding) - font-family must always include web-safe fallbacks (Arial, Helvetica, Georgia, sans-serif) - Always set font-size, line-height, and color explicitly on every text element IMAGES - Always set width, height, border="0", display:block on every <img> - Use absolute URLs only — no relative paths - Always include alt text LINKS & BUTTONS - Never use <button> — use <a> styled as a button inside a <td> - No <video>, <form>, or <input> elements - No JavaScript of any kind OUTLOOK COMPATIBILITY - Use bgcolor attribute on <td> alongside CSS background-color - No CSS background-image (poor Outlook support) - Add <!--[if mso]> conditionals where needed for Outlook rendering META (in <head>) - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta http-equiv="X-UA-Compatible" content="IE=edge">
namestring- Name for the broadcast
previewTextstring- Preview text for the email
replyToarray- Reply-to email address(es)
segmentIdstring- Segment ID to send to
subjectstring- Email subject
textstring- Plain text content of the email
resendmcp_update_contactUpdate a contact in Resend (by ID or email).WriteUpdate Contact
Update a contact in Resend (by ID or email).
Inputs
emailstring- Contact email address
firstNamestring- Contact first name. Pass `null` to remove the contact's first name.
idstring- Contact ID
lastNamestring- Contact last name. Pass `null` to remove the contact's last name.
propertiesobject- Custom property key-value pairs to update (e.g. { "company_name": "Acme" })
unsubscribedboolean- Whether the contact is unsubscribed from all broadcasts
resendmcp_update_contact_propertyUpdate an existing contact property in Resend.WriteUpdate Contact Property
Update an existing contact property in Resend. Only the fallback value can be changed — the key and type cannot be modified after creation.
Inputs
contactPropertyIdstringrequired- Contact property ID
fallbackValuestringrequired- New default value for the property. Pass null to remove the fallback value. Must match the property type.
resendmcp_update_contact_topicsUpdate topic subscriptions for a contact in Resend (by contact ID or email).WriteUpdate Contact Topics
Update topic subscriptions for a contact in Resend (by contact ID or email).
Inputs
topicsarrayrequired- Array of topic subscription configurations to update
emailstring- Contact email address
idstring- Contact ID
resendmcp_update_domainUpdate an existing domain in Resend.WriteUpdate Domain
Update an existing domain in Resend. Allows changing tracking settings, TLS mode, and capabilities.
Inputs
idstringrequired- Domain ID
capabilitiesobject- Domain capabilities. At least one capability must remain enabled.
clickTrackingboolean- Track clicks within the body of each HTML email.
openTrackingboolean- Track the open rate of each email.
tlsstring- TLS mode. "opportunistic" attempts secure connection with fallback. "enforced" requires TLS or fails.one of
opportunisticenforced trackingSubdomainstring- Custom subdomain for tracking links (e.g., "track" for track.example.com). When set, click and open tracking URLs will use this subdomain instead of the default.
resendmcp_update_emailReschedule a scheduled email by updating its scheduled send time.WriteUpdate Email
Reschedule a scheduled email by updating its scheduled send time. Only works for emails that were scheduled and have not yet been sent.
Inputs
idstringrequired- The ID of the scheduled email to update
scheduledAtstringrequired- The new scheduled time in ISO 8601 format (e.g., "2024-08-05T11:52:01.858Z").
resendmcp_update_templateUpdate template metadata by ID, alias, or Resend dashboard URL (name, subject, from, html, variables, etc.).WriteUpdate Template
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.
Inputs
idstringrequired- The template ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>)
aliasstring- New alias for the template.
fromstring- New sender email address.
htmlstring- New HTML content for the template. Email HTML requirements — follow all of these without exception: STRUCTURE - Always include <!DOCTYPE html>, <html>, <head>, <body> - Layout must be table-based: <table>, <tr>, <td> — never use <div> for layout - Outer wrapper table at width="100%", inner content table at max 600px wide - Every table must have cellpadding="0" cellspacing="0" border="0" CSS - All styles must be inline (style="...") — no <style> tag, no external stylesheets - No flexbox, no grid, no CSS variables, no CSS shorthand (use padding-top not padding) - font-family must always include web-safe fallbacks (Arial, Helvetica, Georgia, sans-serif) - Always set font-size, line-height, and color explicitly on every text element IMAGES - Always set width, height, border="0", display:block on every <img> - Use absolute URLs only — no relative paths - Always include alt text LINKS & BUTTONS - Never use <button> — use <a> styled as a button inside a <td> - No <video>, <form>, or <input> elements - No JavaScript of any kind OUTLOOK COMPATIBILITY - Use bgcolor attribute on <td> alongside CSS background-color - No CSS background-image (poor Outlook support) - Add <!--[if mso]> conditionals where needed for Outlook rendering META (in <head>) - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta http-equiv="X-UA-Compatible" content="IE=edge">
namestring- New name for the template.
replyTostring- New Reply-to email address(es).
subjectstring- New default email subject.
textstring- New plain text version of the message.
variablesarray- New array of template variables (replaces existing variables).
resendmcp_update_topicUpdate an existing topic in Resend.WriteUpdate Topic
Update an existing topic in Resend. Note: defaultSubscription cannot be modified after creation.
Inputs
idstringrequired- Topic ID
descriptionstring- New topic description (max 200 characters)
namestring- New topic name (max 50 characters)
resendmcp_update_webhookUpdate an existing webhook in Resend.WriteUpdate Webhook
Update an existing webhook in Resend. You can change the endpoint URL, subscribed events, or enable/disable the webhook.
Inputs
webhookIdstringrequired- Webhook ID
endpointstring- New URL where webhook events will be sent
eventsarray- New array of event types to subscribe to
statusstring- Webhook statusone of
enableddisabled
resendmcp_verify_domainTrigger domain verification in Resend.WriteVerify Domain
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.
- Idempotent
Inputs
idstringrequired- Domain ID
resendmcp_verify_domain_claimTrigger asynchronous DNS verification and ownership transfer for a domain claim, using the placeholder Domain ID.WriteVerify Domain Claim
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.
- Idempotent
Inputs
idstringrequired- The placeholder Domain ID created by the claim
resendmcp_batch_remove_suppressionsRemove multiple entries from the suppression list in Resend in a single call, by email addresses or by suppression IDs (provide exactly one of the two).DestructiveBatch Remove Suppressions
Remove multiple entries from the suppression list in Resend in a single call, by email addresses or by suppression IDs (provide exactly one of the two). The addresses will start receiving emails again. Before using this tool, you MUST double-check with the user that they want to remove these suppressions. Reference the EMAIL ADDRESSES (or IDs) when double-checking, and warn the user that addresses suppressed due to a bounce or complaint may hurt deliverability if emailed again. You may only use this tool if the user explicitly confirms they want to remove the suppressions after you double-check.
Inputs
emailsarray- Email addresses to remove from the suppression list. Cannot be used with "ids".
idsarray- Suppression IDs to remove from the suppression list. Cannot be used with "emails".
resendmcp_cancel_broadcast**Purpose:** Cancel a queued or scheduled broadcast by ID or Resend dashboard URL, without removing it.DestructiveCancel Broadcast
**Purpose:** Cancel a queued or scheduled broadcast by ID or Resend dashboard URL, without removing it. Cancelling a queued broadcast stops it mid-send (emails already sent are not affected). Cancelling a scheduled broadcast reverts it to draft. **NOT for:** Removing a broadcast entirely (use remove-broadcast). Draft and sent broadcasts cannot be cancelled - sent broadcasts are immutable, and drafts have nothing to cancel. **When to use:** User wants to "stop", "cancel", or "pause" a broadcast that is currently sending or scheduled to send.
Inputs
broadcastIdstringrequired- Broadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)
resendmcp_cancel_emailCancel a scheduled email that has not yet been sent.DestructiveCancel Email
Cancel a scheduled email that has not yet been sent. Only works for emails that were scheduled using the scheduledAt parameter.
Inputs
idstringrequired- The ID of the scheduled email to cancel
resendmcp_remove_api_keyRemove an API key by ID from Resend.DestructiveRemove API Key
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.
Inputs
idstringrequired- API key ID
resendmcp_remove_automationRemove an automation by ID or Resend dashboard URL.DestructiveRemove Automation
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.
Inputs
idstringrequired- Automation ID or Resend dashboard URL (e.g. https://resend.com/automations/<id>)
resendmcp_remove_broadcastRemove a broadcast by ID or Resend dashboard URL.DestructiveRemove Broadcast
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.
Inputs
broadcastIdstringrequired- Broadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)
resendmcp_remove_contactRemove a contact from Resend (by ID or email).DestructiveRemove Contact
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.
Inputs
emailstring- Contact email address
idstring- Contact ID
resendmcp_remove_contact_from_segmentRemove a contact from a segment in Resend (by contact ID or email).DestructiveRemove Contact From Segment
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.
Inputs
segmentIdstringrequired- Segment ID to remove the contact from
contactIdstring- Contact ID
emailstring- Contact email address
resendmcp_remove_contact_propertyRemove a contact property by ID from Resend.DestructiveRemove Contact Property
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.
Inputs
contactPropertyIdstringrequired- Contact property ID
resendmcp_remove_domainRemove a domain by ID from Resend.DestructiveRemove Domain
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.
Inputs
idstringrequired- Domain ID
resendmcp_remove_segmentRemove a segment by ID from Resend.DestructiveRemove Segment
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.
Inputs
idstringrequired- Segment ID
resendmcp_remove_suppressionRemove an entry by ID or email address from the suppression list in Resend, allowing the address to receive emails again.DestructiveRemove Suppression
Remove an entry by ID or email address from the suppression list in Resend, allowing the address to receive emails again. Before using this tool, you MUST double-check with the user that they want to remove this suppression. Reference the EMAIL ADDRESS when double-checking, and warn the user that the address will start receiving emails again — if it was suppressed due to a bounce or complaint, sending to it may hurt deliverability. You may only use this tool if the user explicitly confirms they want to remove the suppression after you double-check.
Inputs
idOrEmailstringrequired- Suppression ID or email address
resendmcp_remove_templateRemove an email template by ID, alias, or Resend dashboard URL from Resend.DestructiveRemove Template
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.
Inputs
idstringrequired- The template ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>)
resendmcp_remove_topicRemove a topic by ID from Resend.DestructiveRemove Topic
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.
Inputs
idstringrequired- Topic ID
resendmcp_remove_webhookRemove a webhook by ID from Resend.DestructiveRemove Webhook
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.
Inputs
webhookIdstringrequired- Webhook ID
resendmcp_revoke_oauth_grantRevoke an OAuth grant by ID.DestructiveRevoke OAuth Grant
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.
Inputs
idstringrequired- OAuth grant ID
resendmcp_send_batch_emails**Purpose:** Send up to 100 transactional emails in one API call.DestructiveSend Batch Emails
**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.
Inputs
emailsarrayrequired- Array of email objects to send (1-100 emails)
idempotencyKeystring- Optional unique key for the whole batch that prevents duplicate batch sends on retries (sent as the Idempotency-Key header). Use the same key when retrying the same batch; use a new key for a different batch. Max 256 characters.
resendmcp_send_broadcast**Purpose:** Send (or schedule) an existing broadcast by ID.DestructiveSend Broadcast
**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.
Inputs
broadcastIdstringrequired- Broadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)
scheduledAtstring- When to send the broadcast. Value may be in ISO 8601 format (e.g., 2024-08-05T11:52:01.858Z) or in natural language (e.g., "tomorrow at 10am", "in 2 hours", "next day at 9am PST", "Friday at 3pm ET"). If not provided, the broadcast will be sent immediately.
resendmcp_send_email**Purpose:** Send a single transactional email to one or more recipients immediately (or schedule it).DestructiveSend Email
**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"
Inputs
fromstringrequired- Sender email address (e.g. "onboarding@resend.com" or "Acme <onboarding@resend.com>"). You MUST ask the user for this parameter. Under no circumstance provide it yourself
subjectstringrequired- Email subject line
textstringrequired- Plain text email content
toarrayrequired- Array of recipient email addresses (1-50 recipients)
attachmentsarray- Array of file attachments. Each needs filename plus one of: url or content. Max 40MB total.
bccarray- Optional array of BCC email addresses. You MUST ask the user for this parameter. Under no circumstance provide it yourself
ccarray- Optional array of CC email addresses. You MUST ask the user for this parameter. Under no circumstance provide it yourself
headersobject- Optional custom email headers as key/value pairs (e.g. {"List-Unsubscribe": "<https://example.com/unsubscribe>", "X-Entity-Ref-ID": "unique-id"}). Use for one-click unsubscribe, preventing Gmail threading, or other MIME headers Resend accepts.
htmlstring- HTML email content. When provided, the plain text argument MUST be provided as well.
idempotencyKeystring- Optional unique key that prevents duplicate sends on retries (sent as the Idempotency-Key header). Use the same key when retrying the same logical email; use a new key for a different email. Max 256 characters.
replyToarray- Optional email addresses for the email readers to reply to (e.g. "support@example.com" or "Support Team <support@example.com>"). You MUST ask the user for this parameter. Under no circumstance provide it yourself
scheduledAtstring- Optional parameter to schedule the email. This uses natural language. Examples would be 'tomorrow at 10am' or 'in 2 hours' or 'next day at 9am PST' or 'Friday at 3pm ET'.
tagsarray- Array of custom tags for tracking/analytics. Each tag has a name and value.
topicIdstring- Topic ID for subscription-based sending. When set, the email respects contact subscription preferences for this topic.
No tools match.
