Node reference

Check Condition for Joomla and WordPress

Checks whether something in your flow data is true or false, then sends the flow down the matching branch — like an if/else in everyday logic.

Overview

Checks whether something in your flow data is true or false, then sends the flow down the matching branch — like an if/else in everyday logic.

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

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

Route VIP customers to a different email template or Slack channel
Skip expensive AI steps when input text is empty
Branch on HTTP status codes from an API REST step
Send content to moderation when a flag field is true

Example workflows

Common patterns on the canvas:

Webhook → If (country) → regional Send Email branches
API REST GET → If (status code) → success vs retry paths

How to set it up

Build your conditions on the Design tab. Each condition gets its own output path, plus a fallback path when nothing matches.

Good to know

Drag fields from earlier steps into your conditions. The check uses the real values from the last run.

Properties panel

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

System (automatic — not edited by the user)

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	—	—

User-configured — General tab

Property key	Label	Type	Required	Visible when	Notes
`label`	Label	`text`	No	—	Node label

User-configured — Design tab

Property key	Label	Type	Required	Visible when	Notes
`conditionBuilder`	Condition Builder	`if-condition`	Yes	—	—

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 {{check_condition.result}}.

Field key	Type	Description
`result`	boolean	True when the condition matched; false on the No Match port.
`payload`	object	Upstream payload unchanged — passed through to the matched output port.

Validation rules

Condition Builder (conditionBuilder) must be filled before the flow can be saved.