Send an email as part of your workflow. Emails are sent from your custom domain or the defaultDocumentation Index
Fetch the complete documentation index at: https://docs.nedzo.ai/llms.txt
Use this file to discover all available pages before exploring further.
nedzo-mail.com domain. Replies are tracked in Unibox.
Configuration
| Field | Required | Default | Description |
|---|---|---|---|
| Recipient type | Yes | Contact | Contact sends to the trigger contact’s email. Custom lets you enter a specific address. |
| Custom email | If custom | — | Email address. Only shown when recipient type is “Custom”. |
| From name | No | Workspace default | The sender name that appears in the recipient’s inbox. |
| Subject | Yes | — | Email subject line. Supports {{variables}}. Max 998 characters. |
| Body | Yes (Fixed mode) | — | Email content. Supports {{variables}}. Max 25,600 characters. Only used in Fixed mode. |
| Instruction | No (AI Generated mode) | — | Instructions for the AI when composing the email. Only shown in AI Generated mode. |
Body mode
The Send Email action supports two modes for composing the email body:| Mode | Description |
|---|---|
| Fixed | You write the exact email content. Supports {{variables}} for personalization. |
| AI Generated | The AI composes the email body based on conversation context and your instructions. |
When using AI Generated mode, the Instruction field is optional but recommended. Without it, the AI composes the email based on conversation context alone. With it, you get more control over tone, content, and structure.
Variables
Personalize the subject and body with variables:{{firstName}}, {{lastName}}, {{email}}, {{phone}}, {{businessName}}, plus any trigger data or previous step outputs.
Custom domain
If you’ve set up a custom email domain in Settings > Integrations > Email, emails are sent from that domain. The domain must be DNS-verified before emails can be sent. Without a custom domain, emails are sent fromnedzo-mail.com. Setting up your own domain improves deliverability and brand recognition.
Reply tracking
When a contact replies to a workflow email, the reply appears in Unibox under that contact’s conversation. An inbound webhook route is automatically configured for your domain.Example
Send a summary after a call:- Trigger: Conversation ended → Agent Type: voice
- Condition: Outcome equals “completed”
- Action: Send email
- Recipient: Contact
- From name: Your Company
- Subject: “Summary of our conversation”
- Body: “Hi
{{firstName}}, thanks for taking the time to speak with us. Here’s a quick recap of what we discussed…”
