Zapier loop, Looping by Zapier or a loop step
Looping runs the steps after it once for every item in a list, like one ClickUp subtask per line. The Looping step uses no tasks, but each action inside the loop uses a task every time it runs.
A Zap normally runs once per trigger. Looping lets it work through a list instead, running the next steps once for every item, like every product on an order or every page on a website.
You can loop over text, line items or a set of numbers. A loop can run up to 500 times, and the runs happen in parallel, so don't count on them finishing in order. Each one shows as its own run in Zap history.
There are a few rules. You can only have one Looping step per Zap, you can't put a loop inside a loop, and a loop can't sit on more than one path. Looping is in open beta, and it's available on Professional, Team and Enterprise.
On one website project, I used Looping to create a subtask in ClickUp for every page in the site's sitemap. Nobody had to type out the page list, and every page got its own owner and status.
Looping is where task counts can climb fastest, so I work out the numbers before I build. Anything that can happen once before the loop goes before it, and I keep the steps inside the loop to the bare minimum.
Paid plan. As an example, a sitemap with 40 pages would use 41 tasks: 1 for the fetch, plus 1 for each of the 40 subtasks.
The Looping step itself doesn't. Actions before the loop use tasks once, and each action after the loop uses a task for every item, so 500 items through one action is 500 tasks.
Up to 500 iterations per loop.
No. Zapier allows one Looping step per Zap, with no nested loops. If you need that, the process usually needs rethinking first.
I set these up and train your team, in your own ClickUp or Zapier account.
Book a callContact Jack - jack@withtoki.co.uk