​

Step Conditions

​

When to Use

• The step executes when the condition evaluates to true.
• Use null to remove the condition (the step always executes).

​

Merge vs Replace vs Remove

​

Variable Reference Format

​

Common Patterns

​

Subscriber offline

{ "==": [{ "var": "subscriber.isOnline" }, "false"] }

​

In-App not read

{ "==": [{ "var": "steps.<stepId>.read" }, "false"] }

​

In-App not seen

{ "==": [{ "var": "steps.<stepId>.seen" }, "false"] }

​

HTTP response value equals

{ "==": [{ "var": "steps.<http-step-id>.status" }, "active"] }

Only when the property is declared in the HTTP step’s responseBodySchema. See http-request-step.md.

​

Payload value equals

{ "==": [{ "var": "payload.priority" }, "high"] }

​

Payload value not equals

{ "!=": [{ "var": "payload.priority" }, "low"] }

​

AND / OR / NOT

{ "and": [condition1, condition2] }

{ "or": [condition1, condition2] }

{ "!": [condition] }

​

Output

​

See Also

• design-workflow/references/step-conditions.md — side-by-side Dashboard JSON-Logic vs Framework skip semantics, plus the full list of available subscriber.* properties and step-output paths
• http-request-step.md — declare responseBodySchema so an HTTP response field becomes addressable in steps.<http-step-id>.<property>
• design-workflow/references/channel-selection.md — when to use the “subscriber offline” gate on Push