Workflow is 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 executed in sequence, form the notification journey. There are 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. We consider workflow as a sequence of notifications.

One example of a multi-channel and multi-stakeholder workflow can be a payment reminder, where you have to send a series of reminders to the company’s users.

  • The first reminder is sent to the admins of the accounts via email.

  • 2nd reminder is sent to the admins as well as the finance team of the company on Inbox first, and then via email if the notification is not seen on Inbox.

Payment Reminder workflow

We recommend creating a single workflow for tracking the journey corresponding to a trigger so that it’s easier for you to track the entire flow, like how many users saw the first notification, how many dropped off after the second notification, which is the best performing channel, and more. It is also easier to maintain and iterate over if you have fewer workflows corresponding to an event.

Test your workflows in staging workspace before deploying to production:

It is best to first design your workflows in staging workspace 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 is associated with a notification category. Notification category is used to group related workflows together and are also used for users to set their preferences across a group of workflows. For example, all shipment related notifications can be grouped under a category Delivery updates and user can then chose to turn off these notifications on email and just receive these updates on push channel.

This preference setting will automatically apply to all workflows with category Delivery updates. You can know more about notification categories here.

​
Version control for workflows

All the workflow changes are first saved in the draft version and are only made live once you commit the changes. This allows you to confidently make changes to workflows, without affecting any running workflow in production.

​
Trigger Workflow

Workflows created on SuprSend dashboard can be triggered via 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 are being sent. You can refer to error guides to comprehend the errors and see how to solve them.

​
Analyze notification performance

SuprSend provides comprehensive analytics for you to track the performance of your notifications. You can track delivery, seen, click across all channels in a single graph, track which channel is performing best, and how users are interacting with the notification. You can also get the notification data back in your data warehouse for internal analysis and reporting using 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, SMS, and email. This enables us to track delivery, seen, and click statuses to show 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 represents a segment that user belongs to. It can be organizations, teams within an organization, subsidiary companies or different product lines in the same business. While there is no association of workflows and tenants directly within SuprSend, you can dynamically pass tenant_id in your trigger to send notification for a tenant. This will pick the properties corresponding to that tenant for sending custom notification content for the tenant and also pick per-tenant preferences while executing the workflow. Read more about tenant workflows here.