Node reference

Process List for Joomla and WordPress

Takes a list (such as several articles or rows) and runs the steps after this node once for each item.

Overview

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.

Why use this node

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:

  • Create one CMS record per row returned from a database query
  • Send a personalised message for each item in an API list response
  • Process each attachment or line item from a webhook payload

Example workflows

Common patterns on the canvas:

  1. Select Row (many users) → IteratorSend Email (one per user)
  2. API REST GET (list) → IteratorCreate Article (sync each item)

How to set it up

On the Design tab, point to where the list lives in the data from the step directly before this one.

Good to know

Common after a database query that returns many rows, or an API call that returns a list.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
GeneralCanvas label and read-only node ID
AIOptional assistant to help draft settings from plain language
DesignNode-specific configuration fields

System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

Property keyLabelTypeRequiredVisible whenNotes
_nodeIdNode IDnode-idNo
_payloadFieldsAvailable Fieldspayload-panelNo

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNoNode label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
listPathItems to processiterator-list-pathYes

CMS site configuration (not on this node's properties panel)

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.

Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as {{process_list.index}}.

Field keyTypeDescription
indexnumberZero-based index of the current list item.
totalnumberTotal number of items being iterated.
itemCountnumberNumber of items in the current list.
listPathstringPayload path used to read the list for iteration.
successbooleanWhether the operation completed successfully.
itemobjectOne element from the list at listPath for this iteration.

Validation rules

  • Items to process (listPath) must be filled before the flow can be saved.