Skip to content
Novu logoNovu
Agent-Assigned Workflows

Turn every notification into a conversation

Your product sends a notification. The user has a question, but no-reply makes it a dead end. Assign an agent to the workflow, and every notification becomes the start of a real conversation.

Sign up for free
npx novu connect
  • El Proffen
  • TrustFlight
  • MedVol
  • Check Point
  • MongoDB
  • Cloud Software Group
  • Gangverk
  • Ebury

Move from notification to conversation

Define the message and delivery logic once. Trigger the notification to the subscriber, and allow them to directly respond and converse with the agent.

A trigger call from your app runs through notification settings — delivery timing, message template, and the assigned agent — then reaches the user on Telegram, iMessage, Microsoft Teams, WhatsApp, email, or Slack.
  • Trigger from your app

    Call the workflow by name with a recipient and payload.

  • Run the workflow

    Novu applies the message, timing, and delivery logic defined once.

  • Deliver across channels

    Send notifications through the configured channels from the same trigger.

One toggle on the workflow. The reply does the rest.

No inbound webhook, reply parser, or context store needed. Novu matches the reply, loads the original payload, and passes it to your agent.

A workflow notification step with “Send & reply via agent” switched on and Ada · Support chosen as the agent.
Step 01

Assign an agent to the workflow

In the workflow editor, flip Send & reply via agent and pick the agent. Its messages now go out on the agent’s own connected channels, and replies route straight back to it.

Set up workflow
An agent thread where the user asks to change the delivery address and the agent answers with the order already in context, above the channel icons the reply can arrive on.
Step 02

The user just replies

On the channel they are already on: Slack, WhatsApp, iMessage, Telegram, Microsoft Teams, or email. Novu matches the reply back by reply-to token, thread, or quoted message. No app, no portal, no “click here to respond”.

Customize reply
An agent.ts file reading ctx.notification, with the workflow payload typed and available.
Step 03

Your agent already has the context

The conversation is hydrated once with the original notification. Custom Code agents read a typed ctx.notification. Managed Agents get the same context injected for them. No re-fetch, no “please provide your order number”.

Set agent context
The same thread continuing, with the agent confirming a new delivery address and offering a heads-up when it ships.
Step 04

And the conversation keeps going

The reply is not a one-off. The user keeps talking, the agent keeps answering on the same thread, with the whole history in hand. It stays a live conversation for as long as they need, not a ticket that closes.

See it in action

Watch an email notification turn into a conversation with an agent that already knows the context.

We never run your brain. Novu provides Agent Communication Infrastructure (ACI) for real, two-way conversations between your agents and users across the channels they already use.

  • MCP

    Agents use tools

    Give agents access to APIs, tools, and data so they can take action.

  • A2A

    Agents work together

    Coordinate and collaborate with other agents across systems and workflows.

  • ACI

    Agents talk to people

    Hold real, two-way conversations across the channels your users already use.

The reply lands wherever the user already is

Stop sending mail no one can answer

Assign an agent to a workflow and turn every notification into a conversation your users can actually reply to.

npx novu connect