|
Node |
Check Undelivered Contacts |
|
Description |
This node |
Overview
Drop this node anywhere in a flow where you need to branch based on whether contacts are still pending delivery. When a message reaches it, the node asks the backend for the current undelivered-contact count for the flow, then sends the unmodified message out one of two paths depending on the result.
|
Category |
Inputs |
Outputs |
Default Label |
|---|---|---|---|
|
Contact Operations |
1 |
2 |
Node name, or "Check Undelivered Contacts" if left blank |
Configuration Options
|
Setting |
Default |
What it does |
|---|---|---|
|
Name |
(blank) |
Optional label for the node. |
There's nothing else to configure, the node works automatically based on the flow it's placed in.
Outputs
|
Output |
Label |
Sent when |
|---|---|---|
|
1 (top) |
true (contacts > 0) |
At least one undelivered contact was found for this flow. |
|
2 (bottom) |
false (no contacts) |
No undelivered contacts were found for this flow. |
In both cases the original incoming message is passed through unchanged, only the routing differs.
What Happens When This Node Runs
When a message arrives, the node checks how many contacts are still waiting to be delivered for the current flow, then sends the message out the matching output. While it's running, the node's status dot gives you a quick read on what's happening:
|
Status |
Meaning |
|---|---|
|
🟡 Yellow dot |
Checking for undelivered contacts |
|
🟢 Green dot |
Undelivered contacts found — routed to the true output |
|
🔵 Blue dot |
No undelivered contacts — routed to the false output |
|
🔴 Red ring |
Something went wrong while checking |
If an error occurs, the message isn't sent on either output, nothing continues down the flow from this node until the next message arrives.