Skip to content

✉️ Send Email Node

Purpose

The Send Email node sends an email notification when the conversation reaches this point in the flow. It's used to alert your team about new leads, support requests, or important events — not to email the customer (they're on WhatsApp).

Business Scenario

Use the Send Email node when you need to:

  • Notify your sales team about a new lead with their captured details
  • Alert support staff about an incoming issue
  • Send internal reports — new booking details, appointment requests
  • Create an audit trail — email records of important customer interactions
  • Trigger workflows — some CRMs and ticketing systems can create tickets from emails

Configuration

Field Description
Title Internal name (e.g., "Notify Support Team")
Send To Who receives the email — Support email (from Settings) or a custom address
Recipient Address Only visible when "Custom address" is selected
Subject Email subject line. Supports {{variable}} placeholders.
Body Email body content. Supports {{variable}} placeholders.

Recipient Types

Type Description
Support email (from Settings) Sends to the email address configured in Settings → Organization. Changing it in Settings applies immediately without republishing.
Custom address A fixed email address entered directly (e.g., [email protected])

Dynamic Support Email

Using Support email is recommended — if your support address changes, you only update it once in Settings. The flow doesn't need republishing.

Properties

Property Type Required Default Description
title Text No "" Internal node name
recipientType Select Yes SUPPORT_EMAIL Where to send the email
customEmail Text Only if Custom — Fixed recipient email address
subject Text Yes "" Email subject line
body Text Yes "" Email body content

Inputs

Handle Type Description
Top (↑) Target Receives a connection from any preceding node

Outputs

Handle Type Description
Bottom (↓) Continue Connects to the next node (the email is sent in the background; the conversation continues immediately)

Non-blocking

The email is sent asynchronously — the customer's conversation continues to the next node without waiting for the email to be delivered.

Connection Rules

  • ✅ Can receive connections from any node type
  • ✅ Can connect to any node type
  • ✅ Commonly followed by a confirmation Message to the customer

Example Flow Diagram

Lead Notification

flowchart TD
    A["📥 Ask Name → {{name}}"] --> B["📥 Ask Email → {{email}}"]
    B --> C["📥 Ask Interest → {{interest}}"]
    C --> D["✉️ Send Email<br/><em>To: [email protected]</em><br/><em>Subject: New Lead - {{name}}</em>"]
    D --> E["💬 Thank You<br/><em>Thanks {{name}}! Our sales team will reach out shortly.</em>"]
    E --> F["📋 Main Menu"]

    style D fill:#ccfbf1,stroke:#2dd4bf,stroke-width:2px
    style A fill:#cffafe,stroke:#22d3ee,stroke-width:2px
    style B fill:#cffafe,stroke:#22d3ee,stroke-width:2px
    style C fill:#cffafe,stroke:#22d3ee,stroke-width:2px

Using Variables in Emails

Subject: New WhatsApp Lead - {{name}}

Body:
A new lead just came through your WhatsApp assistant:

Name: {{name}}
Email: {{email}}
Phone: {{phone}}
Interest: {{selected_product}}

Please follow up within 24 hours.

Best Practices

  • ✅ Use variables in the subject and body — include {{name}}, {{email}}, etc. so the email contains all captured details.
  • ✅ Add a confirmation Message after Send Email — let the customer know their request was received.
  • ✅ Place after Question nodes — capture all needed data before sending the email.
  • ✅ Use Support Email for flexibility — one place to update if your team address changes.
  • ✅ Keep the email body informative — include all context so the agent can follow up without needing to ask again.

Common Mistakes

Mistake What Happens Fix
No subject line Email may be filtered as spam or be confusing Add a clear, descriptive subject
Empty body Recipient gets a blank email Include captured variables and context
Custom email typo Email goes to the wrong address or bounces Double-check the address
Using before capturing variables Email contains raw {{variable}} text Place Question nodes before Send Email
No follow-up message to customer Customer doesn't know the email was sent Add a "Thanks, we'll be in touch!" Message