Node reference

Array to String for Joomla and WordPress

Array to String is a Logic in Logic. Flattens an array from upstream into one string with your chosen separator.

Overview

Array to String is a Logic in Logic. Flattens an array from upstream into one string with your chosen separator.

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

Array to String 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 Array to String to a flow:

  • Control flow structure around array to string in complex multi-step workflows
  • Combine with triggers and action steps to replace bespoke integration scripts
  • Make branching, looping, or timing explicit and testable in the designer

Example workflows

Common patterns on the canvas:

  1. TriggerArray to StringSend Email / API REST POST
  2. Parallel branches → MergeArray to String → downstream action

How to set it up

Pick array path, separator, and output field name on Design. Nested arrays flatten; objects become JSON strings.

Good to know

Downstream email or Slack nodes can use {{node.joined_text}} (or your output field name).

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

| arrayPath | Array to join | iterator-list-path | Yes | — | Path to a JSON array on the payload (e.g. node_12.rows or rows if relative).

Drag a list field from “Available lists”, or type a dotted path. Values must be an array at runtime; each element is stringified when joined. |

separatorSeparatortext (default: , )No, Inserted between each element (e.g. comma + space, newline \n, or empty). Literal characters only — this field does not expand {{placeholders}}.
outputFieldKeyOutput field nametext (default: joined_text)Nojoined_text Name of the single string property added to the outgoing payload (default joined_text). Use letters, digits, underscores; downstream nodes read this key.

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 {{array_to_string.joined_text}}.

Field keyTypeDescription
joined_textstringText value from this node's output.
join_array_errorstringError message when joining the array failed.

Validation rules

  • Array to join (arrayPath) must be filled before the flow can be saved.