Connector · Messaging and email
SendGrid, in every client’s workflows.
Send an email, send a template email, or start when an email bounces, with the client’s own SendGrid account.
- Triggers
- 2start a workflow
- Actions
- 2steps in a workflow
Start a workflow when something happens in SendGridBeta
By webhook where SendGrid sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if SendGrid turns it off the alert carries a Reconnect button.
- An email bouncesWebhookAn email bounced, within seconds. The API key needs Event Webhook access (Mail Send alone cannot make one), and each trigger uses one of the plan’s event webhooks.
- A link in an email is clickedWebhookA tracked link clicked, within seconds. The API key needs Event Webhook access.
Do it in SendGrid
A step with its own fields: values from the run go in by name, and what SendGrid answers is there for the next step.
- Send an emailPlain-text email from a verified sender.
- Send a template emailAn email from one of the client’s SendGrid dynamic templates, its variables filled from the run. The template sets the subject and content.
Connect the client’s SendGrid
On the client’s page in Thrum: Add credential, type SendGrid API key.
SendGrid → Settings → API Keys → Create API Key with Mail Send access; for the triggers, also the Event Webhook settings permission (user.webhooks.event.settings.read and user.webhooks.event.settings.update), or Full Access. The From address must be a verified sender.
The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.
Watched like everything else
When SendGrid stops answering or refuses the client’s key, you hear about it, and your client does not.
- A failing request
- Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
- A service that asks for a pause
- Given it, up to an hour
- Requests at once, per account
- 2, per worker; the rest wait their turn
- Timeout
- 15 seconds, unless the step sets its own
- Private and internal addresses
- Refused, on every redirect too
- The client’s key
- Encrypted, bound to the client, and kept out of every run record
- A step that keeps failing
- Marks the workflow Degraded and alerts you, not the client
SendGrid and its logo are trademarks of their owner, 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.