Add a Wait Between Automation Actions
Insert a delay so an automation pauses before its next action — for follow-ups, reminders, and giving other work time to finish.
Sometimes you don't want everything to happen at once. The Wait action pauses an automation for a set amount of time before moving on to the next action — so you can space work out instead of firing it all the instant the trigger fires.
New to automations? Start with Automations Overview.
Why Wait?
A few things get much easier with a pause in the middle:
- Follow-ups. Post "we're live!" immediately, then wait an hour and post an "ICYMI" reminder.
- Breathing room. Give a separate process (a render, an export, a sync) time to finish before the next action reads the result.
- Gentler pacing. Avoid dumping several notifications on your team in the same second.
Add a Wait
- Add the action where you want the pause
In the builder, click Add action and choose Wait / delay. Its position in the action list is where the pause happens — actions above it run, then the automation waits, then the actions below it run.
- Set the duration
Choose an amount and a unit — minutes, hours, or days. A single wait can be up to 7 days.
How It Shows Up in the Logs
A waiting automation is genuinely paused, but you don't lose track of it. While it waits, the run shows a Waiting status in Execution Logs. When the timer is up, it picks up exactly where it left off and finishes — and the whole thing stays a single log entry, so you can read the run start to finish.