The Loop Action is a core component in automation workflows that allows you to perform the same operation sequentially on a set of data records. When you need to process multiple records (such as multiple contacts, tasks, or work orders), the Loop Action can automatically iterate through these records, executing a series of predefined actions for each record, greatly improving work efficiency.
Select array data from upstream steps: Choose a variable containing the database to be processed in the loop, such as the output results from a "Get Records" action
Add Child Executors: Add the operations that need to be performed for each item within the loop body
Application Scenarios: Choose sequential execution when processing order is important (such as sales round-robin assignment); choose parallel processing when efficiency is more important and the processing of data items is independent of each other
Application Scenarios: Choose the abort option when each item must be processed successfully; choose the continue option when partial failures are allowed
Data Type: Usually array / list type
Common Input Sources:
Get Records action (multiple records)Get Members List action (members list)Manually RunWebhook ReceivedLoop Item: Within the loop, child actions can reference the currently processed item through special variables
Variable Acquisition Method:
Output of Each Iteration: Each loop iteration produces its own output result
Overall Output: After the Loop Action completes, it outputs a collection of all iteration results
Downstream References: Actions after the loop can reference the aggregate results of the entire loop, but typically need to use other actions to process these results
Q1: How do I reference the item currently being processed in the loop?
A: First click "Run test" to get the loop item structure, then in the child action, select the appropriate field under "Loop Item" via the variable selector.
Q2: Will the Loop Action have performance issues when processing large amounts of data?
A: When the data volume is very large (over 1000 records), consider using filtering conditions to reduce the processing quantity, or consider processing data in batches to improve performance.
Q3: Can variables outside the loop be accessed in child actions?
A: Yes. Child actions can access not only the current loop item but also all available variables outside the loop.
Q4: How do I track the running status of a Loop Action?
A: You can view detailed logs through the automation run history, including each execution status, processed data, and possible errors.
