Per-pair page

Connect SendGrid to Slack in two minutes.

Real-time triggers from SendGrid, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect SendGrid to Slack — start free See reverse direction

Trigger app

SendGrid as the trigger

Workflows fire when something happens in SendGrid.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Connect SendGrid to Slack — start free

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

SendGrid → Slack

When something happens in SendGrid, do it in Slack.

3 SendGrid triggers wired to 45 Slack actions. Most-used pairing: Email Delivered → Raw API Request.

Slack → SendGrid

Or fire it the other way around.

13 Slack triggers wired to 11 SendGrid actions downstream.

See Slack → SendGrid →

Popular pairings

Common SendGrid → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 135 combinations

When email delivered in SendGrid, raw api request in Slack.

Fires when an email is successfully delivered to the recipient mail server via SendGrid. Use to reconcile sends or to advance a sequence once the previous mail has actually landed.

When email delivered in SendGrid, add reaction in Slack.

Fires when an email is successfully delivered to the recipient mail server via SendGrid. Use to reconcile sends or to advance a sequence once the previous mail has actually landed.

When email delivered in SendGrid, archive channel in Slack.

Fires when an email is successfully delivered to the recipient mail server via SendGrid. Use to reconcile sends or to advance a sequence once the previous mail has actually landed.

When email delivered in SendGrid, cancel scheduled message in Slack.

Fires when an email is successfully delivered to the recipient mail server via SendGrid. Use to reconcile sends or to advance a sequence once the previous mail has actually landed.

When email link clicked in SendGrid, raw api request in Slack.

Fires when a recipient clicks a link in an email sent via SendGrid. Common use: lead-scoring, sales-rep alerts, or branch automation based on engagement.

When email link clicked in SendGrid, add reaction in Slack.

Fires when a recipient clicks a link in an email sent via SendGrid. Common use: lead-scoring, sales-rep alerts, or branch automation based on engagement.

When email link clicked in SendGrid, archive channel in Slack.

Fires when a recipient clicks a link in an email sent via SendGrid. Common use: lead-scoring, sales-rep alerts, or branch automation based on engagement.

When email link clicked in SendGrid, cancel scheduled message in Slack.

Fires when a recipient clicks a link in an email sent via SendGrid. Common use: lead-scoring, sales-rep alerts, or branch automation based on engagement.

When email opened in SendGrid, raw api request in Slack.

Fires when a recipient opens an email sent via SendGrid. Note that Apple Mail Privacy Protection prefetches images, so open events from Apple Mail users are unreliable.

How it works

Connect SendGrid and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize SendGrid and Slack
Open TinyCommand, authorize SendGrid and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a SendGrid trigger
Drop the SendGrid → Email Delivered trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/sendgrid.trigger-email-delivered
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the SendGrid payload into the Slack inputs.
slack.api-request
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about SendGrid + Slack.

How long does it take to connect SendGrid and Slack on TinyCommand?

Under two minutes. Authorize SendGrid and Slack once each, drop the SendGrid trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the SendGrid ↔ Slack integration real-time?

Yes. Both SendGrid and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between SendGrid and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What SendGrid events can trigger a Slack workflow?

Any of the 3 SendGrid triggers, including "Email Delivered". Each fires in real time when the matching event happens in SendGrid.

Do I need a paid plan to use SendGrid with Slack?

No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.

What if I want Slack → SendGrid instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/sendgrid page with the reverse-direction triggers and actions.

Other apps that pair well with SendGrid.

SendGrid + Gmail

SendGrid + Google Sheets

Spreadsheets & Databases

Spreadsheets & Databases

Connect SendGrid to Slack — start free