Short answer: Drop the "SendGrid → Send 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. "sender@example.com" |
From Name from_name | string | Optional | From Name. e.g. "Your Name" |
Subject subject | string | Required | Email subject line. |
Content (HTML) content | string | Required | Content (HTML) |
Content Type content_type | options | Optional | Content Type. Options: HTML, Plain Text |
{"to_email": "recipient@example.com","from_email": "sender@example.com","from_name": "Your Name","subject": "e.g. Welcome aboard!","content": "{{trigger.content}}"}
{"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.