SendGrid

Overview

The SendGrid connector sends mail through the v3 Mail Send API and listens to the Event Webhook for what happens after. Each event carries the message ID Tessel set when sending, so a bounce or click is linked back to the exact run and step.

Teams use it to send receipts when a Stripe charge succeeds, to pause outreach in HubSpot after a hard bounce and to parse replies to a support address with Inbound Parse.

Event coverage

• Delivery events: processed, delivered, deferred, bounce and dropped

• Engagement events: open, click, spamreport and unsubscribe

• Inbound Parse for mail sent to a domain you own

How the Event Webhook works

SendGrid batches events and posts them to Tessel. Tessel verifies the signed webhook with your public key, splits the batch into single events and drops duplicates by sg_event_id, so retries from SendGrid never start a workflow twice.

PATCH /v3/user/webhooks/event/settings
{
  "enabled": true,
  "url": "https://hooks.tessel.dev/sendgrid",
  "delivered": true,
  "bounce": true,
  "click": true
}

PATCH /v3/user/webhooks/event/settings
{
  "enabled": true,
  "url": "https://hooks.tessel.dev/sendgrid",
  "delivered": true,
  "bounce": true,
  "click": true
}

PATCH /v3/user/webhooks/event/settings
{
  "enabled": true,
  "url": "https://hooks.tessel.dev/sendgrid",
  "delivered": true,
  "bounce": true,
  "click": true
}

Idempotency

Each send uses a custom_args run key. If a step retries after a timeout, Tessel checks that key first, so the customer gets one email, not two.

Permissions needed

Create a restricted API key for Tessel. It needs Mail Send and access to the templates it uses. Webhook settings access is only needed while Tessel configures the Event Webhook.

• mail.send to send mail

• templates.read for dynamic templates

• user.webhooks.event.settings.update to set up the Event Webhook