Web Push

Simply signup on SuprSend to create your account. If you already have your company account setup, ask your admin to invite you to the team.

Integrate SuprSend Web SDK and webpush vendor in your website.

​

Different workspaces and their usage

You’ll see 3 workspaces in your SuprSend account: Sandbox, Staging and Production. Workspaces can be switched from top navigation bar.

• Sandbox is setup for quick testing with sample workflow, a sample user with your registered email and pre-configured channels (email, SMS, WhatsApp, Inbox) for quick testing. It’s ideal for quick exploration and testing and is available for limited period.
• Staging is your development workspace. You’ll do all your iterations and testing in this workspace before pushing it to production.
• Production workspace is where you’ll configure your live notifications and sync your actual product users. We do not recommend making changes directly in your production workspace. It will safeguard you from accidentally sending a test notification to your production users.

Call this method as soon as you know the identity of user, that is after login authentication. Pass the id that you use as internal user identifier (UUID, email or numeric code). You’ll use this same id in recipient field to trigger the notification.

suprsend.identify(_distinct_id_);

//Sample
suprsend.identify("291XXXXX-62XX-4dXX-b2XX");
suprsend.identify("johndoe@gmail.com");

​

Call reset to clear user data on log out

Don’t forget to call reset on user logout. If not called, user id will not reset and multiple tokens and channels will get added to the user_id who logged in first on the device.

suprsend.reset();

Workflow houses the automation logic of your notification. Each workflow starts with a trigger, processes the defined logic, and sends one or more messages to the end user. You can create a workflow from SuprSend dashboard by clicking on button on the workflows tab.

To design a workflow, you need:

1. A Trigger point- Trigger initiates the workflow. You can initiate it

   • Using the direct workflow API, where you can include recipient channel information, preferences, and actor details directly in the trigger.
   • By emitting an event: You can trigger these events from your frontend application or from your backend systems, depending on the use case. (note: the recipient needs to be pre-created for event-based triggers).

2. Delivery node- Delivery Nodes represent the channels where users will receive notifications. You can use:

   • multi-channel nodes, to send messages across multiple channels,

   • smart channel routing, to notify users sequentially rather than bombarding them on all channels at once (though it’s generally better to use).

   • Template in delivery node contains the content of the notification. You can add both static and dynamic content sourced from user properties or trigger payloads. We use handlebars as our Whatsapp templating language. You can add dynamic content as {{var}}.

   Add trigger data in the mock to get variable auto-suggestions during editing. Ensure to publish the template before using it in a workflow.

   Learn how to design Webpush template here.

3. Functional nodes (Optional): These are the logic nodes in the workflow. You can use it to add delay, batch multiple notifications in a summary or add conditional branches in the workflow.Check out all workflow nodes here.

You can trigger a test workflow directly from dashboard by clicking on ‘Text’ button in your workflow editor or “Commit” changes to trigger it from your code. We follow Git like versioning for workflow changes, so you need to commit your changes to trigger new workflow via the API. You can check all methods of triggering workflow here.

To trigger a workflow, you need:

1. Recipient: End user who would be notified in the workflow run. Recipient is uniquely identified bydistinct_idwithin SuprSend and must have the relevant channel identity set in their profile. You can define recipient inline in case of API based trigger orcreate user profilefirst for event based trigger.
2. Data or Event Properties: This will be used to render dynamic content in the template (added in template mock) or variables in the workflow configuration.

We’ll be triggering the workflow with direct API trigger for quick testing. You can check all trigger methods here.

​

Sample Payload for API based trigger

You can get workspace key, secret or API Key for trigger from Settings tab -> API Keys . Push channel will be updated in user profile as soon as you identify the user in step 4, so you can just pass the distinct_id and data in the trigger.

curl --request POST \
     --url https://hub.suprsend.com/trigger/ \
     --header 'Authorization: Bearer __api_key__' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "workflow": "_workflow_slug_",
  "recipients": [
      {
        "distinct_id": "0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09",
        "name":"recipient_1"
      }
    ],
  "data":{
      "first_name": "User",
      "invoice_amount": "$5000",
      "invoice_id":"Invoice-1234"
    }
 }

Once triggered, you can monitor the request and it’s status on the ‘Requests’ tab, and view step-by-step debugging of each execution on the ‘Execution’ tab inside workflow.

In SuprSend, each environment is isolated, meaning workflows, users, and vendors are configured separately in testing and production workspaces.