Novu Connect - Ship agents where your users already work
by•
Novu Connect lets any AI agent have two-way conversations across Slack, Teams, WhatsApp, Telegram, and email without building each channel integration yourself. Bring your own agent logic, model, or code. Novu handles the communication layer: delivery, identity resolution, threading, routing, and channel-specific formatting, so your agent can reach users where they already work.
Replies
ReplyMind
Incredible launch, team Novu! 🚀 'Bring your own brain, Novu handles the voice' is the perfect line. It’s awesome to see a trusted open-source notification stack evolve into a robust two-way conversational layer for AI. Bookmarking this for my next build!
Novu
@moon10 It was the most intuitive thing for us, we've been sending notification on all those channels for years now at scale. Now, it's time to convert the same transactional notification to a conversation!
Novu
Emil here, I work on the marketing side at Novu.
The founders have already covered the what and the why, so I'll just add the one thing that made this click for me.
For months, we kept saying "connect agents to channels." But the longer I sat with it, the more I realized connecting a channel is the easy part.
The hard, unglamorous part is keeping one conversation coherent when a user starts on Slack, replies from WhatsApp, and finishes over email. For the agent, it should be a single thread. Same memory, same context. That continuity is the whole point, and it is genuinely hard to build.
The moment it stopped being a slide and became real for me was watching an agent go live on an actual channel in about two minutes, no API key, no plumbing.
If you're building agents, I'd love for you to try it and tell me where it surprises you or where it breaks.
Start free: novu.co/connect
So, which channel would you put your agent on first?
Novu
@emilpearce Let's go for the win!!
Excited to try it. What's the free tier look like for someone just experimenting?
Novu
@_eyalbaruch you can create a free account and have 2 agents running without credit card 🎉
Smart. Can multiple agents share one comms layer or is it one per agent?
Novu
@dalgeitsch Yes, actually, internally we have around 50 different agents on Slack the team has created for various usecases. Similiarly, you might have hundreds of agents, each with it's own email inbox responding to different "users" of your system. But same brain does the logic part.
This is huge for human-in-the-loop workflows. being able to ping a manager on slack for an approval button while the agent talks to a client on whatsapp is exactly what we need. awesome launch🙌
Novu
@vikramp7470 Thank you Vikram! Looking forward to see what you will build with it ⚡
Lamatic.ai
love what novu has been building for a while now — super clean product and strong vision.
aci is especially exciting, had a chance to connect with @tomer_barnea1 and it really feels like the future of notifications. big congrats to the team on the launch 🚀
Novu
@amanintech Hi! Thanks for that! I agree, the future is going to be communication, and notifications are going to plat a part of it, very exciting.
Novu
@tomer_barnea1 @amanintech Appreciate it Aman! Would be exciting to partner on the future of agents together
Dynamo
Congrats on the launch! 🚀
The "-second rule for terminal-to-channel connectivity is a huge win for developer velocity. Running npx novu connect to bridge agents with Slack or WhatsApp that quickly sounds like a dream for anyone building in the AI agent space right now.
Can't wait to see how this simplifies multi-channel notifications! Just curious, how do you handle the auth/handshake for the more walled garden channels like WhatsApp within that minute?
Good luck today!
Novu
@yam_regev Each channel is a unique challenge for removing onboarding friction, and the team get's quite creative about it. Soon, Whatsapp will be even simpler!
Novu
@yam_regev my man! thank you for you all support!!
Riverside
This solves a real pain for us honestly, can I see delivery status, like did the human actually get it?
Novu
@roypovar Yes! you can see it all under the Conversations page of your connected agent 🎉
Novu
@roypovar thanks for your support!
Strong launch. The hardest part of agent UX is meeting users inside existing workflows; Slack/Teams/email threading + identity resolution is exactly the unglamorous glue. Curious how you handle conversation state when the same user jumps channels?
Novu
@sarveshsea We provide the context of each conversation thread, so every time a new conversation starts on different channels/dms a new conversation is created for that thread.
Congrats on the launch. The piece I'd want to understand before adopting a notifications layer is failure semantics: when a downstream provider (email/SMS/push) is degraded, does Novu retry with backoff and fall back to the next channel automatically, or is that orchestration something I define per workflow? Dedupe across channels is the other one — stopping a user getting the same alert by email AND push.
Novu
@mikebrandswarm Yes, Novu performs a back-off retry on delivery. You can also swap provider across the channel in case of a single provider is down. Ofcourse, with providers like Slack it's not the case, since the user is uniquely authenticated to their Slack workspace and there is "no" alternative available.