ClawLink

How to connect Resend to Grok Bot

Connect Resend to Grok Bot with ClawLink: paste your Resend key once and 113 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Grok Bot
Grok Bot
ClawLink
ClawLink
Resend
Resend
ResendAPI KEYMCP

Send transactional and marketing emails. Once connected, Grok Bot can read and act on Resend from chat — pairing, token refresh, and tool wiring handled for you.

113 tools

Grok Bot runs on its own cloud computer, so most Resend guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Resend setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Resend actions from chat with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Grok Bot to Resend.

  1. 1

    Pair from the terminal

    Ask Grok Bot to run the ClawLink CLI. It prints a link you approve once in your browser:

    npx -y @useclawlink/cli login
  2. 2

    Connect Resend

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Grok Bot: "What can you do with Resend?"

Install by command

The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:

npx -y @useclawlink/cli login          # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect resend

Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.

Verify the connection by asking Grok Bot:

Create it in Resend for me, then confirm the important fields before you finish.

Using a different agent?

The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Resend is connected in the dashboard, that agent calls the same 113 Resend tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Resend MCP for Grok Bot

Looking for a Resend MCP server for Grok Bot? ClawLink connects Resend to Grok Bot and exposes 113 Resend tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using a different agent? The OpenClaw Resend integration and the Hermes Resend integration connect the same ClawLink account the same way.

What the Grok Bot Resend integration can do

113 Resend tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 113.

30 of 113 Resend tools for Grok Bot

ToolWhat it does
Create audience resend_create_audienceCreate a Resend audience
Create contact resend_create_contactCreate a Resend contact
Create domain resend_create_domainCreate a Resend domain
Create template resend_create_templateCreate a Resend email template
Get contact resend_get_contactGet a Resend contact by ID
Get template resend_get_templateGet a Resend email template
List audiences resend_list_audiencesList Resend audiences
List contacts resend_list_contactsList Resend contacts in an audience
List domains resend_list_domainsList Resend domains
List templates resend_list_templatesList Resend email templates
Send email resend_send_emailSend an email through Resend
Get automation resend_get_automationRetrieve a Resend automation by ID, including its active workflow steps and connections
Get automation run resend_get_automation_runRetrieve a Resend automation run by automation and run IDs, including its status and step
Get broadcast resend_get_broadcastRetrieve a single broadcast by its ID
Get contact import resend_get_contact_importRetrieve a contact import by ID to check its status, timestamps, and processed row counts
Get contact property resend_get_contact_propertyRetrieve a single contact property from Resend
Get domain claim resend_get_domain_claimRetrieve the latest claim for a placeholder domain created by a claim
Get email attachment resend_get_email_attachmentRetrieve a single attachment from a sent email
Get email metrics resend_get_email_metricsRetrieve account-level email metrics over a date range, with optional filters and dimension
Get event resend_get_eventRetrieve a Resend event definition by UUID or event name
Get log resend_get_logRetrieve a single Resend API log by its ID
Get received email resend_get_received_emailRetrieve a single received email by ID, including its content, headers, recipients, and
Get received email attachment resend_get_received_email_attachmentRetrieve a single attachment from a received email, including its metadata and signed download
Get segment resend_get_segmentRetrieve a single segment by its ID
Get suppression resend_get_suppressionRetrieve a Resend suppression by ID or email address
Get topic resend_get_topicRetrieve a single topic by its ID in Resend
Get usage resend_get_usageRetrieve the account's current usage and plan limits for emails, contacts, segments
Get webhook resend_get_webhookRetrieve a single webhook for the authenticated user
Get webhook event resend_get_webhook_eventRetrieve a single webhook event by webhook ID and event ID
List all contacts resend_list_all_contactsRetrieve a list of all contacts from Resend

Try it: find the Resend tool you need

Browse the 30 Resend tools

Click any tool to see exactly what Grok Bot can do and copy a ready-to-use prompt.

Example prompts

Create it in Resend for me, then confirm the important fields before you finish.

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Resend working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Resend API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Resend account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Resend.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Resend actions to the runtime in a format your agent can reliably use.113 tools for Resend are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Resend to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Resend in the browser, and the 113 tools above work from chat. There is no SDK and no config file, and the Resend key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Grok Bot says it cannot add ClawLink as an MCP server

Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.

Connection succeeds but no tools appear

Reconnect Resend from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling Resend tools

Resend tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Resend call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Resend returns 403 or "permission denied" on one action while others work

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

API key setup works but results look incomplete

Double-check that the API key for Resend has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a Grok Bot Resend integration?

Yes. ClawLink is the fastest way to connect Grok Bot to Resend: link your Resend account once in the browser and Grok Bot can call the Resend API through 113 ready-made tools — no custom code or token handling.

How do I connect Resend to Grok Bot with ClawLink?

Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal and approve the link it prints, then npx -y @useclawlink/cli connect resend to authorize Resend. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files, and the Resend key you paste is stored server-side instead of in your environment.

How long does it take to connect Resend to Grok Bot?

About two minutes. Sign in, click Connect next to Resend in the dashboard, authenticate, and Grok Bot can use it from the next chat message.

Why use ClawLink instead of wiring Resend up myself?

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Resend working from chat.

Grok Bot says it cannot add ClawLink as an MCP server

Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.

On this page