Hello, I am new’ish to Zapier and am trying to figure out how improve a Zapier Loop that ultimately creates an item in Webflow (with multiple locales) and then send an Email out with the newly created Webflow item’s URL.
The question itself is more around how to better time the email send out in Zapier.
Here is an excerpt of my process.

The way this works, is that I loop through 100 items at a time (as a way to handle rate limits across Webflow/Airtable/Sendgrid) and then pause a minute per loop.
During each loop, I create a Webflow item (and its locales) in drafted mode (A), and then send out an email (B), and then every 100 loops I trigger a Webflow site publish (C) which makes all the drafted items live.
The problem is that there can be a slight race condition where a user might instantly open their email and click the URL to the Webflow item before it has been published (which happens within a minute or so of email send-out currently). The nature of this task is pretty important so my goal is to ensure that the item is live before the email arrives.
I am trying to find ways to improve this without a bunch of complexity, and I think the route that interests me the most is if there is a way to just push the left branch (the emails) into a separate zap bucket that delays a minute or two and then send out? I.E. This other zap runs once every few minutes with all items pushed into it and loops through sending all the emails out - or something like that.
That way as the loop runs, it will push 100 or so of these emails into a delay outside of the loop (as if I delay in the loop it will drastically slow down the overall time to run this) while the Webflow publish option triggers and then when the emails send there should be no issues regarding the items not existing yet.
Things I already thought about:
- Creating the Webflow items as Live items. This is not possible when using multiple locales - I think it is being worked on but not available yet. :’(
- Moving all the emails to the right path. This would require me to store all the information for the emails in like a cache or Zapier table as they are looped and then loop through again on the Publish step to actually send out the emails… but unsure how much work or extra zap tasks it will cost in order to do this. I think I would have to add another loop too and am unsure if nested looping is supported.
- Add a minute delay before each email is sent out - this would then make every loop take an entire minute (Zapier’s smallest delay time) and would drastically increase the overall run-time. Currently we only delay ONCE per loop at 100 iterations which is also when we trigger the Webflow publish.
Any suggestions or ideas appreciated!
Thank you!





