Novu

At a Glance:

Novu is an open-source communication infrastructure platform that provides a single API and unified conversation model to connect products and agents to channels like Inbox, Email, SMS, Push, Slack, and Telegram, with a workflow engine, digest engine, and embeddable notification center component.

Overview:

Novu is an open-source communication infrastructure layer designed for developers building products and agents that need to send notifications or have conversations across multiple channels. It provides a single API to manage delivery through Inbox/In-App, Email, SMS, Push, and Chat, eliminating the need to integrate each provider individually. The platform includes a notification workflow engine with branching and conditions, a digest engine that batches multiple notifications, and an embeddable real-time notification center component. For teams already building conversational agents, Novu offers Agent Communication Infrastructure that normalizes inbound messages from Slack, Microsoft Teams, Telegram, WhatsApp, and Email into a consistent model, routes them to your agent, and sends responses back out. Novu handles the provider integrations and channel-specific formatting, while you retain full control over your agent logic.

Key Decision Points:

• Single API across channels: Manage Inbox, Email, SMS, Push, and Chat notifications through one API instead of integrating each provider separately.

• Agent communication layer: If you have already built an agent, Novu provides bidirectional messaging through a unified conversation model that normalizes messages from Slack, Teams, Telegram, WhatsApp, and Email.

• Embeddable Inbox component: A real-time notification center is available as a React component or via API and SDK, with other frameworks listed as coming soon.

• Workflow engine with digests: Notifications can be routed through conditional workflows and batched using the digest engine before delivery.

• Open-core licensing: Core functionality is MIT-licensed; enterprise features in the enterprise folder and apps/web/src/ee require a commercial license.

• Provider management: Novu supports multiple providers per channel (19 Email, 37 SMS, 8 Push, 12 Chat) manageable through an API and UI, but you are responsible for your own provider accounts.

Core Features:

• Unified notification API: Send notifications across Email, SMS, Push, Chat, and In-App channels through a single API endpoint.

• Agent Communication Infrastructure (ACI): Connects agents to Slack, Microsoft Teams, Telegram, WhatsApp, and Email, handling inbound message normalization and outbound delivery through a consistent conversation model.

• Embeddable Inbox component: A real-time, customizable notification center that can be embedded into web applications using React, or built via the API and SDK.

• Notification workflow engine: Define multi-step notification flows with per-channel conditions and branching logic.

• Digest engine: Batch multiple trigger events into a single consolidated notification message.

• Embeddable user preferences: A component that allows end users to manage their own notification channel preferences.

Use Cases:

• Developers adding multi-channel notifications to a SaaS product who want to avoid integrating each provider individually.

• Teams that have already built a conversational agent and need to connect it to Slack, Telegram, Microsoft Teams, or Email for bidirectional communication.

• Applications needing an embeddable, real-time notification center that users can customize through preference controls.

Open-Source Alternative Value:

Novu is open-source under an MIT license for its core components, providing a developer-controlled alternative to proprietary communication platforms like Courier or Knock. Its value lies in the ability to self-host the core notification infrastructure, use a single API across multiple channels and providers, and directly work with the source code. Developers can embed the Inbox component and use the workflow engine without relying on a closed SaaS for notification routing logic, while maintaining their own provider relationships. The agent communication layer extends this to bidirectional messaging scenarios without requiring per-channel webhook implementations.