Dec 18, 2017 06:53 PM
So, I am trying to write a snippet to use in the code step of Zapier.
Their documentation says
[output] An object or array of objects that will be the “return value” of this code. You can explicitly return early if you like.
Setting the output to an array of objects will run the subsequent steps multiple times — once for each object in the array. If Code by Zapier is the Zap’s trigger and an empty array is returned, nothing happens.
My problem is that this sure looks like an array of objects to me, but Zapier says its not. Any ideas?
Aug 13, 2018 09:49 PM
I have set most of my triggers as Slack messages, which I can trigger manually by sending a message to that channel, or set up from an Airtable notification on the event of an updated record in a particular view, for instance.
As far as the input data, in my code at least, it comes from the API fetch which brings in all data straight from a particular Airtable view.
So, the trigger can be anything, it doesn’t have to contain your trigger step. The input data is parsed from the API fetch call in your code.
For example, I have a “send messages with ManyChat” zap.
Maybe that will help a little?
Oct 02, 2018 03:08 PM
Nishant - we (Openside) just released an ehanced zapier connector that can handle bulk items so can read in multiple rows at once to further process. This can likely help you do what you need.
Jul 12, 2019 06:48 AM
varReminderList is currently 1,999 records for me, but Zapier will only let this run if it’s capped at 250 at a time. I would really appreciate it if someone could reply with how I limit the code action so that it only processes the first 250 records from the input. (Once a record is processed, it will be taken out of the loop, so the number will go down to zero once it’s run 8 times.)
THANKS IN ADVANCE! This code snippet has helped us so much over the last few years.
Jul 12, 2019 08:35 AM
Hi @Justin_K - not sure if you saw my previous comment in this thread, but our On2Air: Actions product can handle bulk records and has ability to limit the amount processed to a specific number.