What it does
Novu provides notification workflows, channel integrations, subscriber preferences, and in-app notification components.
Why it’s interesting
Notification logic tends to spread across providers and application services. A workflow layer centralizes routing and preferences, while delivery still depends on configured provider credentials.
Real-world use case
Send an onboarding notification and fall back to email if the in-app message stays unread.
What I can learn
- 01
Provider adapter contracts
Compare how one notification workflow can call different email, SMS, push, and chat providers through interchangeable adapters.
- 02
Delayed steps and notification digests
Understand how delayed steps and time-window aggregation turn bursts of events into scheduled or digest notifications.
- 03
Realtime unread state and client synchronization
Explore how unread counts and notification updates stay consistent between the server and multiple open client views.
One thing to explore
Workflow and channel providers
Follow the apps implementation and connect it to the concepts above.
Explore the source (opens in a new tab)10-Minute Challenge
Explore a notification workflow
Before you start: Node.js and a Novu test workspace with a configured workflow. Do not put API keys in source control.
- Review the current quickstart and create a workflow in the dashboard or local setup.
- Inspect a subscriber and the channel steps in a sample workflow.
- If using the SDK, trigger only against a test subscriber and configured sandbox provider.
npm install @novu/node