Node: Wait (time delay)

What it is

The "Wait" node pauses a workflow's execution for a fixed period before moving on to the next step. Use it to space out messages, give a customer time to reply, or schedule automatic follow-ups without building a separate trigger.

When to use it

• Delayed reminders ("if they haven't replied in 24 hours, send a nudge").
• Welcome sequences with several messages spread over time.
• A breather between a notification and an automatic close action.

Configuration

• Duration: a whole number (e.g. 30, 2, 1).
• Unit: seconds, minutes, hours, or days.

The node multiplies both fields to get the total wait time. Leaving Duration at 0 skips the wait and the workflow continues immediately.

Example

A "Payment reminder" workflow:

1. Send message: "Hi {{contact.first_name}}, your invoice is due today."
2. Wait: Duration = 1, Unit = days.
3. If (payment not recorded) → Send WhatsApp template with the second reminder.

How it behaves while waiting

While the node is paused, the conversation keeps working normally — the contact can keep messaging and agents can keep replying. The workflow execution shows status "waiting" and resumes on its own once the configured time elapses, even across a server restart for long waits (hours or days).

Tips

• For very long waits (several days), prefer this node over chaining manual triggers — it's more reliable.
• If you need to react to something BEFORE the time is up (e.g. the customer replies), use "Wait until an event happens" instead.

Troubleshooting

• "The workflow looks stuck": check the execution history — it's most likely sitting in "waiting" status until the configured time is reached, not an error.