Send email
Description
Sends an email from the Flovello no-reply address. To, CC and BCC each accept one address or a comma-separated list (at least one To address, at most 50 recipients in total). Branches on success/error and outputs the provider messageId on success. To prevent abuse, every recipient must be an active member of the pipeline's organization or a verified destination — any other address fails the whole send on the error branch.
When to use
Use Send email to deliver notifications, reports, or alerts from a pipeline. The
email is sent from Flovello’s shared no-reply address, so no SMTP credentials are
needed. Send one message to several people by listing them comma-separated in
To, CC or BCC. Use BCC when recipients should not see each other’s addresses.
Provide both htmlBody and textBody for maximum compatibility. Wire
upstream Concatenate strings nodes to build dynamic subjects or bodies. The
success pin fires with a messageId on delivery; the error pin fires if the
send fails so you can Log message or Fail accordingly.
Pins
Input pins
| Pin | Type | Default | Notes |
|---|---|---|---|
| To | string | — | The recipient email address, or a comma-separated list such as `anna@example.com, erik@example.com`. At least one address is required. Each must be an active member of the pipeline's organization or an address verified as a destination in Settings. |
| CC | string | — | Optional carbon-copy recipients, as one address or a comma-separated list. Visible to every recipient. The same member-or-verified-destination rule applies. |
| BCC | string | — | Optional blind carbon-copy recipients, as one address or a comma-separated list. Hidden from the other recipients. The same member-or-verified-destination rule applies. |
| Subject | string | — | The email subject line. |
| HTML body | string | — | The HTML body of the email. Used when the recipient's client supports HTML. |
| Text body | string | — | The plain-text fallback body. Shown when the client does not render HTML. |
Output pins
| Pin | Type | Notes |
|---|---|---|
| Message ID | string | The provider-assigned message ID, available on the `success` branch. Useful for logging or auditing. |
Execution pins
| Pin | Direction |
|---|---|
| In | Input |
| Success | Output |
| Error | Output |
Example
Send a daily report email and log the message ID on success. Set the To, Subject, HTML body, and Text body inputs on Send email and wire the execution output of Cron schedule into its execution input. On the Success execution output, wire the Message ID output into the Message input of Log message. Wire the Error execution output to a Fail node so failed deliveries surface in the execution log.