Skip to content
Novu logoNovu

Multi-channel notification
delivery from one workflow

Reach users in-app, by email, SMS, push, and chat from a single trigger.
We handle providers, timing, and each user’s preferences.

Your app calls trigger('task-reminder'), and one Novu workflow delivers it to email, SMS, push, and chat providers.
  • El Proffen
  • TrustFlight
  • MedVol
  • Check Point
  • MongoDB
  • Cloud Software Group
  • Gangverk
  • Ebury

Stop building a new integration for every channel

Each new channel brings its own SDK, template
format, and one more place to debug. With Novu,
you set it up once.

  • Integrate once

    Your backend sends one event. Novu delivers it to every channel through your providers.

  • Change messages without a deploy

    Product teams edit copy, channels, and timing in the dashboard. Test in dev, then publish.

  • Reach users where they act

    Show it in-app first, follow up by email or push if it’s missed, and respect user preferences.

Use the providers
you already have,
on every channel

Connect the accounts you already pay for, run several per channel, and switch providers without touching code.

Browse notification integrations
  • In-app. Novu Inbox, ready to drop
    in or fully restyled to your UI

  • Email. SendGrid, Amazon SES,
    Resend, Postmark

  • SMS. Twilio, Infobip, Sinch, Plivo

  • Push. Firebase Cloud Messaging,
    APNS, Expo, OneSignal

  • Chat. Slack, Microsoft Teams, WhatsApp Business, Telegram, Discord

Nudge users who
missed the message

Send a task reminder in the app. Wait six hours.
Send an email only if the reminder is still unread. One workflow, triggered by one call from your backend.

A task-reminder workflow: send the reminder in-app, wait six hours, then send an email only if the in-app reminder is unread. It is triggered from the backend with novu.trigger.

Control delivery
from one place

Rules, timing, and content live in one workflow, so changing how a message reaches users doesn't mean touching code in five places.

  • Set when steps run

    Run or skip a step based on who the user is, what happened, or whether they acted earlier. Add delays for follow-ups.

  • Give users control

    Users pick their channels, globally or per notification. Critical messages, like password resets, always get through.

  • Personalize messages

    Write content for each channel with live previews and real user data. Send it in their language with built-in translations.

  • Cut the noise

    Group a burst of events into one summary and limit how often the same notification reaches each user.

Keep your providers.
Centralize routing

Connect several provider accounts and decide which one handles each message. Your app keeps sending the same event while Novu picks the right provider.

How routing works
  • A provider per customer. Send a customer's email or SMS through their own provider account, so messages come from their domain and their sender.

  • Rules instead of code. Pick an email or SMS provider by customer, language, or workflow. Messages that match no rule use your default provider.

  • Native channel formats. Write content for each channel and use native formats where supported, such as Slack Block Kit or WhatsApp templates.

Your agent stays yours. Novu carries the messages and keeps track of each conversation across channels, while your model and tools stay on your side.

Let users reply.
Let agents answer

A failed payment usually sparks a question. With Novu Connect, users reply to the email or chat, and your agent answers in context.

A conversation thread: the notification “Your invoice payment failed,” the user reply “Which invoice was this?”, and the agent finding invoice INV-4471 for $120 in the original notification.

Bring your agent to Slack, Teams, WhatsApp,
Telegram, and email, or into your app.

Know what happened
to every notification

See every workflow run step by step: what
was sent, skipped, or failed, and why. Agent conversations are logged too.

Activity Feed for the email step: 1,100 sent, 2,840 skipped because the reminder was read in-app, and 60 failed, with recent events including a SendGrid “550 Mailbox does not exist” failure.

Frequently asked questions

Multi-channel notification delivery means reaching users through more than one channel, such as in-app, email, SMS, push, and chat, from a single integration. A workflow decides which channels to use for each event, in what order, and under which conditions.

Yes. Connect the provider accounts you already use, such as SendGrid, Twilio, or Firebase Cloud Messaging, and use them in your workflows. You can connect more than one provider per channel, and switching providers is a configuration change, not a code change. For email and SMS, you can also choose a provider per customer or language.

Yes. Content, channels, and timing are edited in the Novu dashboard. Changes are tested in a development environment and then published to production, so developers don't need to ship code for a copy change.

Yes. Users can turn channels on or off for all notifications or for specific workflows, from the in-app Inbox or from your own settings page. Messages marked as critical, such as password resets, ignore those settings.

Novu records the failure in the Activity Feed with the provider's response and can report it to your system as it happens. Most sends are attempted once, because rejections like an invalid phone number would fail again, and Novu doesn't switch providers automatically. See the delivery retry policy for the full behavior.

Yes, with Novu Connect. Assign an AI agent to a workflow, and replies to its supported email and chat notifications continue as a conversation with that agent, with the original notification as context. SMS is outbound only.

Yes. Novu is open source. You can use Novu Cloud or host Novu on your own infrastructure. Some features are available only on Novu Cloud.

Build your first multi‑channel workflow

Connect a provider, add your steps, and send a test notification. Add channels as your users need them.