Zoho Workflow Automation Loops Tutorial

Andrew Simpson
September 2, 2021
In this video, you will learn how to loop Workflow Automation in Zoho CRM

The video is about creating a feedback loop in Zoho CRM's workflow automation to handle large data sets that need to be updated regularly, like syncing records with another software or daily roll up of accounts. The feedback loop involves creating a function in Zoho CRM that updates all products once a day by increasing their price by 1, with a system variable to keep track of the current batch of records. The function loops through the products and updates each product's price, and then checks if there are more products to update. If so, the system variable is updated and the loop is triggered again. If not, the system variable is reset.

Business processes that loop can be automated efficiently and easily inside Zoho CRM. By creating a workflow automation feedback loop, you can set parameters to ensure that the function runs multiple times, such as a daily sync of your Zoho CRM with another software that has 500,000 records a day, or a daily roll up for each account or contact. When creating a function, you can set a system variable to keep track of the loop and create a module to trigger the loop every time a record is created. Finally, you can also use a if-else statement to ensure the loop continues until all products are updated, and reset the system variable when the loop is complete. With the help of Zoho CRM, you can automate anything you can think of and improve your workflow.

Having unchecked loops in your code can lead to an overuse of computing power, as the loop will continue to run until the conditions are met. This can be a problem if you are running your code on the cloud, as the repeated calls to an API can max out the requests and cause your code to fail. Unchecked loops can also cause your code to be very inefficient, as it is running the same code or making the same API calls unnecessarily. It is important to ensure that your loops are properly checked and that they end when they should, in order to avoid overuse of computing power and maxing out of API calls.

Need something else?