Hello! I have a scenario where I use a webhook trigger to process an email and look it up on Apify. However, I don’t want to overwhelm the Apify API, so I was wondering if there’s a setting where the scenario would process each trigger sequentially. This means it would only run the next record in the queue after the previous one has been successfully completed. Appreciate it if anyone has any insights!
1 Like
Hi @Fion_Leung,
Yes, it’s definitely possible to have your scenario process one trigger at a time, which is a great idea if you’re trying to avoid hitting the Apify API too hard.
A good way to do this is by building a simple queue. When the webhook is triggered, instead of running everything immediately, you send that data into a table like Make’s Data Store, Airtable, or Google Sheets. You’ll want to add a new column to that table to track the status of each record, like “pending”, “in progress”, or “done”.
Then, you set up a separate scheduled scenario that runs every few minutes. It looks for the next item marked as “pending”, updates it to “in progress”, runs your API logic, and once it finishes, updates the status to “done”.
That way, you’re only processing one item at a time, and the rest of the records stay in the queue until it’s their turn.
-Robin @Trainward_Consulting
Thanks Robin for your quick reply! I thought about this but since we won’t have operations queued up every day, I didn’t want to waste our operations to be checking this every few minutes. May I know if there’s another way around this that you know of? Thank you so much!