Skip to main content
To send a notification with SuprSend, you need three things: a template for the content, a user to receive it, and a workflow that decides when and where it goes.

​
Template

A template holds the content of your notification. One template covers every channel you send on — email, SMS, push, inbox, etc. — each with its own editor. Which of those channels actually send is decided in your workflow, not here. Wherever the content changes from one notification to the next, you write a variable:
  • $recipient — the user receiving the notification. SuprSend fills this from their profile.
  • order_id — a key you name yourself. It arrives in the payload you send when you trigger the workflow.
See every variable a template can use. Your workflow reaches this template by its slug.
SuprSend template editor showing channel tabs, the variables panel, and a variable in the message body

Template editor with channel tabs and the variables panel

Full guide: Templates

​
User

A user is whoever receives the notification. SuprSend identifies each one by a distinct_id — the user ID from your own database. Their profile holds two things: the channel identities that reach them — email address, phone number, push token — and properties you set yourself, like plan or timezone. A channel only sends if the user has an identity for it. Your template can carry both email and SMS content, but a user with no phone number on file gets the email alone.
SuprSend user profile showing channel identities and profile properties

User profile with channel identities and profile properties

Full guide: Users

​
Workflow

A workflow holds the logic your notification runs through — when it goes out, on which channel, whether it waits for a condition to hold true first, etc. Every workflow needs a trigger node to start it and a delivery node to send, and the delivery node is where you name your template by slug. A delivery node sends on a channel only when all four are true:
  • The channel’s content is live in your template.
  • The user has an active identity for that channel.
  • The user has not opted out of that channel.
  • A vendor is connected for that channel.
Workflow edits stay in a draft until you Commit — same as templates.
SuprSend workflow canvas with a trigger node and a delivery node, showing the template and channels selected on the delivery node

Workflow with a trigger node and a delivery node, showing the template it sends

Full guide: Workflows. For ready-made examples, browse the sample workflow library at Workflows → New Workflow → Use Sample Workflow.

​
Triggering a workflow

A workflow starts in one of three ways:
  • Event — your code sends what happened, like order.shipped, plus the data your template needs. Every workflow linked to that event name runs.
  • Workflow API — your code calls one workflow by its slug, and passes the recipients and the data your template needs.
  • List entry or exit — the workflow starts when a user joins or leaves a list.
Full guide: Trigger a workflow. To choose between event and API: Event vs Workflow API.

​
Logs

Open the Logs tab to see what happened. A notification is logged at three stages: A Completed workflow execution does not mean the message was delivered. Only the message log confirms that.
SuprSend logs page on the Messages tab showing per-message status

Message logs with delivery status for each message

Full guide: Logs

​
Other concepts

Terms you’ll run into as soon as you go past a single send.

​
Next steps

Send your first notification

Set up a template, a user, and a workflow end to end.

Design a workflow

Add delays, batching, and multi-channel delivery.