Skip to main content
Build multi-channel fallback workflows in Novu by chaining channel steps with delay and condition logic. A common pattern sends an in-app notification first, waits 24 hours, then sends email or SMS if the message remains unread.

​
How do I build an in-app to email fallback workflow?

  1. Add an in-app step as the first channel step.
  2. Add a delay step (for example, 24 hours).
  3. Add a step condition that checks whether the in-app notification was read.
  4. Add an email step (or SMS step) that runs only when the condition is met.
See step conditions for filtering steps based on subscriber state.

​
Example fallback flow

1

Send in-app notification

Deliver the alert to the subscriber’s Inbox immediately.
2

Wait 24 hours

Use a delay step to pause before the fallback.
3

Check if unread

Apply a step condition so the email step runs only when the in-app message is still unread.
4

Send email fallback

Deliver the same content through the subscriber’s email integration.

​
How do I route VIP subscribers to SMS?

Use step conditions with subscriber metadata. If subscriber.data.tier === 'vip', route to an SMS step; otherwise use email. Pass tier data when creating or updating the subscriber, or inline when triggering the workflow.

​
Frequently asked questions

Yes. Chain any channel steps with delays and conditions. Ensure the subscriber has the required contact fields and integrations configured for each channel.
Novu applies subscriber preferences automatically. Subscribers who opt out of a channel will not receive messages on that channel even if the workflow includes the step.