The Looping Action in SmartSuite expands your automation possibilities by allowing you to repeat one or more actions for each item in a designated input list. Whether you’re processing multiple records returned by a Find action, iterating over arrays received from a Webhook, or preparing for future integrations like AI outputs, the Looping Action delivers a simpler way to handle repetitive tasks. By placing these repeated actions inside a dedicated “container” within the new Advanced Logic section, you can build larger workflows and keep your automation steps organized.
Feature Overview Video
Plan Availability | All plans |
Permissions | Administrators and Solution Managers |
Platform | Web |
My loop did not run as expected: check these six things, in order
Administrators and Solution Managers can change the automation. If you have neither role, send this page and the record name to the person who manages the solution.
The automation did not run at all. No run is listed in History: the toggle, the monthly action limit or a deleted field. The checks are in Fix an automation that did not run.
The input list. A Find action returns up to 100 records by default, and the maximum by plan is Team 100, Professional 250, Enterprise 500, Signature 1,000. See More About Looping Inputs.
The array. A webhook array must be the root element or a direct child of the root object; arrays nested inside other arrays are not supported. When the source returns several arrays, a second dropdown picks the one to loop through. See Specify the Input List.
Actions after the loop. Once a Looping group is added, no further action can follow it; add the next steps inside the group. See Add Actions Inside the Loop.
The nesting level. Advanced Logic nests two levels deep; at the second level, Looping and Conditional Logic are not available. See Access the Advanced Logic Section.
Current item and the Find action. Reference Current item inside the loop, and keep the Find action that builds the input list outside the group; Merge records is not available inside the group. See Action Limitations Inside the Loop.
Still stuck: select the chat button in the lower-right corner of SmartSuite. The panel shows the current service status under Search for help; to reach support, select Ask a question. Include the automation link (the three-dot menu, then Copy Link), the start time of the run and the record name. The full fix guide is Fix an automation that did not run.
What is an Action?
In SmartSuite automations, an action is the "then" part of an automation sequence. It specifies the task performed when a certain event (trigger) occurs and conditions are met. Actions range from simple tasks like updating records to more complex ones like triggering webhooks or syncing data with external systems.
Configuring the Looping Action
The Looping Action allows you to repeat a set of actions for each item in a selected input list, perfect for processing a batch of records returned by a Find Action, iterating over webhook results, or other similar repetitive tasks. Follow the steps below to get started.
1. Access the Advanced Logic Section
Open an existing Automation or create a new one in SmartSuite.
Click + Add Action, then select Advanced Logic from the action picker (if no Looping Action or Conditional Logic group is already in use).
Choose Looping to add a Looping group container to your automation. Remember that:
Advanced Logic actions nest two levels deep: a loop inside a Conditional Logic branch, a branch inside a loop, or a loop inside a loop. At the second level, Looping and Conditional Logic actions are not available.
Once added, you cannot add further actions after the Looping group.
2. Specify the Input List
Inside the Looping container, you’ll first configure which list should be iterated by the Looping Action:
In Select List, choose the list to loop through. This can be:
A Find Action returning multiple records (up to 100 records).
A When webhook is received trigger or a Make an HTTP(S) request action that outputs an array (of simple types or objects).
A list field on a single record (a Trigger output or a Single Find output); see Looping Through Field Values below.
Items may run in a different order than in the input list.
If your selected source (for example a Make an HTTP(S) request action or a webhook trigger) returns multiple arrays, an additional dropdown appears to let you pick the specific array you want to loop through.
More About Looping Inputs
The following are valid options for the “Input List” for a Loop:
Find action
You can select the output of a Find action, which supports both single and multiple Finds, as the input list. A Find action by default returns up to 100 records that will be processed by the loop.
Maximum limits on records found vary by plan:
Team: 100
Professional: 250
Enterprise: 500
Signature: 1,000
Make an HTTP(S) request action
If a Make an HTTP(S) request action returns a list of simple types or objects (an array), you can use this as the input list for a loop.
Webhook trigger
Webhook triggers that output an array of simple types or an array of objects can be used as an input list.
Note
You can loop through the root array or through an array that is a direct child of the root object. Arrays nested inside other arrays are not supported.
AI Workflow Agent action: a Custom Output of the List type can serve as an input list.
3. (Optional) Name Your Looping Group
If desired, provide a custom name for your Looping group in the Group Name field. When you select the list, Group Name is filled in with Repeat for each in “[list name]”, for example Repeat for each in “Tasks”. You can change it.
4. Add Actions Inside the Loop
The Looping Action acts as a container for the actions you want to repeat:
Click “+ Add” within the Looping group container in the left sidebar to add actions.
Configure each action as you normally would.
Nested Logic is supported: you can place a Conditional Logic action or another Looping group inside this Looping group, two levels deep in total (see Automation Action: Conditional Logic).
Current Item
For each iteration, a special output called “Current item” becomes available. This represents the record or array element for that iteration and can be referenced in subsequent actions.
Use “Current item” references inside your actions to dynamically access fields (if iterating over records) or JSON keys (if iterating over objects).
5. Save & Test
Once your Looping group and actions are configured:
Save your Automation in the top-right corner of the screen.
Test your workflow by running or triggering the automation to ensure the Looping Action correctly iterates over all items in your input list.
Looping Through Field Values
You can loop through values from supported fields on a single record, such as a Trigger output or Single Find output.
When setting up the loop, choose the single record source in Select List, then pick the field in Loop by field. The loop runs once for each value in that field. Each cycle's Current item holds the value together with the source record's context. For a Team field, choose whether to loop over the teams themselves or over the deduplicated list of their members.
For example, if an Assigned To field contains three people, the loop runs three times, once for each assigned person.
Supported Field Types:
You can loop through values from these field types:
- Linked Record
- Assigned To
- Team
- Multiple Select
- Tags
- Email
- Phone
- URL
- IP Address
- Lookups to any of the supported field types listed above
Working With Actions Inside a Loop
Once you’ve added a Looping Action and chosen your input list, you can configure and manage the actions that will be repeated for each item in the list. This container-based approach helps you automate repetitive tasks in a structured, intuitive way.
Adding Actions to the Loop
Locate the Looping Container in your automation’s left sidebar.
Click + Add within the container to open the standard action picker.
Select an action to include in the loop (for example Create a record, Update records or Make an HTTP(S) request).
Configure your new action just as you would outside a loop, fields, parameters, and so on.
Referencing “Current Item”
A special output called “Current Item” becomes available inside any action within the loop. This represents the specific record or array element being processed in that iteration:
Record-Based Inputs (e.g., Find Action)
“Current Item” gives you access to each record’s fields (just like a single record output from a Find Action).Array of Simple Types (e.g., [ "task1", "task2" ])
“Current Item” is simply the value of the current element, such as “task1” or “task2”.Array of Objects (e.g.,
[ { "id": "123", "name": "Alpha" }, … ])
“Current Item” lets you reference each object’s keys, “id,” “name,” etc., similar to how you would access fields in a record.
This makes it easy to customize the behavior of each repeated action, for example by inserting “Current Item” details into a new record or sending a parameterized webhook request.
Reordering or Removing Actions
Each action inside the Looping container is displayed in the left sidebar, where you can:
Drag and drop actions to reorder them (if needed).
Remove an action with its three-dot menu > Delete Action. The trash icon on the group header deletes the whole Looping group.
The order shown in the sidebar is the order in which actions execute for each item in the loop.
Action Limitations Inside the Loop
Merge records is not available inside a Looping group.
Ensure that Find Actions (or any action that generates the input list) are placed outside the Looping group if you’re using them as the source for “Current Item” references.
Saving & Testing
Once you’ve added and configured the actions inside your Looping container, click Save or Publish your automation. Testing your automation (manually or via a trigger) will confirm that each item in the input list is processed, and each action in the loop fires in sequence for that item.
Practical Use Cases and Scenarios
The Looping Action opens up a range of possibilities for tackling repetitive tasks and bulk operations in SmartSuite. Below are some common scenarios where looping can simplify your workflow:
1. Bulk Record Updates from a Find Action
If you’ve used a Find Action to retrieve multiple records (e.g., 50 tasks that need to be marked as “Complete”), you can loop through each record and run an Update Record action to change statuses, assign owners, or modify custom fields, all automatically.
2. Sending Multiple Messages or Notifications
Whether you’re integrating with Microsoft Teams, Slack, or a custom messaging system via Webhook, you might need to send individualized messages or alerts for each item in a list. By looping through the items, you can personalize the message content (using “Current Item” placeholders) and ensure that each recipient or channel gets the right information.
3. Iterating Over Webhook Data
A Webhook response often includes an array of items, such as leads, tasks, or customer details. You can use Looping to:
Parse through each item in the Webhook output.
Create new records in SmartSuite for each item (or only for those meeting specific conditions).
Perform follow-up calls to external APIs using each item’s data.
4. Conditional Workflows for Each Item
You can nest a Conditional Logic group inside the Looping group to filter, branch, or halt actions based on each item’s data. For instance, you could loop through a list of orders and only send shipping confirmation emails if the order status is “Paid.”
Last verified 30 Oct 2026.