Connectors
SendGrid
Connect SendGrid for API-based delivery with normalized GenieOS send timelines and suppression checks.
Use the SendGrid connector when your team already manages sender identity, domain authentication, reputation, or billing in SendGrid.
Before you start
- Create a restricted SendGrid API key with mail send permissions.
- Authenticate your sending domain in SendGrid.
- Keep access to Event Webhook settings.
Setup
sequenceDiagram
participant Admin as Workspace admin
participant MG as GenieOS
participant SG as SendGrid
participant Recipient as Recipient
Admin->>SG: Create restricted API key
Admin->>MG: Install SendGrid connector
MG->>SG: Send test via Mail Send API
SG->>Recipient: Deliver message
SG->>MG: Event Webhook callbacks
MG->>Admin: Show normalized timeline- Open Settings -> Connectors and choose SendGrid.
- Paste the API key and configure sender defaults.
- Copy the webhook URL and signing details from GenieOS.
- Add the Event Webhook in SendGrid and enable delivery, bounce, spam report, open, click, and unsubscribe events as needed.
- Send a test message.
Capabilities
| Capability | Support |
|---|---|
| Transactional sends | Yes |
| Broadcast sends | Yes |
| Attachments | SendGrid limits apply |
| Inline images | SendGrid limits apply |
| Webhooks | Event Webhook normalization |
| Suppressions | Provider events can create GenieOS suppressions |
Webhooks and suppressions
SendGrid spam reports, hard bounces, and unsubscribe events should flow back to GenieOS when enabled in the Event Webhook. GenieOS checks local suppressions before every SendGrid handoff.
Troubleshooting
403responses usually mean the API key lacks Mail Send permissions.- Sender errors usually mean the
fromdomain is not authenticated in SendGrid. - Missing event data usually means the Event Webhook does not include the relevant event type.
Keep SendGrid click and open tracking settings aligned with your privacy and consent policy before enabling those webhook event types.