> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/workflows/actions/loop.md). # Loop Executes a block of code a specified number of times or based on a range of values.
### Options * ***Iterable** -* Iterable element which can be traversed or looped through its items one at a time. You can select the previous node value from the data hub or you can provide it directly. * ***Batch Processing** -* Allows processing a group of records in batches, rather than one by one. * ***Batch size** -* Single batch size. To be provided, only if batch processing is enabled. The batch size should be a minimum of 100. ### Examples
IterableBatch ProcessingOutput
[11,12,13,14,15]No

Number of iterations: 5

Iteration 1: {'item': 11, 'index': 0}

Iteration 2: {'item': 12, 'index': 1}

Iteration 3: {'item': 13, 'index': 2}

Iteration 4: {'item': 14, 'index': 3}

Iteration 5: {'item': 15, 'index': 4}

[11,12,13,14,15]

Yes.

Batch size: 3

Number of iterations: 2

Iteration 1: {'item': [11,12,13], 'index': 0}
Iteration 2: {'item': [14,15], 'index': 1}

[{"name": "abc", "age": 20}, {"name": "def", "age": 25}, {"name": "ghi", "age": 30}, {"name": "jkl", "age": 35}, {"name": "mno", "age": 40}]

Yes.

Batch size: 3

Number of iterations: 2

Iteration 1:

{'item': [{"name": "abc", "age": 20}, {"name": "def", "age": 25}, {"name": "ghi", "age": 30}], 'index': 0}

Iteration 2:
{'item': [{"name": "jkl", "age": 35}, {"name": "mno", "age": 40}], 'index': 1}

{{1.response.products}}

Yes.

Batch size: 100

It will return each product data with index.
{% hint style="info" %} *Batch size 3 is used for illustration purpose only. Minimum Batch Size allowed is 100.* {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dckapintegrator.com/project-manager/workflows/actions/loop.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.