GuidesNodes
Send email with dynamic content using placeholders for recipients, subjects, and body text.
Email nodes send an email message via the project's configured email provider. Use them to notify users, deliver reports, or send content generated by upstream nodes such as AI or Code.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| from | string | No | Sender email address. Supports placeholders (for example, {{secrets.fromEmail}}). |
| to | string | No | Recipient email address or addresses. Supports placeholders (for example, {{input.customerEmail}}). |
| subject | string | No | Email subject line. Supports placeholders (for example, Report for {{input.date}}). |
| text | string | No | Plain-text email body. Supports placeholders for dynamic content. |
| html | string | No | HTML email body. Use when you need formatted content with links, images, or styling. Supports placeholders. When both text and html are provided, email clients that support HTML will display the HTML version. |
| replyTo | string | No | Reply-To address. Optional. Supports placeholders. |
Input
The node receives the trigger payload and upstream node outputs. Use placeholders in any configuration field to inject dynamic data -- for example, {{input.customerEmail}} in the to field or {{input.reportBody}} in the html field.
Output
The node produces a result indicating delivery status, typically including a message ID on success or an error on failure. This output is stored in the node execution record and can be passed to downstream nodes.
Tips
- Store sender addresses and provider credentials in Secrets and reference them with placeholders. Never hardcode sensitive values.
- Use
textfor simple notifications. Usehtmlwhen you need links, formatting, or branded templates. - Validate recipient addresses upstream (for example, with a Code node) to avoid failed deliveries.
- Email delivery behavior, rate limits, and sender verification requirements depend on the project's configured email provider.