Wait For Reply
Configure the Wait for Reply widget to pause workflow execution until a user response is received and store reply payloads in variables.
The Wait for Reply widget is used to pause workflow execution until a user response is received within a specified duration.
This widget is commonly used in conversational workflows such as WhatsApp journeys, feedback collection, approvals, and user interaction flows.
Users can configure:
- Wait duration.
- Action when no reply is received.
- Stored variables for saving reply payload data.
Steps to configure Wait for Reply Widget
Drag and drop the Wait for Reply widget into the workflow and connect it to the required workflow step.
Configure the wait duration.
Specify:
- Time — Numeric value for the waiting period.
- Unit — Duration unit such as minutes, hours, or days.
Example:
| Time | Unit |
|---|---|
| 1 | days |
Enable Define action when reply is not received if you want the workflow to handle timeout scenarios.
This allows workflows to trigger alternate actions when the user does not respond within the configured duration.
Configure Stored Variables.
Stored variables are used to save the response payload received from WhatsApp or other supported channels.
Configure:
| Field | Description |
|---|---|
| Stored Variable | Name of the custom variable where the response will be stored. |
| Payload | Payload field selected from the mapper to store in the variable. |
Use the Add Another (+) option to create multiple stored variable mappings.
This is useful when multiple payload fields need to be saved separately.
Save the workflow configuration.
During workflow execution, the workflow waits for the configured reply duration and stores the received response payload in the mapped variables.
Example
| Stored Variable | Payload |
|---|---|
| user_reply | $input.body.message |
| selected_option | $input.body.button.payload |
If no reply is received within the configured duration, the workflow can proceed with the fallback or timeout action if configured.