---
title: "Novu Connect - Agent Communication Infrastructure (ACI)"
description: "Connect AI agents to Slack, Teams, WhatsApp, Telegram, and email. Route inbound messages, preserve conversation context, and deliver replies through Novu ACI."
sidebarTitle: Overview
---
Novu Connect is based on the [Agent Communication Infrastructure (ACI)](/agents/get-started/what-is-aci). It ingests channel webhooks, normalizes events, maintains conversation state, and delivers replies so you can run one agent across Slack, Microsoft Teams, WhatsApp, Telegram, email, and in-app [Web Chat](/agents/channels/web-chat) without rebuilding each integration.
ACI separates two layers:
* **Communication infrastructure**: Webhook ingestion, message normalization, conversation state, identity resolution, and delivery. Owned by ACI.
* **Agent intelligence**: Your LLM, prompts, tools, managed agent config, business logic, or custom runtime. Owned by you.
## Common patterns
### Inbound conversations
Users message the agent on a connected channel (DM, @mention, email, or in-app Web Chat). Novu loads the conversation history and forwards it to your agent brain with the current turn. Replies go back to the same thread.
### Tool approval
Before a sensitive tool runs, the agent can pause and post Approve / Deny in the channel. The turn resumes after the user decides. See [Tool approval](/agents/custom-code-agent/building-blocks/tool-approval).
## Connect your agent
Choose how the agent brain runs:
AI SDK, LangChain, Mastra, or custom handlers on your bridge.
Anthropic Claude. No bridge server.
Claude Platform on AWS. No bridge server.
### Frameworks
`@novu/framework/ai-sdk` + Vercel AI SDK.
`@novu/framework/langchain`.
`@novu/framework` calling Mastra `generate()`.
### Channels
Typing, plan cards, Block Kit, tool approval.
Adaptive Cards, typing, tool approval.
Quick-reply buttons, session context.
Inline keyboards, typing, edit-in-place.
Threaded HTML, action-link approvals.
In-app headless hook, typing, tool approval.
Platform differences are listed in [Channels overview](/agents/channels/overview).
## Message flow
1. A user sends a message on a connected channel.
2. Novu ingests the webhook, normalizes the event, and resolves identity.
3. Novu forwards the event and conversation history to your agent brain.
4. Your agent returns a reply (and may wait on tool approval).
5. Novu delivers the reply to the correct thread.
6. The conversation is stored and visible in the [Novu dashboard](https://dashboard.novu.co/agents).
## Learn more
Architecture and scope of the communication layer.
Inbound path from channel to agent and back.
Agent entities and provider connections.
Feature support by platform.
Pause the turn until the user approves a tool call.
Inspect live conversations in the dashboard.
Headless `useWebChat` in your product UI.