Resources · Make integration

SendGrid Make integrationAutomate SendGrid with Make.

Can SendGrid clean its own lists while you focus on the campaign? The SendGrid Make integration gives you 29 modules: 3 triggers, 24 actions and 2 searches for contacts, bounces, blocks, suppressions and sending. This guide connects your account and builds a first working scenario with you.

Try the SendGrid integration on MakeSee the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SendGrid Make integration do for you?

The SendGrid Make integration links your SendGrid account to Make, a visual tool where you build a scenario (the automation itself, a chain of bricks called modules). Those modules watch your contacts, keep your lists tidy, read bounces and blocks, manage global suppressions and send emails, all without writing code.

Keep deliverability problems from piling up. Get All Bounces and List Blocks pull the addresses SendGrid refused to deliver to. Push them into a sheet your support team already checks, and nobody has to dig through the SendGrid dashboard to find out why a customer never got the receipt.

Feed SendGrid from the tools where leads really arrive. A signup form, a CRM or a checkout page can start the scenario, and Add or Update a Contact (New) drops the person into the right list. No more CSV exports between two tabs.

Respect unsubscribes everywhere. When someone opts out in another tool, Add Emails to Global Suppression tells SendGrid to stop mailing that address across every campaign.

What the app does not cover out of the box goes through Make an API Call, which reaches the rest of the SendGrid API. Also, the Legacy contact modules only work for older accounts. One honest warning: the doc lists these modules without describing them, so what this page says about each one is read from its name. A quick Run once shows you what it really returns. The same app exists on the n8n side too, see the SendGrid n8n integration and the n8n vs Make comparison. New to the editor? The Make training starts from zero.

Connect

How do you connect SendGrid to Make?

  1. 01

    Create an API key in SendGrid

    In SendGrid, open Settings in the left menu, then API Keys. Click Create API Key in the top-right corner, give it Full Access permissions, and copy the value somewhere safe. Make needs this key to act on your behalf.

  2. 02

    Open a connection from any SendGrid module

    In your scenario, add a SendGrid module and click Create a connection. A connection is your SendGrid account linked to Make once, then reused by every SendGrid module. Naming it in Connection name is optional but handy with several accounts.

  3. 03

    Paste the key and save

    Paste the key in the API key field and click Save. If SendGrid asks you to authenticate and confirm access, do it. The module then shows its fields, and you can keep building.

First scenario

Your first scenario: welcome every new SendGrid contact

GoalWhen a new contact shows up in SendGrid, Make sends that person a welcome email through SendGrid.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Everything starts from this empty canvas.

  2. 02

    Add Watch Contacts (New)

    Search for SendGrid, pick Watch Contacts (New), and select the connection you made earlier (or click Create a connection if you skipped it). Fill in the fields the module shows.

  3. 03

    Add Send an Email

    Click the + on the right of the trigger and choose SendGrid Send an Email. Map the contact's details coming from the first module into its fields, so each email goes to the person who just arrived.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed along, here one contact). Check the email landed in a test inbox.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and paid plans go down to 1 minute. Set the rhythm you want and switch the scenario on.

Triggers

What can start a SendGrid scenario?

3 modules start a scenario when something happens in SendGrid. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SendGrid as soon as it happens.

SendGrid1Watch Contacts (New)

Watch Contacts (New)

triggerIn the docs only

This trigger picks up contacts from the current SendGrid contacts system and hands each one to the rest of the scenario as its own bundle, so every new person can get their own follow-up.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, down to 1 minute on paid plans.
When to use it
you add people in SendGrid directly, through an import for instance, and want other tools, or a welcome email, to follow.
Watch out
each module run counts as an operation, the unit Make tracks on your plan, so pick the schedule with that in mind.
SendGrid2Watch New Lists (Legacy)

Watch New Lists (Legacy)

triggerIn the docs only

Here the scenario starts whenever a list appears in the older SendGrid contacts system. Each list comes through as a bundle, handy for logging it elsewhere or preparing the tools around it.

How it fires
scheduled, Make checks the app on the scenario's schedule rather than being told by SendGrid.
When to use it
your account has used the Legacy modules for a long time and your lists still live there.
Watch out
Legacy modules do not work for new users, since their API key lacks the required scopes. On a recent account, stick to the New modules.
SendGrid3Watch New Recipients (Legacy)

Watch New Recipients (Legacy)

triggerIn the docs only

Recipients were the name for contacts in the older SendGrid system. This trigger catches the ones added there and passes each person along, ready to copy into a CRM or a spreadsheet.

How it fires
scheduled, Make looks at SendGrid at the pace set on the scenario's clock, 15 minutes unless you change it.
When to use it
an older account still collects people in Legacy lists and the sales team wants them in its own tool.
Watch out
if the connection was created on a newer account, this module fails for lack of scopes. Use Watch Contacts (New) there.
Modules

What can the SendGrid modules do in Make?

SendGrid gives you 26 modules in 6 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Contacts (New)

7 modules
SendGrid1

Create a List (New)

ActionIn the docs only

Opens a fresh contact list in SendGrid from inside a scenario, so the list exists before any contact is pushed into it. Useful when the list name comes from another app, like a product launch or a new event.

When to use it
a new webinar gets created in your events tool and you want its own mailing list ready.
Watch out
run it only once per event, or you end up with duplicate lists sharing the same name.
SendGrid2

Add or Update a Contact (New)

ActionIn the docs only

The workhorse of the app. It adds a person to your SendGrid contacts or refreshes their details when they are already there, so you do not have to check first whether the address exists.

When to use it
someone fills a form, buys on your store or changes stage in the CRM, and SendGrid should know right after.
Watch out
map the email carefully from the previous module; a wrong mapping updates the wrong person.
SendGrid3

Get All Lists (New)

ActionIn the docs only

Returns the lists of your SendGrid account so the scenario can see what already exists and reuse it. Think of it as reading the table of contents before writing.

When to use it
before creating a list, to check whether one with that name is already there, or to copy every list name into a sheet for an audit.
Watch out
it can bring back many bundles, and each module after it runs once per list.
SendGrid4

Get all Contracts (New)

ActionIn the docs only

Make displays this module as Contracts, yet the doc files it under Contacts (New), so read it as the module that pulls your contacts in bulk. Each one arrives as a bundle you can send elsewhere.

When to use it
a one-off export of your SendGrid audience into a CRM or a data warehouse.
Watch out
run it on a real test first with Run once to check what it returns before chaining costly steps.
SendGrid5

Delete a List (New)

ActionIn the docs only

Removes a list from SendGrid for good. It fits the end of a project, when the event list or the seasonal segment has served its purpose and only clutters the account.

When to use it
an event is marked as finished in your project tool and its list should go with it.
Watch out
place a filter in front of it so only the right list goes, and test with Run once before switching the scenario on.
SendGrid6

Delete Contracts (New)

ActionIn the docs only

Despite the Contracts label, this sits in the Contacts (New) group, which points to deleting contacts from your account. It helps honor a request to forget someone across your stack.

When to use it
a person asks for their data to be erased and the request lands in your ticketing tool.
Watch out
deleting a contact is not the same as silencing them. If you only want them to stop receiving emails, a global suppression is the gentler move.
SendGrid7

Remove Contracts from a List (New)

ActionIn the docs only

Filed under Contacts (New) despite its Contracts label, so read it as taking people out of one list while leaving them in your SendGrid account. The contact stays, only the membership changes, which suits moving someone from one segment to another.

When to use it
a customer cancels their subscription and should leave the list of active members.
Watch out
pair it with Add or Update a Contact (New) when the person must join another list at the same time.

Contacts (Legacy)

8 modules

Legacy modules are for users, who started to use these SendGrid modules before July 2019. Legacy modules do not work for new users as they don't have the required scopes within the API key.

SendGrid8

Create a List (Legacy)

ActionIn the docs only

Same idea as its New counterpart, but for the older contacts system of SendGrid. It creates a list there, for accounts that still run their marketing on Legacy data.

When to use it
your team has not migrated yet and keeps organizing recipients in Legacy lists.
Watch out
a key made on a newer account lacks the scopes Legacy modules require, so the module errors out. Test it with Run once first.
SendGrid9

Add or Update Recipient (Legacy)

ActionIn the docs only

Writes a person into the Legacy recipients base, adding them or refreshing their details if they already exist. It keeps an older account fed from your forms or shop.

When to use it
an account that has run on Legacy data for years and still sends from those lists.
Watch out
it does not touch the New contacts. If your account uses both systems, decide which one is the reference before building.
SendGrid10

Add Recipients to a List (Legacy)

ActionIn the docs only

Places recipients who already exist in the Legacy base into a given list. Where Add or Update Recipient creates the person, this module sorts them.

When to use it
after creating or updating a recipient, to file them in the list matching their language or product.
Watch out
the recipient must exist first, so run the add or update step earlier in the same scenario.
SendGrid11

Get All Lists (Legacy)

ActionIn the docs only

Reads every list of the older contacts system and returns them one by one. It gives you a clear inventory before a migration or a cleanup.

When to use it
you are preparing the move to the New system and want a sheet of the Legacy lists to decide what to keep.
Watch out
each list becomes a bundle, and each module after it spends an operation per bundle.
SendGrid12

Get All Recipients (Legacy)

ActionIn the docs only

Pulls the people stored in the Legacy base so you can copy them elsewhere. It is the export button, only automated and pointed at the tool of your choice.

When to use it
moving an older audience into a CRM, or backing it up in a spreadsheet before cleaning.
Watch out
a large base means many bundles and many operations downstream; test on a small scope with Run once.
SendGrid13

Delete a List (Legacy)

ActionIn the docs only

Erases a list from the older contacts system. Handy to finish a cleanup once you have confirmed the list is empty or no longer mailed.

When to use it
after migrating a Legacy list to the New system, to avoid two copies drifting apart.
Watch out
keep a copy through Get All Recipients (Legacy) before deleting anything that still matters.
SendGrid14

Delete Recipients (Legacy)

ActionIn the docs only

Wipes recipients from the Legacy base entirely, not just from one list. It answers erasure requests on accounts that still hold people in the older system.

When to use it
a deletion request comes in and the person exists only in your Legacy data.
Watch out
the person disappears for good. To keep them but stop mailing, look at Add Emails to Global Suppression instead.
SendGrid15

Delete Recipients from a List (Legacy)

ActionIn the docs only

Detaches recipients from a single Legacy list and leaves them in the base. Think of it as moving a card out of a folder without shredding it.

When to use it
a subscriber changes preference in your app and should leave one Legacy list but stay reachable in others.
Watch out
do not confuse it with Delete Recipients (Legacy), which removes the person from the whole account.

Bounces

2 modules
SendGrid16

Get All Bounces

ActionIn the docs only

Fetches the addresses SendGrid could not deliver to. Each bounce becomes a bundle you can log, flag in a CRM or send to the person in charge of data quality.

When to use it
your sales team keeps mailing leads whose address is dead, and you want their CRM records marked.
Watch out
reading bounces fixes nothing on its own; decide what the scenario does with each address before you switch it on.
SendGrid17

Delete Bounces

ActionIn the docs only

Clears addresses from the SendGrid bounce list so they can receive mail again. It makes sense once the underlying problem has been fixed, like a full mailbox or a typo corrected by the customer.

When to use it
support confirms a customer's new valid address and wants the old bounce gone.
Watch out
tie it to a confirmed correction rather than to a bulk cleanup of the whole list.

Blocks

3 modules
SendGrid18

List Blocks

SearchIn the docs only

A search that returns the addresses the receiving servers blocked. It can come back with zero, one or many results, each one ready to be checked or logged.

When to use it
a customer complains they never got a password reset and you want to see whether their domain is blocking you.
Watch out
with no result, the next modules simply do not run, which is normal and not an error.
SendGrid19

Get a Block

ActionIn the docs only

Looks up one precise address in the block list and returns what SendGrid holds about it. More targeted than List Blocks when you already know who you are looking for.

When to use it
a support ticket arrives with the customer's email, and the agent needs to know right away if that address is blocked.
Watch out
map the address from the ticket field, not typed by hand, so the lookup targets the right person.
SendGrid20

Delete Blocks

ActionIn the docs only

Lifts blocks so SendGrid tries those addresses again. It closes the loop after the receiving side has resolved whatever caused the refusal.

When to use it
your IT contact at a client company confirms their filter now accepts your emails.
Watch out
run Get a Block first to be sure you target the right address.

Global Suppressions

4 modules
SendGrid21

List Global Suppressions

SearchIn the docs only

Searches the addresses that asked never to receive your emails, across every list. The result can be empty or long, one bundle per address.

When to use it
syncing opt-outs into your CRM so the sales team stops contacting people who unsubscribed.
Watch out
treat this list as a promise to your contacts; share it with the tools that send mail, never use it as a target list.
SendGrid22

Get a Global Suppression

ActionIn the docs only

Checks whether one given address is globally suppressed. A quick yes or no before your scenario does anything else with that person.

When to use it
just before adding someone who registered for your webinar, to make sure they had not unsubscribed earlier.
Watch out
place a filter right after it, so the rest of the scenario stops when the address is suppressed.
SendGrid23

Add Emails to Global Suppression

ActionIn the docs only

Tells SendGrid to stop sending to one or more addresses, whatever the list or campaign. It is how you honor an opt-out collected outside SendGrid.

When to use it
a customer unsubscribes from your CRM, your help desk or a preference page, and SendGrid must follow.
Watch out
the suppression covers every list and campaign at once, so keep it for a real opt-out, not a single-list preference.
SendGrid24

Delete a Global Suppression

ActionIn the docs only

Removes an address from the global suppression list, allowing mail to reach it again. It is the reverse move, meant for a person who opts back in on purpose.

When to use it
a former subscriber signs up again through a form with explicit consent.
Watch out
only trigger it from a clear consent action, never from a simple import, or you mail people who said no.

Other

2 modules
SendGrid25

Send an Email

ActionIn the docs only

Sends a message through your SendGrid account, straight from the scenario. The content can mix fixed text and data mapped from earlier modules, like a name or an order number.

When to use it
a transactional moment in another tool, a quote accepted or a ticket closed, deserves a proper email.
Watch out
test with Run once on your own address first; a wrong mapping sends the wrong content to a real customer.
SendGrid26

Make an API Call

ActionIn the docs only

The open door of the app: it calls any endpoint of the SendGrid API with the connection you already set up. Whatever the other SendGrid modules leave out goes through here.

When to use it
you need something no listed SendGrid module offers.
Watch out
you write the request yourself, so keep the SendGrid API reference open and test it with Run once before wiring the next step.
Need help

Need help automating SendGrid with Make?

A person reads every message.

FAQ

Questions about SendGrid and Make

01Is the SendGrid Make integration free?
Yes, SendGrid is a standard app, so it works from the Make Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Every module run counts as an operation on your plan, so a busy scenario uses your allowance faster. Paid plans (Core, Pro, Teams, Enterprise) lift the scenario cap and drop the interval to 1 minute.
02What do you need to connect SendGrid to Make?
A SendGrid account and an API key. In SendGrid, go to Settings, open API Keys, click Create API Key and give it Full Access. Copy the value. Then, in Make, add any SendGrid module, click Create a connection, paste the key in the API key field and save. If asked, confirm access. The connection is reused by all 29 SendGrid modules, so you do this only once per account, not once per module.
03Do SendGrid triggers in Make fire the moment something happens?
No. The doc gives no type for the 3 SendGrid triggers, but their Watch names point to scheduled ones: Make checks SendGrid on the scenario's schedule instead of being called by it. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Paid plans can go down to 1 minute. There is no instant trigger in this app, the kind that SendGrid would call through a webhook as soon as something happens. Plan for that small delay.
04What if a SendGrid module is missing in Make?
Use Make an API Call. It reaches any endpoint of the SendGrid API with the connection you already have, so whatever the listed modules leave out is still within reach. You write the request yourself, following the SendGrid API reference. The doc lists no numeric limit for this app. One common snag is not a missing module at all: the Legacy contact modules fail on recent accounts, and the New modules are the ones to use.
05Should you use Make or n8n for SendGrid?
It depends on where your other automations already run. SendGrid is available in both tools, and each one has its own integration page on this site. In Make you get 29 ready modules covering contacts, bounces, blocks, global suppressions and sending, plus Make an API Call for the rest, all through a visual editor. If your team already builds in n8n, keeping SendGrid there avoids splitting your automations across two places. Pick the tool your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations