A node has one input and one or more ports. Each port stands for an outcome. Some ports fire right away (such as Executed), others only when something happens (such as paid). A port with muting stops the other ports of that node as soon as it fires.
Two kinds of ports
| Kind | Example | When it fires |
|---|---|---|
| Direct | Executed, out | Right after the node has done its work |
| Outcome | paid, no response after x days, not sent | As soon as that event happens, even days later |
So a message node makes two things happen at the same time: the path behind Executed continues right away (for example to a wait node and a next message), while the node keeps listening for a payment, a bounce or the due date passing.
Muting
For each port it is fixed whether it mutes the other ports:
- paid mutes: after a payment, no response and not sent no longer fire.
- no response after x days mutes: after that, a late payment no longer counts as an outcome of this node (the payment is of course still booked).
- not sent mutes: a message that was not delivered can no longer lead to "no response".
- Executed does not mute.
This way you prevent a customer who has paid from still going down the "no response" path.
Ports without an edge
A port with no edge attached does nothing. That is normal: leave paid empty if nothing needs to happen after payment. If nothing is attached to not sent, the collection order goes to the task list No contact data.
Bringing several paths together
An input can receive several edges: different outcomes can lead to the same next node. If you want to merge paths into one (only the first one continues) or wait until all paths have arrived, there are separate nodes for that, coming soon. See Nodes that are coming.