Using Send Email Nodes

Send emails from your workflow using the send email node.

Overview

The Send Email node sends a single email from your workflow to one or more recipients. It is the quickest way to add notifications, alerts, status reports, or customer-facing messages without configuring a dedicated email connector.

Send Email is a focused alternative to a generic Connector node calling a Gmail or SendGrid tool. Reach for it when you just need to deliver a message; reach for a connector when you need provider-specific features like templates, scheduling, or campaign tracking.

Configuration

1. Drop a Send Email node onto the canvas.
2. Add one or more To recipient addresses. Template expressions are supported.
3. Write the Subject. Template expressions are supported.
4. Write the Body. Template expressions are supported.
5. Optionally set a Reply-To address.
6. Choose error behaviour: fail the step or continue.

Configuration Reference

• To - one or more recipient addresses, comma separated or as a list.
• Subject - single-line string, accepts {{ }} expressions.
• Body - multi-line string, accepts {{ }} expressions.
• Reply-To - optional address recipients reply to.
• On error - Fail the step stops the workflow; Continue logs the error and proceeds.

Usage Examples

• Shipment notification - subject Order {{ step1.order_number }} has been shipped with a body that references {{ step2.tracking_number }} and {{ step2.carrier }}.
• Internal alert - a Condition node detects a failure path and a Send Email node notifies an on-call address with the relevant execution details.

Tips

• Build the body in a Transform node (plaintext mode) first if you need rich templating or shared layout across multiple emails.
• For repeated sends across a list of recipients, wrap the node in a Loop and reference {{ item.email }}.
• Use a dedicated Reply-To address (for example a shared inbox) so replies do not end up at the workflow owner.

Common Pitfalls

• An empty or malformed To field fails the step. Validate the source field before sending.
• Body content is plain text by default. HTML markup will be visible as raw tags unless the provider negotiates HTML rendering.
• Setting error behaviour to Continue silently swallows delivery failures. Pair it with logging or a fallback path so problems are visible.

Related Articles

• Using Transform Nodes (Plaintext Mode)
• Working with Variables and Templates
• Using Connector Nodes in Direct Mode
• Understanding Retry and Error Handling

Learn More

• Send email node documentation