Logger for Joomla and WordPress

Writes information to the flow execution log so you can see what happened during a test or live run.

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.

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

• Inspect payload values while building a new flow
• Confirm an API step returned the fields you expect before going live
• Capture execution context during troubleshooting in production

Common patterns on the canvas:

1. Trigger → Logger → Send Email / API REST POST
2. Parallel branches → Merge → Logger → downstream action

Optionally type a short message on the General tab. Leave the message blank to show the full run execution log (each component’s lines, same as Trigger Flow without a Logger).

This node ends the branch — nothing continues after it. Useful for troubleshooting before you wire up the real next step.

The designer shows these tabs for this node:

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

Other steps in the same area of the palette:

• Array to String (join-array-to-text) — Logic
• Check Condition (if) — Logic
• Filter List (filter-list) — Logic
• Match Text (match-regex) — Logic
• Merge (merge) — Logic