A notiflow is a notification workflow that defines how and when notifications are delivered to your users. Each notiflow consists of a series of connected steps that control the flow of notification delivery.

Notiflow Structure

Every notiflow contains:

Trigger Step - The entry point that starts the workflow when triggered via API
Channel Steps - Send notifications through configured channels (email, SMS, push, etc.)
Control Steps - Modify flow behavior (wait, batch, throttle)
End Step - Marks the completion of a workflow branch

Steps are connected as a directed graph, allowing you to build linear flows or more complex branching logic.

Step Types

Step	Purpose
Trigger	Entry point for the workflow
Channel	Send notification via a channel
Wait	Delay execution for a duration
Batch	Group notifications together
Throttle	Limit notification frequency
End	Terminate a workflow branch

Building a Notiflow

Create a notiflow - Give it a name and description
Add steps - Drag steps onto the canvas and connect them
Configure channels - Select which channel to use for each channel step
Design templates - Create the notification content with dynamic variables
Test - Preview and test your notiflow before publishing
Publish - Make the notiflow live and ready to trigger

Example Flow

A simple order confirmation notiflow might look like:

Trigger → Channel (Email) → End

A more complex flow with a follow-up reminder:

Trigger → Channel (Email) → Wait (24 hours) → Channel (Push) → End

Versioning

Notiflows use a versioning system to safely make changes without affecting live notifications. See Versioning for details.

Templates

Each channel step has an associated template that defines the notification content. Templates use Liquid syntax for dynamic content. See Templates for details.

Overview