Novu Connect

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 🚀

Go team Novu!!!

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🙌

Smart. Can multiple agents share one comms layer or is it one per agent?

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.

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?

Excited to try it. What's the free tier look like for someone just experimenting?

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/connectSo, which channel would you put your agent on first?

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!

This solves a real pain for us honestly, can I see delivery status, like did the human actually get it?

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!

Just tried the Claude prompt. Mind = blown. What’s the latency like on WhatsApp replies?

Congrats! 🙌 Love the idea of ACI, it solves a real pain point of building and doing all hassle with the integrations layer, which is a huge distraction where at the end you want just to ship the agent quickly. I will be definitely using it for my side projects to create, automate, research, part of the work I do manualy. And I am waiting for the scheduling support!😊I am curious what others have alredy build on top of this?

Standard text is fine but interactive elements like slack buttons or whataap quicl replyes really drive engagmetns for bots, can our agents pass intereactive ui payloads through Novo connect ?

This solves a real pain for us honestly - can I see delivery status, like did the human actually get it?