SendGrid ➔ n8n Payload Specification
Technical reference for automating data exchange between Email API and Workflow Automation workflows.
💡 How this integration works:
1. SendGrid triggers an event when email.delivered occurs.
2. Data is packaged into a standard JSON webhook payload.
3. Payload is delivered into your n8n intake pipeline and mapped to your Workflow Automation targets.
Authentication & Event Specs
| Parameter | Source (SendGrid) | Destination (n8n) |
|---|---|---|
| Auth Mechanism | Bearer API Key | Header Auth / Basic |
| Trigger Event | email.delivered | Ingest Pipeline |
Sample Webhook JSON Payload
{
"event": "email.delivered_to_n8n",
"timestamp": 1788105199,
"source": {
"platform": "SendGrid",
"auth_mode": "Bearer API Key",
"data": {
"msg_id": "sample_msg_id_val",
"recipient": "sample_recipient_val",
"event_type": "sample_event_type_val",
"smtp_code": "sample_smtp_code_val"
}
},
"destination": {
"platform": "n8n",
"auth_mode": "Header Auth / Basic",
"target_endpoint": "https://api.n8n.com/v1/ingest",
"mapped_fields": {
"execution_id": "{{source.msg_id}}",
"workflow_name": "{{source.recipient}}",
"node_output": "{{source.event_type}}",
"timestamp": "{{source.smtp_code}}"
}
}
}
Quick Integration Setup
- Retrieve your secret API credentials from your SendGrid developer dashboard using authentication method
Bearer API Key. - Configure the target endpoint URL to route payloads into the n8n intake pipeline.
- Map incoming schema properties according to the JSON specification detailed above.
Expected HTTP Response Codes
| Status Code | Meaning | Troubleshooting Step |
|---|---|---|
200 OK | Success | Payload accepted and queued for routing. |
401 Unauthorized | Auth Failure | Verify headers for valid Bearer API Key credentials. |
422 Unprocessable | Schema Error | Check field keys alignment between source and target payload. |