Capture node

The Capture node sends a feedback form or WhatsApp Flow, watches for one sent elsewhere, or waits for answers to several forms and routes on them.

The Capture node (code name Form) collects structured answers. It works in one of three ways, chosen in its Waiting card:

Move on at once + Send the form now: send a form and continue straight away.
Move on at once + Only watch for a form sent elsewhere: send nothing and continue.
Wait here: wait for answers to one or more forms, route on the answers, and give up after a time limit.

When to use it

Send an intake questionnaire to the patient on WhatsApp, or raise a form on a nurse's screen, without holding up the journey.
Branch the journey on answers: "if pain score is above 7, call the patient; otherwise continue".
Race several forms (for example a WhatsApp form to the patient and a form on the nurse's screen) and continue with whichever is answered first.

Configuration: Move on at once

Field	What it does	Options and default
Wait here or move on	See The Waiting block.	Move on at once is the default.
What this step does	Send now or only watch.	Send the form now (default) or Only watch for a form sent elsewhere.
Variant	The kind of form.	Feedback form (default) or WhatsApp Flow.
Feedback form	Feedback form only. The form to raise. Required.	Your clinic's feedback forms.
Lands with	Feedback form only. The form is raised as a task for this role. Required: Pick the role whose screen shows this form.	Staff roles.
Centre for staff tasks	Feedback form only. The centre whose worklist this task appears in.	Default the patient's usual centre (most visits).
WhatsApp Flow	WhatsApp Flow only. The flow to send. Required.	Your WhatsApp Flows.
Flow CTA text	WhatsApp Flow only. The button text. Required.	Free text.
Message body	WhatsApp Flow only.	Defaults to the CTA text.
Template when the chat is quiet	WhatsApp Flow only. Required. Inside 24 hours of the patient's last message the form goes as it is; after that WhatsApp allows only an approved template, so this template carries the form as its button.	Approved WhatsApp templates whose Flow button opens the chosen flow.
Prefill values (Advanced)	Feedback form only. field → context expression: pick a Field and enter an Expression. Use Add prefill.	Optional.
Flow initial data (Advanced)	WhatsApp Flow only. Use Add flow data.	See limitations.
Skip this step when…, If this step is already in the past (Advanced)	See the overview.	No condition; Follow the journey.

If no approved template opens the chosen flow, the panel says No approved template opens this form yet. Create one under Templates with a Flow button that opens it.

Under the fields the panel reminds you: To react to the answer later, add a Pause step that waits for the event feedback.form_submitted.

Configuration: Wait here (await and route)

Awaits every form in parallel — the first decisive submission wins, routes on its answers, and cancels the rest.

Field	What it does	Options and default
Waits for	Fixed text: The answers to the forms listed below. The first decisive answer wins.	—
Time limit	Required. How long to wait for any answer.	Amount and unit (minutes, hours or days).
Count from (optional)	An expression for the moment to count from.	Empty counts from the start of the step.
Reminder before the limit	Before the limit, a form sent to the patient is sent again and a form raised as a task is brought up again. Empty uses the clinic default.	Must be shorter than the time limit.
Path taken at the limit	The outcome name used when the limit runs out. Required: Name the path the journey takes at the limit.	Free text, for example `no_response`.
Open work when the journey moves on	What happens to an open form task when the journey moves past it.	Clinic default, Keep it open, Cancel it, Hand it to operations.
Skip this step when…, If this step is already in the past (Advanced)	See the overview.	No condition; Follow the journey.

Add each form with Add awaited form. Each form is a card summarised by its filler label (or form name), its delivery and its number of routes. Each card has:

Field	What it does	Options and default
Form type	The kind of form.	Feedback v3 (default) or WhatsApp Flow.
Form	The form or flow. Required.	—
Message body, Flow CTA text	WhatsApp Flow with Active delivery.	Fill in both: a WhatsApp Flow form without them stops the step when it runs.
Template when the chat is quiet	WhatsApp Flow with Active delivery. Required. As above.	—
Filler label	A name for who fills it in, shown in the card summary and in the connection editor.	For example Nurse intake.
Measure key	Saves the form's score as a patient measure under this key.	Optional. A Routine goal can then follow it.
Delivery	How the form reaches the person.	Active (default). Passive: Passive delivery is coming soon — not available in v1.
Recipient	Who receives the form.	Feedback v3: Role only. WhatsApp Flow: Patient or Identity expression (see limitations).
Answer routes	Named routes with conditions on the answers. Use Add route, give it a Route label, and add rows of Question, Condition, Answer with Add condition. With more than one row, Match offers All conditions or Any condition.	Optional.
Outcome when answered	The outcome when an answer matches no route.	Free text, for example `answered`. Required: Review before publishing flags a form without one, and the connection editor lists it only once it has a name.
Prefill values	Question → Expression. Pre-fills this field before the form is sent.	See limitations.

Conditions by question type

Question type	Conditions offered
Text, email, phone, name	equals, does not equal, contains, does not contain
Number, date, date and time	equals, does not equal, greater than, less than
Single choice, dropdown, dimension	equals, does not equal
Multiple choice	contains any of, contains all of, does not contain
Composite	Not routable: Composite questions cannot be routed on in v1 — pick a different question

When options come from a data source, type the answer value yourself (Options come from a data source — enter the answer value directly; for multiple choice, enter answer values as a comma-separated list).

Outcomes and branches

Mode	What you pick in the connection editor's Outcome list
Move on at once	No Outcome list. Plain connections are followed as soon as the step finishes.
Wait here	Each answer route, listed by its Route label (or, without one, as filler label · route code); each form's Outcome when answered, listed as filler label · outcome; and No-response fallback outcome for the Path taken at the limit.

Where a form has no Filler label, the connection editor uses the form's reference instead, which is hard to read. Give every awaited form a Filler label and every route a Route label.

Bind each route, form fallback, and no-response outcome on this node's outgoing edges. Review before publishing warns about outcomes with no connection.

What happens when it runs

Send the form now, Feedback form. A form task is raised for the Lands with role at the chosen centre. If the patient has no contact record, or no centre can be found, the step fails. The journey moves on at once.

Send the form now, WhatsApp Flow. If the patient has messaged within the last 24 hours, the flow is sent as it is. Otherwise the Template when the chat is quiet is sent with the form as its button. If the chat is quiet and no template is set, the step fails. The journey moves on at once.

Only watch. Nothing is sent and the journey moves on at once. To react to the answers later, add a Pause that waits for feedback.form_submitted.

Wait here.

Every awaited form is sent to its recipient at the same time, and the time limit starts.
The first submitted form wins. Its score is saved under its Measure key if set. Its answers are checked against its routes in order; the first match gives the outcome, otherwise Outcome when answered is used. The other forms are cancelled.
If nothing is answered before the limit, the step takes the Path taken at the limit.

A form that cannot be delivered (for example the chat is quiet and no template is set, or the recipient cannot be found) is not sent, and the step waits until the time limit. Connect the path at the limit so these patients are followed up.

Example

Pain check after discharge.

Wait here, Time limit 24 hours, Path taken at the limit no_response.
Add an awaited form: Form type WhatsApp Flow, Form Pain check, Message body and Flow CTA text filled in, Template when the chat is quiet the approved pain-check template, Filler label Patient, Recipient Patient.
Add a route with Route label Severe pain: Question Pain score, Condition greater than, Answer 7.
Set Outcome when answered to answered.
Connect Severe pain to an Engage step for the on-call nurse, Patient · answered to the next routine step, and No-response fallback outcome to a Reach reminder.

Tips and limitations

Feedback forms raised as tasks appear on staff worklists; see Where tasks come from.
When you switch an awaited form from Feedback v3 to WhatsApp Flow, its recipient stays Role. Change it to Patient or Identity expression.

Known gaps

The panel says the path at the limit is also taken when an answer matches none of the routes. In practice, an answer that matches no route takes that form's Outcome when answered. Connect that outcome too.
Flow initial data and the Prefill values of an awaited form have no effect yet.
An awaited WhatsApp Flow form set to the Role or Team recipient is not sent. Use Patient or Identity expression.

journeysnodescaptureformswhatsapp flowfeedback formrouting