Engage node

The Engage node raises a task for a role, person or team at a centre, and can wait for the answer staff give before the journey continues.

The Engage node (code name Task) puts human work into a journey. It raises a task on a centre's worklist for a role, a specific person or a team. It can either continue at once or wait until staff finish the task and pick an answer, then branch on that answer.

How staff see and complete these tasks is covered in Your task worklist and Working a task.

When to use it

A nurse should call the patient after a missed check-in.
The front desk should confirm insurance before booking, and the journey should wait for the result.
A doctor should review a form answer and decide the next path.

Configuration

Field	What it does	Options and default
Label, Notes	See Label and Notes.	—
Title	The task title staff see. Required: A task needs a title.	Free text.
Send it to, Person, Team	Who gets the task. See Staff task fields.	A role (default), A specific person, A team.
Ask	The role that gets the task. Relabelled Role, if nobody can take it when you choose a person or team. Always required: The task role is always required.	Staff roles. Roles marked (no permissions yet) cannot be picked.
Centre	The centre whose worklist this task appears in. Required. See Field sources.	Default the patient’s usual centre (most visits).
Wait here or move on (Waiting card)	Waits for: A staff member of the chosen role to finish the task and give an answer. See The Waiting block.	Move on at once (default) or Wait here.
Time limit	Wait here only. Required. Counted from the moment the task is raised.	Amount and unit (minutes, hours, days).
Reminder before the limit	Wait here only. Before the limit, the assignee or the role is told again through the task notifications, on top of the escalation policies. Must be shorter than the time limit.	Empty uses the clinic default.
At the limit	Wait here only. A fixed path, shown in the panel as The journey takes the path fallback. In the connection editor it is the outcome Nobody answered in time.	—
Open work when the journey moves on	What happens to this task if it is still open when the journey moves past the step. Operations is the role named in Settings ▸ Journeys.	Clinic default (default), Keep it open, Cancel it, Hand it to operations.
Answers staff can give	The answers staff choose from when they complete the task. Each entry is a Disposition; add one with Add disposition. When the task waits for the outcome, bind each answer to a connection leaving this step.	Optional list.
Description / instructions (Advanced)	Instructions shown on the task.	Free text.
Priority (Advanced)	Task priority. Tenant default applies when empty	Free text.
Skip this step when…, If this step is already in the past (Advanced)	See the overview.	—

Outcomes and branches

Mode	What you can pick in the connection editor's Outcome list
Move on at once	Nothing. Plain connections fire as soon as the task is raised.
Wait here	One entry per answer in Answers staff can give (shown exactly as typed), plus Nobody answered in time.

Publishing is blocked when a waiting Engage has no time limit. The review panel also warns when an answer has no connection bound to it, and when answers are offered but every path ignores them (whatever staff answer, the journey takes the same path). Connect Nobody answered in time too, so the patient has a path when nobody answers.

What happens when it runs

A task with the Title, instructions and priority you set appears on the chosen centre's worklist. If no centre can be found for the patient, the step fails and staff can see the failure on the patient's run.
The task is assigned:
- A role: the task goes to that role at the centre.
- A specific person: the task goes to that staff member. If they are inactive, it goes to the role in Role, if nobody can take it.
- A team: one member on duty at the task centre is picked by the team rule, or the team's default member when nobody is on duty. If nobody is available, the task goes to the fallback role.
Move on at once: the journey continues straight away. The task stays open on the worklist until staff complete it.
Wait here: the patient stays on this step until staff complete the task with an answer (that answer decides the path), until an escalation policy ends the wait, or until the time limit runs out (Nobody answered in time). The reminder goes out the chosen time before the limit.

Some Reach messages carry news that a person must give first. Those messages are held back unless a waiting Engage step, such as a call, comes before them on every path.

Example

Chase a missing consent.

Engage step chase_consent: Title Call patient about consent form, Send it to A role, Ask Front desk.
Wait here, Time limit 1 day, Reminder before the limit 4 hours.
Answers staff can give: will_sign_today, refused, unreachable.
In the connection editor, bind will_sign_today to a connection back to the Sign step, refused to a Close with Outcome kind failure, and unreachable and Nobody answered in time to a second Engage step for the clinic manager.

Tips

Answers appear in the connection editor exactly as typed. Use short, consistent values such as confirmed and not_reachable.
Pick a role that has permissions; roles marked (no permissions yet) cannot receive tasks.
Escalation and reassignment of open tasks follow the escalation policies on the Organisation tab of SettingsPlatform ConfigurationSystem Settings (see Where tasks come from), in addition to the reminder set here.
When a scheduler runs this step, it never waits: the Waiting card shows A step run by a scheduler never waits.

journeysnodesengagetasksstaffdispositions