Skip to main content
Agents are currently in private beta. Please contact us at [email protected] to get access.
Novu for Agents sits between chat providers and your code. Users can message your agent, and your agent can message them back on the same thread. When a user sends a message or interacts with your agent from a connected platform, Novu receives it, resolves identity and conversation state, and forwards the full context to agent brain. Your agent brain processes the message and replies; Novu delivers the response back to the platform.

​
Types of agents

Novu supports two types of agents:
  • Custom code agent
  • Managed agent
A custom code agent is one where you build the agent brain with your own code. Use the Agent SDK, LangChain, and similar tools to implement it. Your agent brain receives the context object and processes it however you decide. Call an LLM, run business logic, route to a human, or combine all three.
Custom code agent

Custom code agent message flow from a connected platform through Novu to your agent brain and back.

Read more on how to connect a custom code agent.

​
Conversations

A conversation is the stateful thread where communication happens. When a user sends a message from a connected provider, Novu creates a new conversation or loads the existing one for that thread. The conversation includes message history, metadata, participants, status, and platform context needed to process the next interaction. A conversation can include multiple participants. The agent is one participant in the conversation, but it is not the conversation itself. This distinction matters when you inspect conversations in the dashboard or build agent behavior around conversation state. A Slack thread, email thread, in-app Web Chat thread, or other provider-specific thread maps to a conversation in Novu automatically.

​
Participants and subscriber identity

Participants are the people, agents, or systems involved in a conversation. When a user messages your agent from a provider, Novu tries to resolve that platform user to a known subscriber.
  • If a match exists, the handler receives subscriber information such as subscriber ID, name, or email. This subscriber is used to identify the user across conversations.
  • If no match exists, the user is tracked as a platform user and your agent brain should account for cases where subscriber data is unavailable.
Once identity is resolved later, they are upgraded to a full subscriber and future messages include their subscriber data. Subscriber identity helps your agent personalize responses, look up account details, or decide whether a conversation should be escalated. Identity resolution is provider-aware: a Slack user and an email sender may each have different identifiers at the provider level that Novu resolves to a single subscriber.

​
Agent brain

Novu calls your agent brain with the complete context: the message, conversation history, subscriber, and platform details. Your agent brain processes it with your LLM, business logic, or any system you choose and calls ctx.reply() in case of custom code agent or sends a reply message to the platform in case of managed agent.

​
Next steps

Connect AI SDK

Connect a Vercel AI SDK agent to Slack.

Connect LangChain

Connect a LangChain agent to Slack.

Connect Mastra

Connect a Mastra agent to Slack.

Slack

Slack capabilities and setup links.

Web Chat

Headless chat in your product UI.

Managed agent

Connect a managed Claude agent.

Agents API reference

Create, configure, and manage agents programmatically.