# 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.

- Page: https://www.agent200.com/tools/sendgrid/
- Category: Email and calendar
- Authentication: Managed OAuth
- Identifier in code: `sendgrid`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

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/

## About

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.

## SendGrid tools

- **Send an email** (`sendgrid_send_email`, write): Send an email, optionally from a dynamic template.
- **Add or update contacts** (`sendgrid_upsert_contacts`, write): Add contacts or update existing ones, optionally into a list.
- **Search contacts** (`sendgrid_search_contacts`, read): Find contacts that match a query.
- **List contact lists** (`sendgrid_list_lists`, read): List the account's contact lists.
- **List templates** (`sendgrid_list_templates`, read): List the account's email templates.
- **Create a campaign** (`sendgrid_create_single_send`, write): Create a Single Send for chosen lists or segments.
- **Schedule a campaign** (`sendgrid_schedule_single_send`, write): Send a Single Send now or at a set time.
- **Get email stats** (`sendgrid_get_stats`, read): Read delivery, open and click totals for a date range.
- **List bounces** (`sendgrid_list_bounces`, read): List addresses that bounced.

## Limits you can set

**Turn single tools on or off.** Let the agent read stats and contacts, and switch off `sendgrid_schedule_single_send` if 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "How did last week's emails perform?"
- "Add these webinar signups to the Webinar list"
- "Which addresses bounced since Monday?"

## Guides: SendGrid with your AI framework

- [SendGrid + Claude](https://www.agent200.com/tools/sendgrid/framework/claude.md): Connect SendGrid to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [SendGrid + ChatGPT](https://www.agent200.com/tools/sendgrid/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds SendGrid into your own agent with OpenAI's models and the Agent200 SDK.
- [SendGrid + Claude Code](https://www.agent200.com/tools/sendgrid/framework/claude-code.md): Have Claude Code build a SendGrid agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [SendGrid + Muse](https://www.agent200.com/tools/sendgrid/framework/muse.md): Connect SendGrid to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [SendGrid + Grok Bot](https://www.agent200.com/tools/sendgrid/framework/grok-bot.md): Connect SendGrid to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [SendGrid + OpenAI Dots](https://www.agent200.com/tools/sendgrid/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on SendGrid agent with OpenAI's models and the Agent200 SDK.
- [SendGrid + Claude Duet](https://www.agent200.com/tools/sendgrid/framework/claude-duet.md): Connect SendGrid to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [SendGrid + Hermes Agent](https://www.agent200.com/tools/sendgrid/framework/hermes-agent.md): Connect SendGrid to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [SendGrid + OpenClaw](https://www.agent200.com/tools/sendgrid/framework/openclaw.md): Connect SendGrid to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### 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.

## Related connectors

- [Gmail](https://www.agent200.com/tools/gmail.md): Read, search, draft and send email from each user's own Gmail account.
- [Outlook](https://www.agent200.com/tools/outlook.md): Work with mail and calendar in each user's Microsoft Outlook account.
- [Google Calendar](https://www.agent200.com/tools/google-calendar.md): Check availability and create, update or cancel events in your users' calendars.
- [Calendly](https://www.agent200.com/tools/calendly.md): Find open times, share booking links, and book, review or cancel meetings in Calendly on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
