# How to connect Resend to Grok Bot (paste one key, 62 tools) > Connect Resend to Grok Bot with ClawLink: paste your Resend key once and 62 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/grokbot/resend 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. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect resend` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Resend. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Resend** — `npx -y @useclawlink/cli connect resend`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect resend # connect Resend (browser OAuth) npx -y @useclawlink/cli actions resend # list available actions npx -y @useclawlink/cli run resend --input '' # execute (add --confirm for writes) ``` ### 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: ```bash 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: ```bash 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 62 Resend tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/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 62 Resend tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Resend integration](https://claw-link.dev/openclaw/resend) and the [Hermes Resend integration](https://claw-link.dev/hermes/resend) connect the same ClawLink account the same way. ## What the Grok Bot Resend integration can do 62 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 62. ### 30 of 62 Resend tools for Grok Bot | Tool | What it does | |---|---| | **Create audience** `resend_create_audience` | Create a Resend audience | | **Create contact** `resend_create_contact` | Create a Resend contact | | **Create domain** `resend_create_domain` | Create a Resend domain | | **Create template** `resend_create_template` | Create a Resend email template | | **Get contact** `resend_get_contact` | Get a Resend contact by ID | | **Get template** `resend_get_template` | Get a Resend email template | | **List audiences** `resend_list_audiences` | List Resend audiences | | **List contacts** `resend_list_contacts` | List Resend contacts in an audience | | **List domains** `resend_list_domains` | List Resend domains | | **List templates** `resend_list_templates` | List Resend email templates | | **Send email** `resend_send_email` | Send an email through Resend | | **Get contact property** `resend_get_contact_property` | Retrieve a single contact property from Resend | | **Get email attachment** `resend_get_email_attachment` | Retrieve a single attachment from a sent email | | **Get segment** `resend_get_segment` | Retrieve a single segment by its ID | | **Get topic** `resend_get_topic` | Retrieve a single topic by its ID in Resend | | **Get webhook** `resend_get_webhook` | Retrieve a single webhook for the authenticated user | | **List all contacts** `resend_list_all_contacts` | Retrieve a list of all contacts from Resend | | **List API keys** `resend_list_api_keys` | Retrieve a list of API keys for the authenticated user | | **List broadcasts** `resend_list_broadcasts` | Retrieve a list of broadcasts | | **List contact properties** `resend_list_contact_properties` | Retrieve a list of contact properties from Resend | | **List contact segments** `resend_list_contact_segments` | Retrieve a list of segments that a contact is part of | | **List contact topics** `resend_list_contact_topics` | Retrieve a list of topic subscriptions for a contact in Resend | | **List email attachments** `resend_list_email_attachments` | Retrieve a list of attachments from a sent email | | **List emails** `resend_list_emails` | Retrieve a list of emails sent by your team | | **List received emails** `resend_list_received_emails` | Retrieve a list of received emails for the authenticated user | | **List segments** `resend_list_segments` | Retrieve a list of segments from Resend | | **List topics** `resend_list_topics` | Retrieve a list of topics for the authenticated user | | **List webhooks** `resend_list_webhooks` | Retrieve a list of webhooks for the authenticated user | | **Retrieve audience** `resend_retrieve_audience` | Retrieve a single audience | | **Retrieve contact** `resend_retrieve_contact` | Retrieve a contact in Resend | ## Example prompts **Create Audience** > Create it in Resend for me, then confirm the important fields before you finish. **Create Contact** > Create it in Resend for me, then confirm the important fields before you finish. **Create Domain** > Create it in Resend for me, then confirm the important fields before you finish. **Create Template** > Create it in Resend for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself 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. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, 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 maintenance** | You 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 usability** | You still need to expose the right Resend actions to the runtime in a format your agent can reliably use. | 62 tools for Resend are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio 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 62 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### 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. ### 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 62 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. ## Related - [Grok Bot SendGrid integration](https://claw-link.dev/grokbot/sendgrid) — Deliver transactional and marketing emails - [Dialpad](https://claw-link.dev/grokbot/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/grokbot/discord-bot) — Automate Discord server actions with bot-specific permissions