Connect SendGrid and Zendesk
Start a client’s workflow in SendGrid and act in Zendesk, or the other way round, on the client’s own accounts.
Each app by itself: SendGrid integration and Zendesk integration, with how to connect it, its scopes and its limits.
What the pair is used for
- When a customer’s email bounces, SendGrid opens a Zendesk ticket with that address as the requester, saying whether it bounced hard or was blocked, why, the server’s answer and the SMTP status, so support knows to reach the person another way.
- A click on a tracked link, such as a “Call me back” link in a follow-up email, can open a ticket for whoever clicked, with the link, their browser, the category and the time.
- New Zendesk tickets, and tickets that reach a chosen status such as solved, can email a manager or a shared inbox through SendGrid with the subject, description, status, priority and type.
Every way SendGrid and Zendesk join
A workflow starts from a trigger in one app and runs a step in the other, on the client’s accounts. Where the library has a starter for it, it installs that pairing into a client switched off; any other pairing is two steps on the canvas.
From SendGrid to Zendesk
| When this happens in SendGrid | This runs in Zendesk | How fast | Starter |
|---|---|---|---|
| An email bounces | Open a ticket | Within seconds | Install the starter |
| An email bounces | Update a ticket | Within seconds | Two steps on the canvas |
| A link in an email is clicked | Open a ticket | Within seconds | Install the starter |
| A link in an email is clicked | Update a ticket | Within seconds | Two steps on the canvas |
From Zendesk to SendGrid
| When this happens in Zendesk | This runs in SendGrid | How fast | Starter |
|---|---|---|---|
| A ticket is opened | Send an email | Within seconds | Install the starter |
| A ticket is opened | Send a template email | Within seconds | Two steps on the canvas |
| A ticket is solved (or reaches a status) | Send an email | Within seconds | Install the starter |
| A ticket is solved (or reaches a status) | Send a template email | Within seconds | Two steps on the canvas |
Set up the starter
Send an email in SendGrid when a ticket is opened in Zendesk
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s Zendesk, for “A ticket is opened”
- 3Connect the client’s SendGrid, for “Send an email”
- 4Fill in SendGrid: From address (For example hello@northside.example)
- 5Fill in Who it goes to (SendGrid) (The address that gets it: yours, or the client’s team)
- 6Switch it on. Within seconds: Zendesk tells us as it happens.

What it produces
The SendGrid step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- From
- hello@lakeview.example
- Subject
- A ticket is opened: Emma Collins
- Text
- A ticket is opened in Zendesk. Subject: Emma Collins Description: I’d like a consultation on Thursday at 10:30, with the $500 deposit. Status: new Priority: 2 Type: new
- To
- emma.collins@example.com
Setup notes for this pair
- The ticket starters need no fields of their own; the requester, subject and body are all filled from the SendGrid event. Every click opens its own ticket, so one person clicking twice makes two.
- Ticket emails go to the address you give in “Who it goes to (SendGrid)”. Zendesk’s event has no requester name or email, so mailing the customer needs a step that finds the user by requester ID first.
Field mapping, starter by starter
Each value a starter’s step is given, and where it comes from. Words in brackets are filled in when it runs; change any of it after installing.
Open a ticket for bounced emails
Open a ticket in Zendesk when an email bounces in SendGrid
| Zendesk value | Filled from |
|---|---|
| Body | An email bounces in SendGrid. Address that bounced: [the email’s email, from SendGrid] bounce (hard) or blocked (soft): [the email’s type, from SendGrid] Why: [the email’s bounce classification, from SendGrid] Their server’s answer: [the email’s reason, from SendGrid] SMTP status: [the email’s status, from SendGrid] |
| Requester email | [the email’s email, from SendGrid] |
| Subject | An email bounces |
Open a ticket for email clicks
Open a ticket in Zendesk when a link in an email is clicked in SendGrid
| Zendesk value | Filled from |
|---|---|
| Body | A link in an email is clicked in SendGrid. Who clicked: [the email’s email, from SendGrid] Link: [the email’s url, from SendGrid] Browser: [the email’s useragent, from SendGrid] Category: [the email’s category, from SendGrid] When (Unix time): [the email’s timestamp, from SendGrid] |
| Requester email | [the email’s email, from SendGrid] |
| Subject | A link in an email is clicked |
Send an email for new tickets
Send an email in SendGrid when a ticket is opened in Zendesk
| SendGrid value | Filled from |
|---|---|
| From | [SendGrid: From address] |
| Subject | A ticket is opened: [the ticket’s subject, from Zendesk] |
| Text | A ticket is opened in Zendesk. Subject: [the ticket’s subject, from Zendesk] Description: [the ticket’s description, from Zendesk] Status: [the ticket’s status, from Zendesk] Priority: [the ticket’s priority, from Zendesk] Type: [the ticket’s type, from Zendesk] |
| To | [Who it goes to (SendGrid)] |
Send an email for solved tickets
Send an email in SendGrid when a ticket is solved (or reaches a status) in Zendesk
| SendGrid value | Filled from |
|---|---|
| From | [SendGrid: From address] |
| Subject | A ticket is solved (or reaches a status): [the ticket’s subject, from Zendesk] |
| Text | A ticket is solved (or reaches a status) in Zendesk. Subject: [the ticket’s subject, from Zendesk] Description: [the ticket’s description, from Zendesk] Status: [the ticket’s status, from Zendesk] Priority: [the ticket’s priority, from Zendesk] Type: [the ticket’s type, from Zendesk] |
| To | [Who it goes to (SendGrid)] |
SendGrid and Zendesk and their logos are trademarks of their owners, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.