Wait
Pause the workflow for a configured duration.
The Wait action delays execution for a set time using hours, minutes, and seconds. The combined duration is stored as timerInfo.numberOfSeconds (maximum 82,000 seconds in the form, about 22.8 hours).
When to use
- Cool-down before a follow-up message.
- Scheduled spacing between campaign steps.
- Give the customer time to act before a reminder or fallback.
Configuration
| Field | What it does | When to use |
|---|---|---|
| Wait (time selectors) | Hours / minutes / seconds; updates timerInfo | Set delay length; invalid totals above max are not applied |
| Description | Canvas note | Document why the pause exists |
The time UI uses three dropdowns (zero-padded). Changing any unit recalculates total seconds and persists hours, minutes, seconds, and numberOfSeconds.
Flow behavior
- Input: Any prior node.
- Output: One edge when the wait completes (runtime scheduling uses platform automation/event infrastructure).
- Does not create sub-nodes.
Examples
Reminder after one hour
- Send WhatsApp question with Wait for user response off.
- Wait → 01:00:00.
- Send a second WhatsApp reminder.
Short buffer before API call
- Wait → 00:00:30.
- HTTP Request to your backend.
Related
- WhatsApp — timeout sub-node (different mechanism)
- Sub-nodes
- HTTP Request