Novu Connect: One Agent, Every Channel, One Conversation

Your AI agent can think. Now it can talk.

Novu Connect is live: the communication layer for AI agents. One agent, every channel your users already use, held together in one synced conversation, through a single API. You bring the agent. Connect handles identity, threading, and delivery.

Meet ACI: Agent Communication Infrastructure

Every wave of AI infrastructure solved one connection. MCP connected agents to tools. A2A connected agents to other agents. ACI connects agents to people.

Agent Communication Infrastructure is the layer that lets an agent hold a real, two-way conversation with humans on the channels they already use. Novu Connect is the first ACI layer. Learn about the category.

The ACI architecture: communication providers (Slack, WhatsApp, MS Teams, Telegram, email) connect through Novu for identity resolution, credential management, observability, and a unified conversation, to the agent brain (Agent SDK, LangChain, or Claude Managed Agent) — The ACI stack: communication channels, the Novu bridge, and your agent's brain.

One agent, every channel

Reach your users on the surfaces they never close:

Slack: channels and DMs, answering in-thread with full context.
Microsoft Teams: the same agent inside the enterprise, with identity handled.
WhatsApp: a real back-and-forth, not a no-reply blast.
Telegram: fast, bot-friendly, community-native.
Email: the universal fallback, same thread, same context.

Add a channel later, and your agent code does not change.

Choosing where your agent listens and communicates in the Novu dashboard: Slack, Microsoft Teams, WhatsApp Business, and Novu Email, with Telegram, Google Chat and more coming soon — Choosing where your agent listens and responds, in the Novu dashboard.

One conversation, not five bots

The hard part was never connecting a single channel. It was keeping one conversation coherent across all of them.

Picture it: a user starts in Slack this morning, follows up from WhatsApp at lunch, and closes the loop by email tonight. To your agent, it is one thread. Same memory, same context. They never repeat themselves.

Managing an agent's conversations in Novu: one synced thread per user across channels — One synced conversation per user, across every channel.

That is the part that single-channel connectors cannot do. Identity resolution and threading are handled for you, so the conversation follows your user across channels.

Live in minutes: three ways to start

Pick the path that fits how you work.

1. CLI. Run one command:

npx novu connect

2. Agent-first. Paste a prompt where your agent already lives: "Add an agent to my app https://novu.co/agents.md". Sixty seconds later, your agent is live on a real channel, no account or API key required.

3. Dashboard. Set it up visually in the Novu dashboard.

A Novu agent live in Slack: the connected support agent replies in a thread and offers to continue setup in the dashboard — An agent live in Slack, minutes after setup.

Bring your own brain

The agent logic stays yours. Bring Claude or your own code, and Connect carries it across every channel. We never run your agent's brain. Claude Managed agents are supported out of the box, on a free tier.

Creating an agent in Novu and connecting your own code or model through the unified conversational API — Bring your own code or model through the unified conversational API.

Same infrastructure, now two-way

Connect runs on the same delivery infrastructure behind your Novu notifications. No new stack, no migration. The one shift: it carries two-way agent conversations, not just the outbound messages you already send.

Connect your first agent at novu.co/connect. This is day one, with more agent runtimes and channels on the way.