Zapier delay step, Delay by Zapier, delay until or delay after queue
Delay puts a Zap on hold before its next actions run, for a set time, until a date or in a one at a time queue. Delay steps use no tasks, need a paid plan and can hold a run for up to 30 days.
Delay is a step that makes a Zap wait before carrying on. It's how you send a follow up three days later, chase something on a due date or space actions out.
There are three types. Delay For waits a set amount of time. Delay Until waits for a date and time. Delay After Queue lines runs up and lets them through one at a time, which helps avoid rate limits and duplicate records when lots of runs land together.
Delay steps don't use tasks, and they're on Professional, Team and Enterprise. A run can wait for up to 30 days. If the Zap is off when a delay ends, the steps after it don't run, so a Zap with delays in it needs to stay on.
I use Delay for follow ups, like checking whether a proposal has been signed a few days after it's sent. Pairing it with a Filter means the chaser only goes out when it's still needed.
Delay After Queue is the delay I use most. On busy builds, when a batch of records hits ClickUp at once, a queue lets them through one by one, which keeps clear of ClickUp's API rate limits.
Paid plan. Signed proposals stop at the Filter after 1 task.
No. Delay steps don't count towards your task usage.
30 days. For anything longer, I'd use a date in ClickUp and a scheduled check instead.
No. Delay holds up the actions that come after it. The trigger still fires when the event happens.
I set these up and train your team, in your own ClickUp or Zapier account.
Book a callContact Jack - jack@withtoki.co.uk