Skip to main content
Technical Preview

Overview

A client-mode connector for a curated messaging slice of the Twilio SendGrid API v3: Default BASE_ADDRESS is https://api.sendgrid.com/v3. Topics use messaging/sendgrid/<object>/<verb>.
All events send Authorization: Bearer {api_key}. Prefer Hub secret SENDGRID_API_KEY. Inbound Event Webhook (delivered / bounce / open) → MQTT is out of scope for this client-mode package. EU regional subusers may use https://api.eu.sendgrid.com/v3.

Basic Syntax

Events

Auth

  1. Create an API key in the SendGrid UI with Mail Send (and preferably Template Engine Read) scopes. Use a verified sender identity for from.
  2. Set connector BASE_ADDRESS to https://api.sendgrid.com/v3 (or https://api.eu.sendgrid.com/v3 for EU regional).
  3. Pass api_key on the MQTT payload so Authorization: Bearer {value.json.api_key} resolves.
  4. Store the key in Hub / GET SECRET "SENDGRID_API_KEY". Never commit real credentials.
  5. Successful GET /user/profile returns HTTP 200. POST /mail/send returns 202 Accepted. GET /templates returns 200 with a paged result array.

Example payloads

getUserProfile:
sendMail (raw):
sendMail (dynamic template):
listTemplates:

Install

  1. The template ships with the broker. List it with -listTemplates or fetch it from the Hub catalog.
  2. Deploy with -addConnector from SendGridRestApi.lot (not hub-metadata.lot).

See also

Last modified on October 26, 2026