Short answer: Drop the "SendGrid → Send Template Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
To Email to_email | string | Required | To Email. e.g. "recipient@example.com" |
From Email from_email | string | Required | From Email. e.g. "noreply@company.com" |
From Name from_name | string | Optional | From Name. e.g. "Your Company" |
Template ID template_id | string | Required | SendGrid Dynamic Template ID — starts with 'd-'. Find in SendGrid > Dynamic Templates. |
Template Data (JSON) dynamic_data | string | Optional | Dynamic template variables |
{"to_email": "recipient@example.com","from_email": "noreply@company.com","from_name": "Your Company","template_id": "e.g. d-abc123def456","dynamic_data": "{\"name\": \"John\", \"order_id\": \"12345\"}"}
{"id": "msg_sen_123","status": "sent","success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.