Delays, Attributes, Tags and End Stage
The automation nodes that wait, change the patient's record, and end the workflow
These four nodes run without an agent as soon as a patient reaches them. A patient is only visible on the Care Manager board while inside a stage, so while they sit in one of these nodes they are neither listed nor counted.
Time Delay
Holds the patient for a fixed time, then passes them to the next node.
Field | Meaning | Constraint |
|---|---|---|
Delay | The number to wait | From 0 to 365 days; "Please enter a valid time" or "Please enter a valid time (maximum 365 days)" otherwise |
Unit | Seconds, Minutes, Hours or Days | Starts at 1 second |
- The node card shows the delay, for example "Time Delay" and "3 Days".
- While waiting, the patient is off the board: their previous stage's tasks were resolved when they left it, and no stage lists them. They reappear when the next stage starts and assigns them.
- One output. A missing connection ends the workflow when the delay is over.
Example: after a "Report sent" stage, a Time Delay of 2 Days before a "Report follow-up call" stage keeps the patient off the board for two days, then puts them in the follow-up stage as a fresh task.
Update Attribute
Sets or clears one patient attribute when the patient passes through.
Field | Meaning | Constraint |
|---|---|---|
Attribute | The attribute to change, from the attribute picker | Required |
Select Action on Attribute | Update Attribute to set a value, Remove Attribute to clear it | Disabled until an attribute is picked |
Value | The new value, typed | Shown for Update Attribute only; text wrapped in double braces is refused |
- The patient's name and phone cannot be removed: "Cannot remove name or phone attribute".
- The change is immediate and shows on the patient's User profile and in their Logs.
- One output.
Example: an Update Attribute node after a "Consultation done" stage sets the attribute that marks the programme step, so a later condition node can route on it.
Update Tags
Adds tags to the patient or removes them.
Field | Meaning | Constraint |
|---|---|---|
Select Tag Action | Add Tags or Remove Tags | Required before tags can be picked |
Tags | One or more of your tags, shown as chips | Any number |
- Tags show on the patient's card and under Tags on the Overview, and they can be searched and filtered on across the app.
- The node card shows the first tag and "+N more".
- One output.
Example: Add Tags with the tag "Declined" on the Not interested path lets the marketing team exclude those patients from the next campaign.
End Stage
Ends the workflow for the patient.
- The patient's stage conversation, their open tasks and the workflow's own conversation are resolved.
- The patient leaves the board and appears in the Completed column of the Repository.
- The workflow's Completed count on the list rises by one.
- The node has an output, but nothing follows it.
A patient who completes the workflow can enter it again the next time a trigger fires for them, starting from the start node (see Bringing Patients In).
Draw an End Stage after every last stage. A stage whose outputs are unconnected also ends the workflow when the outcome fires, but an explicit End Stage keeps the design readable.
Where the patient is between stages
Last updated on