> ## 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.

# Email integration

> Set up a custom email domain in Nedzo to send branded emails from workflows. Configure DNS records, verify your domain, and track replies.

Set up a custom email domain to send branded emails from your workflows. Replies are tracked in Unibox.

<Note>
  Looking for a support inbox that turns incoming email into Unibox conversations without per-agent setup? See the [Email channel](/integrations/email-channel) instead — it's a separate, simpler setup available on Launch, Scale, and Enterprise plans.
</Note>

## 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

1. Go to **Settings > Integrations** in your dashboard
2. Find **Email** and click **Configure**
3. Enter your sending domain (e.g., `mail.yourdomain.com` or `notifications.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        |

Add these records in your domain registrar's DNS settings (GoDaddy, Cloudflare, Namecheap, etc.).

### 3. Verify

1. After adding the DNS records, go back to your dashboard
2. Click **Check** to verify the records
3. DNS propagation can take up to 48 hours, but usually completes within a few minutes

Once verified, you're ready to send emails.

## 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

See [Chat agents → Email channel](/agents/voice-agents#email-channel) for full per-agent setup.

## Using in workflows

Add a **Send Email** node to any workflow:

1. **Recipient** — Send to the trigger contact's email or enter a custom address
2. **From name** — The sender name that appears in the inbox
3. **Subject** — Email subject line (supports variables)
4. **Body** — Email content (supports variables)

**Example:**

```
Subject: Thanks for chatting with us, {{first_name}}
Body: Hi {{first_name}}, thanks for your time today. We'll follow up with more details shortly.
```

## 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 |

Any data passed as trigger variables is also available using `{{variable_name}}`.

## Default domain

If you don't set up a custom domain, emails are sent from `nedzo-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

1. Go to **Settings > Integrations**
2. Click **Remove** on the Email integration to delete your domain configuration