Send an Email from a Pipeline¶
The Send an Email node lets your chatbot trigger an email at any point in a pipeline — without stopping or altering the conversation. Use it to notify an administrator, send a summary to a participant, or alert your team when something important happens.
Note
This node is a passthrough: its output is identical to its input. The email is sent, and the pipeline continues as normal.
Prerequisites¶
- A pipeline with at least one node before the Send an Email node to provide input.
- If you plan to address emails dynamically (e.g. to the participant's own address), the email address must already be stored in participant data or session data.
Add and configure the node¶
- Open your pipeline in the pipeline editor.
- Add a Send an Email node at the point in the flow where the email should be triggered.
- Connect it to the upstream node that provides the content you want to send.
- Fill in the Subject, Recipient, and optionally the Body fields (see below).
- Connect the node's output to the next step in your pipeline.
Field reference¶
Subject¶
Accepts a plain string or use template variables to personalize the subject line.
Examples:
| Goal | Value |
|---|---|
| Fixed subject | Weekly check-in summary |
| Include participant identifier | Update for {{ participant_details.identifier }} |
| Include a value from participant data | Report for {{ participant_data.name }} |
Recipient¶
Accepts a comma-separated list of email addresses. See the Recipient Field Syntax reference for advanced usage.
Body¶
Optional. Accepts a plain string or a Jinja2 template. See Body Field Behavior reference for details and an example.
When left blank, the node's input is used as the email body. This is useful when the previous node in the pipeline has already produced the text you want to send.
Template variables¶
The variables available for the Subject, Recipient, and Body fields are listed here.
Example use cases¶
Notify your team of an emergency
Use a Router node to detect whether the user needs urgent assistance. In the router's emergency branch, add the Send an Email node with the recipient set to your team address and the body describing the situation. This lets you escalate extraordinary circumstances — such as a user in crisis — without waiting for the session to end.
Route a completed intake form to the right team member
After a bot collects structured information from a user (such as a support request or referral), use an LLM node to extract the key details, then add the Send an Email node to forward them to the appropriate contact. Set the recipient using a participant data field (e.g. {{ participant_data.assigned_caseworker_email }}) and use the LLM output as the body.
Alert your team when a threshold is reached
After an Increment counter tool updates a counter in participant data, use a router to check the value. When the threshold is met, route to the Send an Email node to trigger an alert.