Email and calendar
SendGrid for AI agents.
Managed auth, ready-made tools.
Send email, manage contacts and lists, schedule campaigns and check delivery stats in the SendGrid accounts your users connect.
About SendGrid
With the SendGrid connector, your agent sends and tracks email from the SendGrid accounts your users connect. It can send a message, add contacts to a list, prepare and schedule a campaign and check delivery stats and bounces, using only the tools your project allows.
SendGrid is Twilio’s email delivery platform for transactional and marketing email.
Tools
What your agent can do in SendGrid.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own SendGrid connection.
-
Send an email
Writesendgrid_send_emailSend an email, optionally from a dynamic template.
-
Add or update contacts
Writesendgrid_upsert_contactsAdd contacts or update existing ones, optionally into a list.
-
Search contacts
Readsendgrid_search_contactsFind contacts that match a query.
-
List contact lists
Readsendgrid_list_listsList the account's contact lists.
-
List templates
Readsendgrid_list_templatesList the account's email templates.
-
Create a campaign
Writesendgrid_create_single_sendCreate a Single Send for chosen lists or segments.
-
Schedule a campaign
Writesendgrid_schedule_single_sendSend a Single Send now or at a set time.
-
Get email stats
Readsendgrid_get_statsRead delivery, open and click totals for a date range.
-
List bounces
Readsendgrid_list_bouncesList addresses that bounced.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in SendGrid, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read stats and contacts, and switch off
sendgrid_schedule_single_sendif it should never send a campaign. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example statistics only. A call outside them is refused.
Get started
Connect SendGrid
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect SendGrid
Each end user authorizes their own SendGrid account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own SendGrid account, once. const connection = await agent200 .user("user_123") .connect("sendgrid"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the SendGrid tools
Name the user, the model and the tools. The model decides which SendGrid tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "How did last week's emails perform?", tools: ["sendgrid"], }); console.log(result.output);
Access
Sign-in and permissions.
-
How a user connects
SendGrid offers no OAuth sign-in for other apps. A user connects with an API key created in their own SendGrid settings; their SendGrid password is never shared.
-
What access the key has
What the user set when creating the key: full access, or restricted access chosen area by area. The user can change or delete the key at any time in SendGrid.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the SendGrid connector and how to use it.
Connector: SendGrid, through Agent200. In code: "sendgrid". What it does: Send email, manage contacts and lists, schedule campaigns and check delivery stats in the SendGrid accounts your users connect. Page: https://www.agent200.com/tools/sendgrid/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on SendGrid's own page, through the authorization link Agent200 returns. Never ask a user for a SendGrid password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: sendgrid_search_contacts, sendgrid_list_lists, sendgrid_list_templates, sendgrid_get_stats, sendgrid_list_bounces. Write tools: sendgrid_send_email, sendgrid_upsert_contacts, sendgrid_create_single_send, sendgrid_schedule_single_send. Name "sendgrid" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/sendgrid/framework/claude/ https://www.agent200.com/tools/sendgrid/framework/chatgpt/ https://www.agent200.com/tools/sendgrid/framework/claude-code/ https://www.agent200.com/tools/sendgrid/framework/muse/ https://www.agent200.com/tools/sendgrid/framework/grok-bot/ https://www.agent200.com/tools/sendgrid/framework/openai-dots/ https://www.agent200.com/tools/sendgrid/framework/claude-duet/ https://www.agent200.com/tools/sendgrid/framework/hermes-agent/ https://www.agent200.com/tools/sendgrid/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/sendgrid.md
Guides
Use SendGrid with the AI you build on.
Step-by-step setup for SendGrid with a specific model, assistant or agent framework.
-
SendGrid + Claude
How to connect SendGrid to Claude
-
SendGrid + ChatGPT
How to connect SendGrid to ChatGPT
-
SendGrid + Claude Code
How to connect SendGrid to Claude Code
-
SendGrid + Muse
How to connect SendGrid to Muse
-
SendGrid + Grok Bot
How to connect SendGrid to Grok Bot
-
SendGrid + OpenAI Dots
How to connect SendGrid to OpenAI Dots
-
SendGrid + Claude Duet
How to connect SendGrid to Claude Duet
-
SendGrid + Hermes Agent
How to connect SendGrid to Hermes Agent
-
SendGrid + OpenClaw
How to connect SendGrid to OpenClaw
FAQ
SendGrid and Agent200, answered.
Who handles the SendGrid OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for SendGrid.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's SendGrid connection, never another user's. It cannot reach anything the user or SendGrid has not authorized.
Can I limit what my agent can do in SendGrid?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.