The Wait node lets you pause a workflow before the next step runs. This is useful when you want to delay a message, task, or other action by a specific amount of time.
A Wait node pauses the workflow until the selected delay has passed. Once the delay ends, the workflow continues to the next node automatically.
Wait nodes are commonly used for:
In most workflows, the Wait node is based on the moment the workflow reaches that node. You can delay the workflow by:
Example:
When using a day-based wait, you may also see a Resume at option. This lets you choose the time of day when the workflow should continue after the delay.
For example:
In that case, the workflow waits two days and then continues at 9:00 AM.
Standard waits have built-in limits depending on the unit you choose:
| Wait Type | Minimum | Maximum |
|---|---|---|
| Minutes | 10 minutes | 60 minutes |
| Hours | 1 hour | 24 hours |
| Days | 1 day | 90 days |
If a workflow uses the Appointment Created trigger, the Wait node becomes appointment-aware. In that case, you can use:
These waits are based on the appointment’s scheduled time rather than the moment the workflow reaches the node.
Note: Appointment-based waits are covered in more detail in the Using Appointment-Based Triggers & Waits article.
When a workflow reaches a Wait node, the run pauses until the delay ends. During that time, the workflow run may appear as:
Once the wait is over, the workflow continues automatically.
If your account uses Holiday and Weekend Pause settings for workflow messaging, those settings can affect when email and text actions actually send after a wait ends.
For example, a workflow may finish waiting on Saturday, but the email or text may not send until the next allowed day and time.
Important: A Wait node controls when the workflow resumes. Separate account-level pause settings may still affect when a message is sent.
It starts counting from the moment the workflow reaches the Wait node.
No. The minimum standard minute-based wait is 10 minutes.
No. The maximum standard day-based wait is 90 days.
A standard wait is based on when the workflow reaches the node. An appointment-based wait is based on the appointment’s scheduled time.
Not always. If your account uses holiday or weekend pause settings, the workflow may resume but the message can still wait until the next allowed sending time.
If you need help using Wait nodes in workflows, contact support@leadcenter.ai.
If you can’t find the answers you’re looking for, our support specialists are available to answer your questions and troubleshoot if necessary.