Skip to content

Changelog

Product updates, improvements, and fixes

Follow us on X

All changelog posts

  • Agent Inbox: give your AI agent a way to reach you

    Agent Inbox is now available. Give your AI agent its own email address, Telegram bot and Slack app, set it up in one command, and connect it over CLI or MCP.

    Authors:
    Dima GrossmanPaweł TymczukNikita GrossmanVictor Yakubu
    Dima G., Paweł T., Nikita G., Victor Y.
    Cover image for Agent Inbox: give your AI agent a way to reach you

    Give your agent its own name, email address and contact card, plus its own Telegram bot and Slack app, so it can reach people and people can reach it.

    Agent Inbox is now available. It works with the agent you already run, whether that's Claude Code, Codex, Cursor, ChatGPT, OpenClaw, Hermes, or anything that can run a CLI or connect to MCP.

    Read more: Agent Inbox: give your AI agent a way to reach you
  • Web Chat for in-app agent conversations

    Embed a Novu Connect agent in your React application while Novu handles live delivery, history, approvals, and conversation state.

    Authors:
    Adam ChmaraVictor Yakubu
    Adam C., Victor Y.
    Cover image for Web Chat for in-app agent conversations

    Web Chat is now available in open beta on Novu Connect. It gives your agent an in-app channel, so users can start and continue a conversation inside your product instead of moving to Slack, Microsoft Teams, WhatsApp, Telegram, or email.

    The React client is headless. You build the message list, composer, and layout that fit your product. Novu manages the live connection, conversation history, agent-run state, tool approvals, and activity visible in the Dashboard.

    Read more: Web Chat for in-app agent conversations
  • Manage agents and conversations through the Novu MCP server

    Create and update agents, connect channels, and inspect conversation activity from any MCP-compatible AI tool.

    Authors:
    Nikita GrossmanVictor Yakubu
    Nikita G., Victor Y.
    Novu MCP Server

    Agent and conversation tools are now available on the Novu MCP server. You can manage the conversational side of Novu from the same AI tool you use to create workflows, inspect subscribers, and troubleshoot notification delivery.

    Ask your assistant to create or update an agent, connect a channel, list recent conversations, or inspect the activity timeline for a specific thread. Together with the existing workflow tools, you can also assign agents to existing workflows without switching between your editor and the Novu Dashboard.

    Read more: Manage agents and conversations through the Novu MCP server
  • Agent-Assigned Workflows

    Turn a workflow notification into the first turn of an agent conversation, with the original message and trigger payload already in context.

    Authors:
    Nikita GrossmanVictor Yakubu
    Nikita G., Victor Y.
    Cover image for Agent-Assigned Workflows

    You can now assign an agent to a workflow from the Novu Dashboard. Workflow messages are sent through the agent's connected channels, and when a subscriber replies, Novu routes the reply to that agent with the originating workflow, message, and trigger payload already in context.

    This closes the gap between notifications and conversations. A workflow can send “Your order has shipped,” the subscriber can reply “Can I change the delivery address?”, and the agent receives the order data from the original trigger without a separate correlation layer in your application.

    Read more: Agent-Assigned Workflows
  • Provider content overrides in the Dashboard

    Save provider-native JSON on Chat and Tool workflow steps, then version and promote it with the rest of the workflow.

    Authors:
    George DjabarovVictor Yakubu
    George D., Victor Y.
    Provider content overrides in the dashboard

    Provider content overrides can now be configured directly in the Novu Dashboard. Use them when a workflow needs fields from a provider's native API that the shared step editor does not expose, such as Slack Block Kit, WhatsApp templates, or PagerDuty incident fields.

    Previously, these payloads had to be added to every trigger() call in application code. You can now save the JSON once on the workflow step. It applies to every trigger and moves from development to production with the workflow.

    Read more: Provider content overrides in the Dashboard
  • Rich chat editor for workflow Chat steps

    Build structured chat notifications with text, images, lists, link buttons, variables, and provider-aware previews from the workflow editor.

    Authors:
    Paweł TymczukVictor Yakubu
    Paweł T., Victor Y.
    Rich chat editor for workflow Chat steps

    Workflow Chat steps now include a visual block editor. Instead of limiting every workflow-sent chat notification to one text body, you can compose structured messages for approvals, reports, summaries, prompts, and calls to action from the Dashboard.

    Novu converts the shared message into a provider-specific format at delivery time. You author the content once, then inspect how it may appear on each chat provider connected to the environment.

    Read more: Rich chat editor for workflow Chat steps

Free to start, ready to scale

10K events/month free forever. From weekend projects to enterprise scale, we've got you covered.