How to connect SendGrid to OpenClaw
Connect SendGrid to OpenClaw with ClawLink: paste your SendGrid key once and 359 tools work from chat. No MCP server to run, nothing stored on your machine.
SendGridAPI KEYMCPDeliver transactional and marketing emails. Once connected, OpenClaw can read and act on SendGrid from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to SendGrid access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical SendGrid setup: install one ClawHub skill, connect SendGrid in the browser, and OpenClaw can call real SendGrid actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the SendGrid skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "SendGrid" (hith3sh/sendgrid-email) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/sendgrid-email
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to SendGrid.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect SendGrid
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with SendGrid?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect SendGrid in the ClawLink dashboard — paste your SendGrid API key once.
Verify the connection by asking OpenClaw:
Use SendGrid to add or update a contact and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once SendGrid is connected in the dashboard, that agent calls the same 359 SendGrid tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
SendGrid MCP for OpenClaw
Looking for a SendGrid MCP server for OpenClaw? ClawLink connects SendGrid to OpenClaw and exposes 359 SendGrid tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes SendGrid integration works the same way.
What the OpenClaw SendGrid integration can do
359 SendGrid tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 359.
30 of 359 SendGrid tools for OpenClaw
| Tool | What it does |
|---|---|
Add or update a contact sendgrid_add_or_update_a_contact | Add or update a SendGrid contact |
Create a campaign sendgrid_create_a_campaign | Create a SendGrid campaign |
Create a custom field sendgrid_create_a_custom_field | Create a SendGrid custom field |
Create a list sendgrid_create_a_list | Create a SendGrid contact list |
Create a transactional template sendgrid_create_a_transactional_template | Create a SendGrid transactional email template |
Get a user s account information sendgrid_get_a_user_s_account_information | Get SendGrid account information |
Get all automation stats sendgrid_get_all_automation_stats | Get SendGrid automation statistics |
Get all categories sendgrid_get_all_categories | List SendGrid email categories |
Get all field definitions sendgrid_get_all_field_definitions | List SendGrid custom field definitions |
Get all sender identities sendgrid_get_all_sender_identities | List SendGrid sender identities |
Get all single sends sendgrid_get_all_single_sends | List SendGrid single sends |
Completed steps sendgrid_completed_steps | Retrieves the verification status of a SendGrid account, checking if Domain Authentication and |
Domain warn list sendgrid_domain_warn_list | Retrieves a list of domains known to implement DMARC (Domain-based Message Authentication |
Download CSV sendgrid_download_csv | Retrieves a presigned S3 URL to download a CSV file of email activity data (up to 1M events |
Export contacts status sendgrid_export_contacts_status | Retrieves the status of a contact export job and provides download URLs when ready |
Export single send stats sendgrid_export_single_send_stats | Exports Single Send campaign statistics in CSV format |
Filter all messages sendgrid_filter_all_messages | Filter and retrieve email activity from the SendGrid Email Activity Feed API |
Filter messages by message ID sendgrid_filter_messages_by_message_id | Retrieve detailed information about a specific email message by its unique message ID |
Get a contact by ID sendgrid_get_a_contact_by_id | Retrieves the full details of a single contact by their unique ID from SendGrid Marketing |
Get a list of all ip addresses on your account sendgrid_get_a_list_of_all_ip_addresses_on_your_account | Fetches your account's IP addresses with details such as pool association and warm-up status |
Get a list of all senders sendgrid_get_a_list_of_all_senders | Retrieves a list of all Sender identities associated with your SendGrid account |
Get a list of subusers assigned to an ip sendgrid_get_a_list_of_subusers_assigned_to_an_ip | Retrieves a list of Subuser IDs assigned to a specific IP address in your SendGrid account |
Get a specific sender sendgrid_get_a_specific_sender | Retrieves the details of a specific Marketing Sender by its unique ID |
Get a user s profile sendgrid_get_a_user_s_profile | Retrieve the authenticated user's profile details |
Get account offerings sendgrid_get_account_offerings | Retrieves the offerings (email packages and add-ons) assigned to a specific customer account |
Get all accounts sendgrid_get_all_accounts | Retrieves all accounts under the organization |
Get all available offerings sendgrid_get_all_available_offerings | Retrieves all available SendGrid offerings for account provisioning |
Get all existing exports sendgrid_get_all_existing_exports | Retrieves all existing contact export jobs from SendGrid Marketing Campaigns |
Get all ip pools that have associated ips sendgrid_get_all_ip_pools_that_have_associated_ips | The function lists your IP Pools and samples up to 10 IPs from each |
Get all single sends stats sendgrid_get_all_single_sends_stats | Retrieve email statistics for SendGrid Single Sends (one-time marketing email campaigns) |
Try it: find the SendGrid tool you need
Browse the 30 SendGrid tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use SendGrid to add or update a contact and walk me through the result in plain English.
Create it in SendGrid for me, then confirm the important fields before you finish.
Create it in SendGrid for me, then confirm the important fields before you finish.
Create it in SendGrid 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SendGrid working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the SendGrid API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected SendGrid 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 SendGrid. | 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 SendGrid actions to the runtime in a format your agent can reliably use. | 359 tools for SendGrid are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes SendGrid 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 OpenClaw users instead. You install the plugin once, connect SendGrid in the browser, and the 359 tools above work from chat. There is no SDK and no config file, and the SendGrid 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
OpenClaw installed the SendGrid skill but can't call the tools
The ClawHub skill teaches OpenClaw about SendGrid, but the calls run through the ClawLink plugin and your connected account. Make sure SendGrid is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect SendGrid 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 SendGrid tools
SendGrid 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 SendGrid 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.
SendGrid 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 SendGrid has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw SendGrid integration?
Yes. ClawLink is the fastest way to connect OpenClaw to SendGrid: link your SendGrid account once in the browser and OpenClaw can call the SendGrid API through 359 ready-made tools — no custom code or token handling.
How do I add SendGrid to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink SendGrid skill from ClawHub, then you click Connect in the dashboard to authorize SendGrid. OpenClaw calls the tools from the next message — no config files, and the SendGrid key you paste is stored server-side instead of in your environment.
How long does it take to connect SendGrid to OpenClaw?
About two minutes. Sign in, click Connect next to SendGrid in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring SendGrid up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SendGrid working from chat.
OpenClaw installed the SendGrid skill but can't call the tools
The ClawHub skill teaches OpenClaw about SendGrid, but the calls run through the ClawLink plugin and your connected account. Make sure SendGrid is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
