Menu
Mattering Automations connector

A SendGrid MCP where test sends never reach an inbox

Connect one API key and transactional sends, dynamic templates, marketing contacts, suppressions, and stats become workflow steps for visual automations and AI agents. The one node that delivers real email is labeled SendGrid: Send Email (Sends Real Email), and its first field is sandbox_mode, the documented switch that validates a send end to end without delivering anything.

41 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the SendGrid MCP connector does

The SendGrid connector for Mattering Automations is 41 nodes across the v3 API: transactional mail send, dynamic and legacy templates with their versions, marketing contacts, lists, and segments (plus the custom field definitions that upserts need), the full deliverability toolkit (bounces, blocks, spam reports, invalid emails, global unsubscribes, and suppression groups), global and per-category statistics, real time email address validation, the account's verified senders, and introspection of the API key's own permission scopes.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer which addresses bounced this week and why, whether a from address is verified, and what a key is actually allowed to do, without anyone opening the SendGrid dashboard.

Because Mattering is a work platform rather than middleware, deliverability work lands somewhere useful by default: a scheduled sweep over bounces, blocks, spam reports, and unsubscribes can update records in a Mattering database and open remediation tasks in Mattering Productivity, all on one canvas next to the rest of the work. Mailgun is also available as a Mattering connector, so teams can automate whichever email platform they already send through.

Real delivery is impossible to miss. The one node that sends is labeled SendGrid: Send Email (Sends Real Email), and its first field is sandbox_mode: with it on, SendGrid validates the entire request and returns success without delivering, the platform's documented safe test path. The from address must be a verified sender or on an authenticated domain, and SendGrid: List Verified Senders exists as the pre-send check. Once SendGrid accepts a live send it cannot be recalled, so gate the node behind a condition, an approval step, or a manual run.

One connection, three surfaces

  • Visual automations. Drag SendGrid nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every SendGrid node, ready to drop on the canvas

41 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 24

SendGrid: Get Bounce

Look up whether one specific address has bounced and why. Returns an array (empty when the address has no bounce record).

SendGrid: Get Category Stats

Email statistics broken down by message category (the labels set on sends, e.g. by the Mail Send node's categories field). Up to 10 categories per call; category data covers the previous 13 months only.

SendGrid: Get Contact

Fetch one marketing contact by its contact ID (a UUID), including list memberships and custom field values. Get the ID from SendGrid: Search Contacts.

SendGrid: Get Contact Import Status

Check an asynchronous contact job (upsert or delete) by the job_id those nodes return. status is pending, completed, errored, or failed; results carries created, updated, deleted and errored counts plus an errors_url when rows failed.

SendGrid: Get Contact List

Fetch one marketing list. Set contact_sample true to include a small sample of the list's contacts in the response.

SendGrid: Get Global Stats

Account-wide email statistics (requests, delivered, opens, clicks, bounces, spam reports, unsubscribes) over a date window, optionally aggregated by day, week, or month. Needs the stats scope.

SendGrid: Get Segment

Fetch one segment including its query definition. Set contacts_sample true to include a sample of matching contacts (the sample refreshes on SendGrid's 1-to-24-hour schedule, not live).

SendGrid: Get Suppression Group

Fetch one unsubscribe group with its unsubscribe count.

SendGrid: Get Template

Fetch one template with its versions array (each version carries id, name, subject, active flag and editor; use the version id with the version nodes below).

SendGrid: Get User Profile

Read the account holder's profile (name, company, address, phone, website). Needs the user.profile read scope on a restricted key. A 403 from this endpoint usually means the API key was created with Restricted Access and lacks the needed permission scope, not that the key is invalid; check the key in SendGrid Settings > API Keys.

SendGrid: List API Key Scopes

List the permission scopes granted to the API key making the call (e.g. mail.send, templates.read). Takes no parameters, works for any valid key regardless of its restrictions, and returns only scope-name strings, so it doubles as the credential health check. If another SendGrid node returns 403, run this to see what the key is actually allowed to do.

SendGrid: List Blocks

List blocked sends: messages a receiving server refused for reasons about the MESSAGE or connection (content, reputation, timeouts) rather than the address. Unlike bounces, blocks do not suppress future sends.

SendGrid: List Bounces

List bounced addresses with the bounce reason and SMTP status code. SendGrid auto-suppresses future sends to these addresses. Filter by a Unix time window.

SendGrid: List Contact Lists

List marketing contact lists with their contact counts. Page with page_size and the page_token from the previous response's _metadata.next.

SendGrid: List Field Definitions

List all contact field definitions: your custom fields (with the IDs needed by Add or Update Contacts) and SendGrid's reserved fields. Field types are Text, Number, and Date.

SendGrid: List Global Unsubscribes

List addresses on the global unsubscribe list (recipients who opted out of ALL email from this account). Filter by a Unix time window and page with limit and offset. Needs the suppression scope.

SendGrid: List Group Suppressions

List the email addresses suppressed (unsubscribed) from one group. The response is a plain array of address strings.

SendGrid: List Invalid Emails

List addresses SendGrid found malformed or nonexistent at send time. Useful as a cleanup feed for the contact base.

SendGrid: List Segments

List marketing segments (the 2.0 segmentation API) with their contact counts. Segment counts and samples refresh on SendGrid's own schedule (1 to 24 hours), so counts can lag reality.

SendGrid: List Spam Reports

List recipients who marked mail from this account as spam. SendGrid suppresses future sends to them; treat these as hard opt-outs in any sync.

SendGrid: List Suppression Groups

List unsubscribe (suppression) groups: the per-mail-stream opt-out categories recipients see, e.g. Newsletter vs Product Updates. Accounts can hold up to 200 groups. Group IDs feed the Mail Send node's asm_group_id.

SendGrid: List Templates

List transactional email templates (up to 300 per account). NOTE the API's own default only returns LEGACY templates, so this node defaults generations to 'legacy,dynamic' to show everything; modern Handlebars templates are the 'dynamic' generation with IDs starting 'd-'.

SendGrid: List Verified Senders

List the account's sender identities with their verification state. Useful before Mail Send: the from address must be a verified sender (or on an authenticated domain) or the send is rejected.

SendGrid: Search Contacts

Search marketing contacts with an SGQL query. Returns at most 50 contacts plus the total contact_count matching. Emails are stored lowercase, so compare against lowercase values. Queries that run past 20 seconds return a 408.

Action nodes 17

SendGrid: Add Global Unsubscribes

Add addresses to the global unsubscribe list so they receive no further email from this account. The safe direction of suppression management: use it to honor opt-outs collected elsewhere.

SendGrid: Add Group Suppressions

Add addresses to one unsubscribe group's suppression list so they stop receiving that mail stream (they can still receive email attributed to other groups).

SendGrid: Add or Update Contacts

Add new marketing contacts or update existing ones by email (upsert). Up to 30,000 contacts or 6MB per call. Processing is asynchronous: the response is a 202 with a job_id, not the finished result. Poll SendGrid: Get Contact Import Status with that job_id to confirm completion. Omitted fields on an existing contact are left unchanged, and email addresses are lowercased by SendGrid. Custom fields must already exist (see SendGrid: List Field Definitions for their IDs). Needs the marketing.contacts scope.

SendGrid: Create Contact List

Create a new (empty) marketing list. Add contacts to it with SendGrid: Add or Update Contacts using list_ids; the Lists API itself cannot add contacts.

SendGrid: Create Template

Create a new transactional template shell. Content lives in versions: follow with SendGrid: Create Template Version to add subject and body. Accounts are limited to 300 templates.

SendGrid: Create Template Version

Add a version (subject + body content) to a template. Setting active 1 makes it the live version served when the template is sent. Dynamic templates use Handlebars, e.g. {{first_name}}, filled at send time via dynamic_template_data.

SendGrid: Delete Bounce

Delete one address's bounce record, re-enabling sends to it. DESTRUCTIVE: the bounce record (reason, timestamp) is gone for good, and re-sending to an address that hard-bounced hurts sender reputation. Only use after the underlying problem (typo fixed, mailbox restored) is genuinely resolved.

SendGrid: Delete Contact List

Delete a marketing list. DESTRUCTIVE: the list is gone; with delete_contacts true its member contacts are also deleted from the account (asynchronously, returning a job_id). With delete_contacts false (default) the contacts survive and only the list is removed.

SendGrid: Delete Contacts

Permanently delete marketing contacts by ID. DESTRUCTIVE: deleted contacts and their field data are gone (SendGrid recommends exporting contacts as a backup first). Processing is asynchronous: the response is a 202 with a job_id, not the finished result. Poll SendGrid: Get Contact Import Status with that job_id to confirm completion. The API's delete-all-contacts switch is deliberately not exposed on this node.

SendGrid: Delete Global Unsubscribe

Remove one address from the global unsubscribe list. CAUTION: removing a suppression re-enables email to an address whose owner may have unsubscribed on purpose. Only remove addresses you have a documented, lawful basis to email again.

SendGrid: Delete Group Suppression

Remove one address from one group's suppression list. CAUTION: removing a suppression re-enables email to an address whose owner may have unsubscribed on purpose. Only remove addresses you have a documented, lawful basis to email again.

SendGrid: Remove Contacts from List

Remove contacts from a list WITHOUT deleting them from the account (re-add them any time with Add or Update Contacts). Asynchronous: returns a job_id.

SendGrid: Send Email (Sends Real Email)

Send a real email through SendGrid to real recipients. DESTRUCTIVE in the way that matters: once SendGrid accepts the request (202) the message cannot be recalled. For testing, set sandbox_mode true: SendGrid then validates the whole request and returns success WITHOUT delivering anything, which is the documented safe test path. Provide html_content or text_content, or a template_id (dynamic templates start with 'd-') with dynamic_template_data. The from address must be a verified sender or on an authenticated domain, or SendGrid rejects the send with a 403. A successful response has an EMPTY body (the message id travels in the X-Message-Id response header, which the connector envelope does not surface). Needs the mail.send scope.

SendGrid: Update Contact List

Rename a marketing list.

SendGrid: Update Template

Rename a template. Version content is edited through the template version nodes, not here.

SendGrid: Update Template Version

Edit an existing template version: subject, content, or the active flag (set active 1 here to activate this version). Only the fields provided are changed.

SendGrid: Validate Email Address

Validate one email address in real time: verdict (Valid, Risky, Invalid), confidence score, and checks for syntax, MX records, disposable domains, role addresses, and known bounces. PAID GATE: Email Address Validation is only available on Email API Pro and Premier plans, AND it requires its own dedicated validation API key (a key created with the Email Address Validation permission), so the connector's regular key may get a 403 here even on a qualifying plan. Rate limited to 7 requests per second. Note the path is /v3/validations/email (plural).

Connecting SendGrid takes one credential

SendGrid issues API keys from Settings > API Keys in its dashboard; keys start with SG. and are sent as a bearer credential on every request. A key's permission scopes are chosen at creation and cannot be changed afterward: Full Access is the simple choice, and a Restricted Access key needs at least the Mail Send, Template Engine, Marketing, Suppressions, and Stats permissions to cover this connector's surface.

1

In SendGrid, open Settings > API Keys, create a key, and choose its permissions. Scopes are fixed at creation, so grant what your automations will need.

2

In Mattering Automations, open Connectors, click Add Connector, choose SendGrid, and create a credential with that key.

3

Click Test Connection. Mattering calls SendGrid's scopes endpoint, which authenticates any valid key regardless of how restricted it is, and confirms the credential works.

4

All 41 SendGrid nodes appear in the canvas palette. Run SendGrid: List Verified Senders before any send: the from address must be one of them or on an authenticated domain.

Common uses for the SendGrid MCP

A deliverability sweep that actually goes somewhere

SendGrid: List Bounces, SendGrid: List Blocks, SendGrid: List Spam Reports, and SendGrid: List Invalid Emails read the addresses SendGrid could not or should not reach, with reasons and timestamps. On a schedule, that feed can update records in a Mattering database and open remediation tasks, turning a list nobody checks into work someone finishes.

Transactional email with a rehearsal mode

SendGrid: Send Email (Sends Real Email) delivers through dynamic templates or raw content, and its sandbox_mode field validates the entire send without delivering, so a workflow can be exercised end to end before it ever touches an inbox. SendGrid: List Verified Senders confirms the from address will be accepted before the first run.

Contact sync that tells the truth about timing

SendGrid: Add or Update Contacts upserts marketing contacts by email address, up to 30,000 per call, and returns a job id rather than pretending the work is done: processing is asynchronous, and SendGrid: Get Contact Import Status polls the job until it completes with per-row counts. SendGrid: Search Contacts finds contacts with an SGQL query.

Suppression management with a consent posture

SendGrid: Add Global Unsubscribes and SendGrid: Add Group Suppressions honor opt-outs collected anywhere else in the business, the safe direction of suppression management. The nodes that remove suppressions exist too, but they warn plainly: removing one re-enables email to someone who may have opted out on purpose.

Templates managed from the canvas

SendGrid: Create Template and SendGrid: Create Template Version build a dynamic template with a Handlebars subject and body, SendGrid: Update Template Version edits content or activates a version, and SendGrid: List Templates defaults to showing both dynamic and legacy generations, working around an API default that hides modern templates.

Key health an agent can check

SendGrid: List API Key Scopes takes no parameters and returns exactly what the calling key is allowed to do. Because SendGrid keys carry permission scopes fixed at creation, a restricted key returns 403 on endpoints outside its grants, which looks like a bad credential; this node settles the question from the canvas in one run.

Example: A nightly deliverability sweep that cleans the records and opens remediation tasks

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule runs the sweep each night.

2

SendGrid: List Bounces, SendGrid: List Blocks, and SendGrid: List Spam Reports pull the last day of problems using a Unix time window.

3

SendGrid: List Invalid Emails and SendGrid: List Global Unsubscribes complete the picture with malformed addresses and account-wide opt-outs.

4

Each flagged address upserts a record in a Mattering database with the reason, the source list, and the timestamp; spam reports and global unsubscribes are marked as hard opt-outs.

5

SendGrid: Search Contacts checks whether a flagged address still sits in the marketing contact base.

6

A remediation task opens in Mattering Productivity listing addresses to remove or correct, so a person closes the loop instead of a delete node running unattended.

SendGrid MCP questions, answered

What SendGrid operations are supported?

41 nodes on the v3 API: transactional mail send with sandbox mode, templates and template versions, marketing contacts, lists, and segments plus custom field definitions, the deliverability toolkit (bounces, blocks, spam reports, invalid emails, global unsubscribes, suppression groups), global and category statistics, single email address validation, verified senders, the account profile, and API key scope introspection. Deliberately not shipped: the delete-all-contacts switch and bulk suppression wipes (too much blast radius for an automation), Single Sends and campaign authoring, API key management (it echoes key material), webhook configuration, and subuser, IP, and domain authentication setup, which are dashboard work.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Can this connector send real email by accident?

It is built to make that hard. The one node that delivers is labeled SendGrid: Send Email (Sends Real Email) so nobody mistakes it on a canvas, and its first field is sandbox_mode: with it on, SendGrid validates the entire request and returns success without delivering anything, which is SendGrid's documented safe test path. A live send also requires the from address to be a verified sender or on an authenticated domain, or SendGrid rejects it with a 403. Once SendGrid accepts a live send it cannot be recalled, so keep the node behind a condition, an approval step, or a manual run.

Why does a node return 403 when the connection test passes?

SendGrid API keys carry permission scopes chosen when the key is created, and a restricted key returns 403 on any endpoint outside its grants, which looks exactly like a bad credential. The connection test cannot be fooled by this: it calls the scopes endpoint, which works for every valid key regardless of restrictions. When a node 403s, run SendGrid: List API Key Scopes to see what the key is actually allowed to do, then create a new key with the missing permissions; scopes cannot be added to an existing key.

Why does email validation return 403 on a key that works everywhere else?

SendGrid: Validate Email Address is gated twice. Email Address Validation is only available on SendGrid's Email API Pro and Premier plans, and even on a qualifying plan it requires its own dedicated validation API key, created with the Email Address Validation permission; the connector's regular key gets a 403 there no matter how broad its scopes. A 403 from this node is a plan and key gate, not a broken integration.

Can a SendGrid event trigger a workflow?

Not as a trigger node in this connector. Webhook configuration (the event webhook and inbound parse) is deliberately not managed here, so there is no inbound SendGrid trigger. The honest pattern today is polling: run the bounce, block, spam report, unsubscribe, and stats nodes on a schedule and act on what changed.

Why did my contact upsert return before the contacts existed?

Because SendGrid's marketing contact writes are asynchronous. SendGrid: Add or Update Contacts, SendGrid: Delete Contacts, and SendGrid: Remove Contacts from List all return a 202 with a job id, and processing can take minutes. SendGrid: Get Contact Import Status polls that job id until the status is completed, with created, updated, and deleted counts and an errors report when rows failed. Workflows should treat the job status, not the initial response, as the signal that the work happened.

What does deleting a suppression actually do?

It re-enables email to an address whose owner may have opted out on purpose, which is why SendGrid: Delete Global Unsubscribe and SendGrid: Delete Group Suppression carry an explicit consent warning: only remove addresses you have a documented, lawful basis to email again. SendGrid: Delete Bounce goes further: the bounce record is gone for good, and re-sending to an address that hard-bounced damages sender reputation, so it is flagged destructive and should only run after the underlying problem is genuinely fixed.

41 nodes waiting on the canvas

Put SendGrid to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. SendGrid is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products