Set up a custom email domain to send branded emails from your workflows. Replies are tracked in Unibox.Documentation Index
Fetch the complete documentation index at: https://docs.nedzo.ai/llms.txt
Use this file to discover all available pages before exploring further.
What it does
- Custom sender domain — Send emails from your own domain (e.g.,
notifications@yourdomain.com) - Per-agent inbound addresses — Give each chat agent its own address on the verified domain (e.g.
support@mail.yourdomain.com,billing@mail.yourdomain.com) so inbound emails route to the right agent - Workflow emails — Send automated emails as part of any workflow
- Reply tracking — Inbound replies appear in Unibox alongside other conversations
- Variable substitution — Personalize emails with contact data
How to set up
1. Add your domain
- Go to Settings > Integrations in your dashboard
- Find Email and click Configure
- Enter your sending domain (e.g.,
mail.yourdomain.comornotifications.yourdomain.com)
2. Add DNS records
After adding your domain, Nedzo shows you DNS records to add at your domain provider:| Record Type | Purpose |
|---|---|
| TXT | Domain ownership verification |
| CNAME | Email authentication (DKIM) |
| MX | Inbound reply handling |
3. Verify
- After adding the DNS records, go back to your dashboard
- Click Check to verify the records
- DNS propagation can take up to 48 hours, but usually completes within a few minutes
Per-agent inbound addresses
Once your domain is verified, each chat agent can claim its own local part on that domain. Open the agent → Settings tab → enable the Email channel → enter a local part in Inbound Email Address. The full inbound address is the local part you set +@ + your verified sending domain. For a domain mail.yourdomain.com, an agent with local part support receives emails sent to support@mail.yourdomain.com.
Rules:
- Lowercase letters, numbers, dots, hyphens, and underscores
- Max 64 characters
- No leading, trailing, or consecutive dots
- Unique per workspace — two agents in the same workspace can’t share the same local part
Using in workflows
Add a Send Email node to any workflow:- Recipient — Send to the trigger contact’s email or enter a custom address
- From name — The sender name that appears in the inbox
- Subject — Email subject line (supports variables)
- Body — Email content (supports variables)
Available variables
| Variable | Description |
|---|---|
{{first_name}} | Contact’s first name |
{{last_name}} | Contact’s last name |
{{email}} | Contact’s email |
{{phone}} | Contact’s phone number |
{{variable_name}}.
Default domain
If you don’t set up a custom domain, emails are sent fromnedzo-mail.com. Setting up your own domain improves deliverability and lets recipients recognize your brand.
Daily send limits
Each workspace has a daily email send cap to protect deliverability and prevent runaway workflows. The cap covers all outbound paths combined — workflow Send Email actions, agent auto-replies, and manual sends from Unibox. When you approach the cap, a banner appears in the dashboard with the current usage and the daily limit. Once the cap is hit, additional sends are blocked for the rest of the UTC day and clearly surfaced as failed in workflow execution logs and the conversation timeline. The counter resets at midnight UTC. If you need a higher limit, contact support.Disconnecting
- Go to Settings > Integrations
- Click Remove on the Email integration to delete your domain configuration
