docs/agents/channels/email.mdx
Use email as a messaging channel for your agent. Novu preserves standard email threading, delivers HTML replies with action links, and can request tool approval in-thread. Email is request/response only: no typing indicator or plan card.
| Capability | Support |
|---|---|
| Full context history | Yes |
| Threaded replies (email threading) | Yes |
| Live typing indicator | No |
| React with eyes on the original email | Yes |
| Plan card | No |
| Rich text | HTML |
| Tap-to-respond | Yes (action links in the body) |
| Emoji reactions | Gmail only (limited set) |
| Message edits in place | No |
| Action / MCP tool approval | Yes (action links) |
| MCP connect card | Yes (action links) |
| Resolve conversation | Yes |
| File sharing | Not yet |
| Streaming word-by-word | Not yet |
Full matrix: Channels overview.
A user emails the agent address. Novu reacts with eyes on the original message while the agent runs, then sends a threaded HTML reply with optional action links.
Gated tools send Approve / Deny action links in a follow-up email. The handler resumes after the user clicks a link.
| Framework / Platform | Guide |
|---|---|
| Custom code agent | Follow a connect guide, then add email as another provider |
| Managed agent | Claude or AWS Claude, then link email in the dashboard |
Email provider credentials are configured in the Novu dashboard when you add the provider.
@novu/react does not ship an email connect button. Email connections are address-based: configure the email provider on the agent in the dashboard (or via the Agents API). Users reach the agent by emailing that address; threading is handled by ACI.
For Slack, Teams, and Telegram embeddable buttons, see Connect components.