mailerpress/list-workflow-conditions returns the available condition operators and fields for workflow rules.
It arrives already shaped as {operators: [...], fields: [...]}, so nothing needs wrapping.
At a glance
| Ability | mailerpress/list-workflow-conditions |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A CONDITION node splits a workflow. The fields are what it can test — contact attributes, tags, list membership, engagement — and the operators are how.
Pairing them wrongly is the usual authoring error: an operator that expects a list given a scalar, or a date operator applied to a text field. Both produce a condition that evaluates false for everybody.
That failure is invisible in exactly the way the tag-deletion failure is — the workflow runs, the branch is never taken, and it looks like nobody qualified.
Conditions can reference tags and lists by name as well as by ID, which is why mailerpress/find-workflows-using asks for both when checking dependencies.
Multi-way splits use settings.branches on the node rather than a chain of two-way conditions.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
operators | array | The available operators. |
fields | array | The fields a condition can test. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What can an automation branch on?
It resolves to one call:
{
"ability": "mailerpress/list-workflow-conditions",
"parameters": {}
}Worth knowing
- A mismatched operator and field evaluates false for everybody, silently.
- That looks identical to nobody qualifying.
- Conditions can reference tags and lists by name as well as ID.
- Multi-way splits use the branches setting, not chained conditions.
Related abilities
- MailerPress Create Workflow — compose with these
- MailerPress Find Workflows Using — which is why names matter
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category