Skip to main content

Smart Channel Routing: Sends notification subsequently at each consecutive channel with a delay (computed using time-to-live) between each channel.

name
string
required

Human-readable name of the node

Example:

"Send smart channel notification"

node_type
string
required
Allowed value: "send_smart_channel_routing"
template
string
required

Slug of the template used for smart channel routing notification content.

Required string length: 1 - 120
Pattern: ^[a-z0-9-_]+$
description
string | null

Description of what this node does

channels
enum<string>[]

Available channels for smart routing algorithm to choose from.

Available options:
sms,
email,
androidpush,
iospush,
webpush,
inbox,
whatsapp,
slack,
ms_teams
channels_expr
string

jq-expression for preparing available channel list dynamically at runtime.

Minimum string length: 2
success
string

Success metric to track for smart channel routing.

Example:
{
"delivered": {
"summary": "Notification delivered",
"value": "delivered"
},
"seen": {
"summary": "Notification seen",
"value": "seen"
},
"interacted": {
"summary": "User clicked the notification",
"value": "interacted"
},
"custom_event": {
"summary": "Custom event name",
"value": "<custom_event_name>"
}
}
success_is_event
boolean

Whether the success metric is a custom event. If not, notification status will be used to determine success.

ttl_value
string

Time-to-live value for the smart channel routing notification in static duration format.

Example:

"1h"

mandatory_channels
enum<string>[]

Channels that will be sent immediately regardless of smart routing logic.

Available options:
sms,
email,
androidpush,
iospush,
webpush,
inbox,
whatsapp,
slack,
ms_teams
routing_basis
enum<string>

Basis for smart channel routing. Determines the order in which channels are tried. Right now only cost_low_to_high is supported. We'll be adding more routing rules like in the order of engagement in future.

Available options:
cost_low_to_high