Workflow acts as the notification powerhouse where you define the logic and stitch individual pieces together, like user, template, vendor, and preferences, to deliver notifications to the end user.

A workflow comprises a series of steps that, when performed in sequence, form the notification journey. There exists primarily four types of workflow steps, referred to as workflow nodes in SuprSend:

​
Create workflow

In SuprSend, you can group multi-channel and multi-stakeholder notifications in a single workflow, by considering the workflow as a sequence of notifications.

One example of a multi-channel, multi-stakeholder workflow involves sending a series of payment reminders to a company’s users.

  • The system sends the first reminder to the account admins via email.

  • The second reminder reaches both the admins and the finance team of the company—first via Inbox, then via email if the notification isn’t seen on Inbox.

Payment Reminder workflow

Creating a single workflow to track the journey linked to a trigger helps simplify tracking the entire flow—e.g., understanding how many users saw the first notification, how many dropped off after the second, which channel performs best, and more. Fewer workflow

Test your workflows in staging workspace before deploying to production:

Design your workflows in the staging workspace first and trigger a test workflow before making it live for your production users. Once your workflow is well tested and working, clone it to the production workspace.

​
Notification categories

Each workflow connects to a notification category, which helps group related workflows. Users can manage their preferences across these groups. For instance, you can group all shipment-related messages under the category Delivery updates, allowing users to turn off email alerts and receive them only via push notifications.

This preference setting automatically applies to all workflows under the category Delivery updates. Learn more about notification categories here.

​
Version control for workflows

The system first saves all workflow changes in a draft version and only makes them live after you commit the updates. This approach lets you confidently update workflows without affecting any that currently run in production.

​
Trigger workflow

Workflows created on SuprSend dashboard can trigger via an event call or via a direct API call.

​
Track / Debug Workflow run

For each workflow run, you’ll see a detailed log capturing the state and response of each workflow step as they’re sent. You can refer to error guides to understand the errors and see how to resolve them.

​
Analyze notification performance

SuprSend provides comprehensive analytics to track the performance of your notifications. You can track delivery, seen, and clicks across all channels in a single graph, identify the best-performing channel, and see how users interact with the notification. You can also retrieve the notification data in your data warehouse for internal analysis and reporting using the S3 connector.

Configure SuprSend webhook in vendor dashboard to track delivery data 👍

Ensure to include the SuprSend webhook callback URL in your vendor dashboards for WhatsApp, Short Message Service (SMS), and email. This enables tracking of delivery, seen, and click statuses for display in logs and analytics.

For real-time updates to your system, you can also add your webhook endpoint as an outbound webhook in SuprSend. SuprSend processes data received from your end-vendors in a standard format, eliminating the need to adapt your system for different vendor data structures.

​
Per-Tenant workflow

Tenants represent a segment that a user belongs to. These can include organizations, teams within an organization, subsidiary companies, or different product lines within the same business. While SuprSend doesn’t directly associate workflows with tenants, you can dynamically pass tenant_id in your trigger to send a notification for a tenant. This picks the properties corresponding to that tenant for custom notification content and considers per-tenant preferences when executing the workflow. Read more about tenant workflows here.