What wait nodes do
A wait node tells the automation to hold for a set amount of time before continuing.
Once that wait time passes, the automation moves into the next step automatically.
This is helpful when your workflow should happen in stages instead of all at once.
Why wait nodes matter
Not every follow-up should happen immediately.
Sometimes you want to:
give a lead time to respond
space out communication
delay the next internal task
avoid sending too much at once
build a smoother client experience
Wait nodes help you control pacing so your automation feels thoughtful instead of rushed.
How wait nodes work
You choose how long the automation should pause, then the workflow waits for that amount of time before continuing.
Waits can be set in:
minutes
hours
days
weeks
That means you can build simple timing like:
wait 30 minutes
wait 2 hours
wait 1 day
wait 1 week
Good examples of wait nodes in a workflow
Example 1
Trigger: Contact Form Submitted
Wait: 1 day
Then: Send a follow-up email
This gives the lead a little breathing room before the next message goes out.
Example 2
Trigger: Contract Signed
Wait: 2 hours
Then: Create onboarding tasks
This can help separate client-facing actions from internal team actions.
Example 3
Trigger: Payment Received
Wait: 3 days
Then: Send the next document
This is useful when the next step should happen later in the process, not instantly.
Example 4
Trigger: Questionnaire Submitted
Wait: 1 week
Then: Create a reminder task
This works well when you want to revisit something later without manually remembering it.
When to use a wait node
Use a wait node when:
timing matters
the next step should not happen right away
you want to spread actions out across time
the workflow should feel more natural for the client
your team needs a delayed reminder or follow-up
If the next step should happen immediately, you probably don’t need a wait.
A simple way to think about it
A wait node creates space between steps.
It gives your automation rhythm.
Instead of everything firing at once, the workflow can move at the pace that makes the most sense for the process.
Wait nodes work well with other nodes
Wait nodes are often most useful when paired with:
actions, when you want to delay sending or creating something
conditions, when you want timing before checking a rule
triggers, when you want the workflow to begin now but continue later
Things to keep in mind
A wait node does not stop the automation forever. It only pauses it for the amount of time you choose.
After the wait is over, the workflow continues automatically into the next step.
That makes wait nodes great for follow-ups, reminders, and staged workflows that need better pacing.