Skip to content
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.

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 →
Both directions

Pick the way that fits your stack.

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

SendGridSlack

When something happens in SendGrid, do it in Slack.

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

SlackSendGrid

Or fire it the other way around.

13 Slack triggers wired to 11 SendGrid actions downstream.

See SlackSendGrid
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. 1
    Connect
    Authorize SendGrid and Slack

    Open Tiny Command, authorize SendGrid and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a SendGrid trigger

    Drop the SendGrid → Email Delivered trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/sendgrid.trigger-email-delivered
  3. 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. 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. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command 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 Tiny Command?
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. There's a free tier that covers most SendGrid+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
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.
Related

Other apps that pair well with SendGrid.


Wire SendGrid to Slack in 2 minutes.

Free tier available. No credit card. No onboarding call.