Resolve recipient
Route by subscription → sms/whatsapp
Resolve recipient works out who should be notified and on which channel (SMS or WhatsApp) based on your saved subscriptions, then routes the job to the right delivery step.
How it works
This node answers the two questions that come before any alert: who gets it, and how. It looks at your saved subscriptions, the record of who signed up to hear about what and on which channel, and matches the current job to the right person and their preferred way of being reached.
It exists so you do not hard-wire a phone number into a flow. People come and go and change how they want to be contacted, and the subscription list is where that lives. Resolve recipient reads from that list at the moment of sending, so the alert always goes to the current right person on their current channel.
Once it has decided, it hands the job off to the matching delivery step. A subscriber set to SMS is routed to the text step; one on WhatsApp goes to the WhatsApp step, so the same flow reaches everyone the way they asked to be reached.
Common use cases
Real situations where this node earns its place in a flow.
Send to whoever subscribed
Resolve which person or channel should receive an event based on their subscription, then hand off to SMS or WhatsApp.
Pick the right channel
Route each recipient to the channel they opted into instead of guessing.
Resolve recipient in a workflow
A simple example of where this node sits in a flow.
What you set up
- Make sure the relevant subscriptions (who, what, which channel) are saved first.
- Pick the value on the job that identifies which subscribers this alert is for.
- Connect the SMS and WhatsApp paths so each resolved channel has a delivery step.
Common questions
Where do the recipients come from?
From your saved subscriptions, the list of who opted in to which alerts and on which channel. Resolve recipient reads that list at send time, so changes to it take effect on the next job.
What if someone is on WhatsApp instead of SMS?
It routes them to the WhatsApp step instead of the text step. Each subscriber goes down the path for the channel they chose, so one flow can reach a mixed audience correctly.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
sourceAppWhich source app's subscription table to look the inbound event up in, to resolve the recipient's channel (sms / whatsapp) to branch on.
Type: stringDefault:photoenroll
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "relay-resolve",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "relay-resolve",
"kind": "processor",
"title": "Resolve recipient",
"subtitle": "Route by subscription → sms/whatsapp",
"config": {
"sourceApp": "photoenroll"
}
}
}