This section demonstrates how to configure a workflow from your backend using SuprSend HTTP API method or using SuprSend SDK.

This method of triggering workflows from backend is omni-channel in nature; with a single API method you can trigger workflow on any channel as long as there is a published template available. You do not have to make any changes in your code if you wish to add/ remove a channel or a vendor.

Workflow using SuprSend SDK

You can use SuprSend SDK to easily integrate with SuprSend platform and send communications through SuprSend.

Currently, we have SDK available for following languages:

Workflow using http API

If your backend tech stack is in any other language other than the above SDK options, you can use http API to send communication via SuprSend. Refer doc link

How to check Backend Workflows on SuprSend platform?

  1. Go to the Workflows tab by clicking on 'Workflows' in the left Navigation Panel.

  2. All the workflows with the 'updated by' value = "Dynamic Workflow" are the workflows that are created from Backend.

  3. You can see the Workflows from their name, along with the templates used, notification category, status, updated by, and last updated on.

  4. You cannot edit these workflows on SuprSend platform. You cannot mark these workflows as 'Inactive' from the SuprSend platform either.

How are individual workflow triggers clubbed together?

Each workflow is a unique combination of workflow name, template slug and notification category that you provide in your API method. All the workflows that are triggered for any user with the same values in these 3 parameters will be clubbed under the same name. You can see the statistics of these workflows together.

If you change any of these parameters, a new workflow will be shown in the list with the same workflow name.