- Integrations
- /
- SendGrid
- /
- Actions
- /
- Send Email
ActionSendGridUpdated May 2026
How do I send an email via SendGrid?
Short answer: Drop the "SendGrid → Send Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
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 |
Sample request
{"to_email": "recipient@example.com","from_email": "sender@example.com","from_name": "Your Name","subject": "e.g. Welcome aboard!","content": "{{trigger.content}}"}
Returns
{"id": "msg_sen_123","status": "sent","success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send Email.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send Email.
What does the Send Email action do in SendGrid?
Sends a transactional email via SendGrid with from, to, subject, HTML/plain content, and optional CC/BCC/attachments/reply-to. The bread-and-butter SendGrid action.
What inputs does Send Email require?
Required: To Email, From Email, Subject, Content (HTML). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if SendGrid returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Send Email support batch operations?
Yes. Run Send Email inside a Loop node to process arrays. Tiny Command handles SendGrid's rate limits automatically so you don't have to throttle manually.
More actions
Other SendGrid actions.
Action
Add or Update Contact
Adds or updates (upserts) a contact in SendGrid marketing with email, name, custom fields, and list memberships. Used to keep your audience in sync with your CRM or product DB.
ActionCreate List
Creates a new contact list in SendGrid. Use to spin up campaign-scoped audiences from your CRM segments.
ActionDelete Contact
Deletes one or more SendGrid contacts by ID. Used for GDPR/CCPA right-to-delete requests or for unsubscribe cleanup.
ActionDelete List
Deletes a SendGrid contact list (the contacts themselves are not deleted, just removed from the list). Use to retire one-off campaign audiences.
ActionFind Contact by Email
Searches for a SendGrid contact by email and returns the record with custom fields and list memberships. The standard upsert lookup before deciding to add or update.
ActionGet List
Returns a SendGrid contact list by ID with name and contact count. Use to render a list-detail view or to validate a list reference.
Send send email from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.