Send Email
Send Email delivers a one-way email through one of your connected email inboxes without leaving the flow. You pick the connector that sends, define the recipient — a literal address or a flow variable — and compose a subject and body with full {{variable}} support. The node sends and moves on immediately; it does not wait for a reply. To react to replies, pair it with a Read Incoming node later in the flow.
The body can be plain text or HTML, and can optionally be wrapped in the connector's branded template so every email carries your header, colors and footer.
Configuration
| Option | Description |
|---|---|
connectorId | The email connector (inbox) that sends the message |
recipientType | literal for a typed address, or variable to read it from a flow variable |
to | The literal recipient address. Supports {{variables}} |
recipientVariable | The string variable holding the recipient when recipientType is variable |
cc / bcc | Optional comma-separated address lists. Support {{variables}} |
subject | The email subject. Supports {{variables}} |
body | The email body. Supports {{variables}} |
contentType | text or html |
useBrandedTemplate | Wraps the body in the connector's branded email template |
attachments | List of attachments, each a variable holding a file URL plus an optional filename |
Output Handles
| Handle | When |
|---|---|
| Next | The email was handed to the email provider and the flow continues |
There is no dedicated error handle. If sending fails — missing connector, invalid recipient or a provider error — the node records a failure notice and routes through the flow's error path, falling back to the connector's default responder.
Things to Know
Invalid addresses behave differently per field. An invalid main recipient fails the node outright; invalid entries in cc or bcc are silently dropped and the email still goes out to the valid ones.
HTML is sanitized and gets a plain-text twin. When contentType is html the body is sanitized before sending and a plain-text version is generated automatically for clients that prefer it.
The inbox signature is appended automatically. If the connector has an email signature configured, it is added after the body — with or without the branded template.
Attachments come from variables, not uploads. Each attachment points to a variable that holds a file URL (for example from a Create PDF or Ask File node); attachments whose variable is empty at runtime are skipped.