Takes a list (such as several articles or rows) and runs the steps after this node once for each item.
Takes a list (such as several articles or rows) and runs the steps after this node once for each item.
This step executes when the flow reaches it along a wired path. It does not call external services by itself unless combined with API or CMS steps — it shapes how the flow continues.
Process List is a logic step in the Logic group. Logic steps control how data moves through the flow: branch on conditions, loop over lists, pause, merge parallel paths, or reshape payloads.
Typical reasons teams add Process List to a flow:
Common patterns on the canvas:
On the Design tab, point to where the list lives in the data from the step directly before this one.
Common after a database query that returns many rows, or an API call that returns a list.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| General | Canvas label and read-only node ID |
| AI | Optional assistant to help draft settings from plain language |
| Design | Node-specific configuration fields |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
_payloadFields | Available Fields | payload-panel | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
listPath | Items to process | iterator-list-path | Yes | — | — |
Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.
After this step runs, later nodes can reference these fields using placeholders such as {{process_list.index}}.
| Field key | Type | Description |
|---|---|---|
index | number | Zero-based index of the current list item. |
total | number | Total number of items being iterated. |
itemCount | number | Number of items in the current list. |
listPath | string | Payload path used to read the list for iteration. |
success | boolean | Whether the operation completed successfully. |
item | object | One element from the list at listPath for this iteration. |
listPath) must be filled before the flow can be saved.Other steps in the same area of the palette:
join-array-to-text) — Logicif) — Logicfilter-list) — Logicdebug) — Logicmatch-regex) — Logic