# Add a "Loop on Items" step in Automations, similar to the functionality found in ActivePieces

**URL:** https://community.teable.ai/t/add-a-loop-on-items-step-in-automations-similar-to-the-functionality-found-in-activepieces/220
**Category:** Feature Requests
**Tags:** cloud
**Created:** [April 29, 2026, 3:12pm UTC](https://community.teable.ai/t/add-a-loop-on-items-step-in-automations-similar-to-the-functionality-found-in-activepieces/220 "2026-04-29T15:12:09Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 29, 2026, 3:12pm UTC](https://community.teable.ai/t/add-a-loop-on-items-step-in-automations-similar-to-the-functionality-found-in-activepieces/220/1 "2026-04-29T15:12:10Z")

</div>

**What’s the feature?**

Add a “Loop on Items” step in Automations, similar to the functionality found in ActivePieces.

**Your use case**

I write an array of data into a table using the Teable API. I then need Teable automation to loop through each row of that data, evaluate and process it, and send it to other platforms. Currently, I have to use ActivePieces alongside Teable to meet this requirement. It would be fantastic if Teable natively supported a similar “Loop on Items” step!

For example, if I send a JSON array containing 1,000 rows to a Teable automation via a webhook, I would like Teable to be able to loop through this array and add only the data that meets specific conditions into the table.

It might also be necessary to include a “Wait” step. For example, adding a 100ms delay within the loop—waiting 100ms after processing each row before sending the processed data to an external webhook. This would ensure compliance with the rate limits of external APIs.

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 29, 2026, 6:14pm UTC](https://community.teable.ai/t/add-a-loop-on-items-step-in-automations-similar-to-the-functionality-found-in-activepieces/220/2 "2026-04-29T18:14:11Z")

</div>

Hi @OtakuSay , just to clarify, Teable does have a Loop action, but it doesn’t support conditional logic inside the loop. We’d recommend using a Run Script action. You can check our docs for more details:

> **[Loop (batch) - Teable](https://help.teable.ai/en/basic/automation/actions/logic/loop-run)**
>
> Process multiple items in one action by iterating over an array

> **[Run script - Teable](https://help.teable.ai/en/basic/automation/actions/ai/ai-script)**
>
> Describe what you need in plain language and let AI write the automation logic for you

---

<div class="post-metadata">

### Author: ![OtakuSay](https://community.teable.ai/user_avatar/community.teable.ai/otakusay/32/302_2.png) [@OtakuSay](https://community.teable.ai/u/OtakuSay)
#### Post date: [April 30, 2026, 7:58am UTC](https://community.teable.ai/t/add-a-loop-on-items-step-in-automations-similar-to-the-functionality-found-in-activepieces/220/3 "2026-04-30T07:58:23Z")

</div>

Thanks for the suggestion! While using a script action is a viable workaround, could you consider decoupling the Loop functionality into an independent “Loop” step in a future update?

Having a dedicated Loop step that allows for visual, drag-and-drop actions (like adding conditions or delays) inside the loop would be much more intuitive and user-friendly than writing custom scripts for every iteration.

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 30, 2026, 8:49am UTC](https://community.teable.ai/t/add-a-loop-on-items-step-in-automations-similar-to-the-functionality-found-in-activepieces/220/4 "2026-04-30T08:49:44Z")

</div>

To be transparent, Run Script is where we’re putting our energy for automation logic right now — it’s intentionally built to be the flexible core for cases like this. We’ve noted the ask for a visual Loop step though.
