Creating & Managing Templates

​

Create a template

• From the Templates page — go to Templates in the sidebar and click + New Template. You’ll link it to a workflow later.
• From a workflow — click Create Template inside a delivery node in the workflow builder. The template is automatically linked to that workflow and its name and slug are pre-filled from the workflow and node names. This is the fastest path when building a new notification from scratch.

1

Click + New Template

From the Templates page or a workflow node, open the creation modal.

Enter a Name (display label, changeable later) and a Slug (the identifier your workflow uses to reference this template — auto-derived from the name, cannot be changed after creation). Renaming the template later doesn’t affect the slug, so existing workflows keep working.

2

Pick channels

Select the channels you want to send on. You can add more channels later by clicking the + tab in the editor, or remove a channel from the channel’s three-dot menu.

​

Write your content

• View mode (default) — shows the published version, read-only.
• Edit mode — click Edit to open the draft. Content auto-saves as you type. Live traffic is never affected until you commit. If you exit without committing, your draft is saved — you can come back and pick up where you left off.

​

The Variables panel

{
  "order_id": "ORD-1234",
  "order": {
    "total": "$49.99",
    "address": { "city": "San Francisco" }
  },
  "tracking_url": "https://yourapp.com/track/ORD-1234"
}

• {{$recipient.name}} — user’s name
• {{$recipient.email}} — user’s email
• {{$recipient.phone}} — user’s phone number
• {{$recipient.distinct_id}} — user’s unique ID
• Any custom property you’ve set on the user profile

• {{$brand.brand_name}} — tenant’s display name
• {{$brand.logo}} — tenant’s logo URL
• {{$brand.primary_color}} — brand colour (used in email Tenant blocks)
• {{$brand.properties.address}} — custom tenant properties (address, support email, etc.)
• {{$brand.$hosted_preference_url}} — hosted unsubscribe/preference page link
• {{$brand.$embedded_preference_url}} — embedded preference widget link

• {{$actor.name}} — actor’s name
• {{$actor.email}} — actor’s email

​

Using variables in content

​

Commit

​

Using the template in a workflow

​

Test

• Test one channel
• Test all channels

1. Pick the Channel (e.g., Email, SMS).
2. Enter a Recipient (email or distinct ID).
3. Optionally pick a Notification Category — determines which vendor config is used (e.g., transactional vs promotional SMS vendor).
4. Optionally pick a Tenant — loads that tenant’s branding into $brand and selects the matching tenant variant. Leave blank to use defaults.
5. Click Send Test.

1. Enter a Recipient — the panel shows every channel that user has identities for.
2. Check the channels to include.
3. Optionally pick Category and Tenant.
4. Click Send Test.

​

Version history

​

Variants

• Languages — a Spanish variant for Spanish-speaking users, Hindi for Hindi. SuprSend auto-selects based on the recipient’s preferred language. See Multi-lingual Templates.
• Tenants — Uber’s users see Uber branding, Acme’s users see Acme’s. One template serves all tenants.
• Payload conditions — show different content based on trigger data (e.g., plan == "pro" gets a premium message).

​

Import content

• This template — another variant (e.g., copy default English into a new Spanish variant, then translate).
• Other templates — any template in your workspace. Pick a variant and preview before importing.

​

Clone and promote

​

Managing templates