Triggers - Run a separate flow for each record

Updated 4 months ago by Devinder Singh

Byteline allows you to use triggers that provide multiple input records to start a flow. These include RSS Trigger, Airtable Trigger, and other polling-based triggers. 

Note: This is applicable only for the polling-based triggers. 

In this documentation, Byteline users can learn how to use the advanced section of the application and execute flows for the updated records. 

Note: Initially by default, the setting is set to start one flow per record per second.  

Let’s get started.

How does it work?

When Byteline polls for the updated records, it can return more than one record. Now it can either run one flow for each record (Total flow runs = number of records) or a single flow for all the records (total flow runs = 1). 

For better understanding, here is an example- 

Suppose 10 records are updated in the Airtable within the polling interval of 15 minutes. Then you can either go for one flow run for 10 records or 10 flow runs for 1 record each. 

One Flow for Each Record

This is the default option. The users can use the advanced section to change this setting. Below are the steps. 

Step 1: Click on the edit button to configure the node.

Step 2: Once you click on the edit button, a modal window will appear. Scroll down to the Advanced settings and tick the box where it says "run a separate flow for each record." Hit the Save button

Step 3: Click on the edit button for the Webflow node.

Once you click on the edit button, a modal window will appear and you will see that there will be no loop running in the Webflow Update. This makes the configuration easy. Close the modal window and run the test. 

Once you have configured the node, run a test by clicking on the Test Run button at the top right corner of the interface.

Single Flow for All the Records

The users can use the advance section to run multiple flows on all the records in one go. Below are the steps for a single flow for all the records.  

Step 1: Click on the edit button to configure the node.

Step 2: Once you click on the edit button, a modal window will appear. Scroll down to the Advanced settings and uncheck the box where it says "run a separate flow for each record." Hit the save button

Step 3: Click on the edit button for the Webflow node.

Once you click on the edit button, a modal window will appear and you will see that there is a loop over available in the Webflow Update. This loop over improves the performance quality as the flow is handling multiple records at one time. 

Once you have configured the node, run a test by clicking on the Test Run button at the top right corner of the interface.

How to decide? 

While each method has its benefits, both of them offer some distinctive features as well. Here are a few advantages.

One flow for each record

Two key benefits of one flow for each record for the polling-based triggers are mentioned below:  

  • Default setting - This is the default setting of the interface. It does not require any additional steps to follow. Whenever you run a test, the initially followed procedure is to extract one flow for each record in one second.

  • Easy configuration - The flow is easy to configure as there is no loop-over that needs to be configured. For example, Webflow Update modal window. 

Single flow for all the records

Two key benefits of single flow for all the records for polling-based triggers are mentioned below:

  • Flow can have tasks that run once for all records - When you want to execute a particular task, you must choose multiple record flow. A good example is, Webflow CMS publish. When you want to publish a website, to reflect any changes made to a website, it must be done with multiple records extracted in a single flow as there is no point in publishing the site for each record. 
  • Better performance - Here is an example to explain it in a better way. When you want to update, say 1000 records, in a flow, it will happen very fast as it is within one process. That gives you better performance because the execution happens collectively for multiple records.  

 

Feel free to connect with us for any doubts.


How did we do?