Node: Send Customer Email

The Send Customer Email node (send_customer_email) sends an email to the contact tied to the workflow run — not to a teammate. Use it for confirmations, welcomes, receipts, or any notice you want delivered straight to the customer's inbox, alongside whatever you already do on WhatsApp or other channels.

When to use it

• Confirm a purchase or signup with a formal email.
• Send a receipt or a link you'd rather not paste into a chat.
• Reach a customer who doesn't have an open conversation right now (e.g. a workflow triggered from a Boards automation or the CRM).

Requirements

• The contact needs an email on file; if not, the step is skipped without breaking the workflow.
• The workspace needs at least one active Email channel — the node reuses the same sender (AWS SES) Omnifox already uses.

Configuration

• Subject (required): supports variables, e.g. Welcome {{contact.first_name}}.
• Body (required): plain text or HTML; supports variables like {{contact.first_name}}.
• Render as HTML: turn on if the body contains HTML tags.

Example

On a workflow triggered by "Deal won" in the CRM, add this node with:

• Subject: Thanks for your purchase, {{contact.first_name}}!
• Body: Hi {{contact.first_name}}, your order is confirmed. Just reply to this email with any questions.

The customer gets the email even if there's no open conversation in the inbox.

Tips

• To reply inside the active chat (WhatsApp, Webchat, etc.) use the Send message node instead.
• The system automatically appends an unsubscribe link to keep sending practices compliant.

Troubleshooting

• Email never arrives: check that the contact has a valid email and the workspace has an active Email channel.
• "Blocked": cold sends (no prior conversation) are rate-limited to prevent abuse; if blocked, wait or start the relationship on a conversational channel first.