> For the complete documentation index, see [llms.txt](https://docs.rubica.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubica.au/workflow-automation/setting-conditions-on-a-workflow-trigger.md).

# Setting Conditions on a Workflow Trigger

Narrowing a Workflow Trigger (or Stage Action) down to the right clients — the operators available and how they combine.

A [Workflow Trigger](/workflow-automation/workflow-triggers-creating-a-trigger.md) on its own applies to **every** Account that matches its event — every household with a Next Review Date 14 days out, say. **Conditions** narrow that down to the clients you actually mean: "...but only if they're on an Ongoing service," "...but only Household Accounts, not businesses."

The exact same condition-builder, with the exact same rules, is also available on [Stage Actions](/workflow-automation/stage-actions-overview.md#conditions) — this page covers the mechanics once for both.

## Where to find it

**Home → Settings → Workflow Templates →** pick a template **→ Workflow Triggers** tab **→** open a trigger **→ Conditions** section **→ + Add Condition**. On a Stage Action, the same section appears on the action's edit screen.

## Fields

| Field        | Notes                                                                                        |
| ------------ | -------------------------------------------------------------------------------------------- |
| **Field**    | Any field on the Account the trigger/action is evaluated against — live list, not hardcoded. |
| **Operator** | Equals / Not Equals / Contains — see below.                                                  |
| **Value**    | What to compare against.                                                                     |

### Operators

* **Equals** — exact match.
* **Not Equals** — exact non-match.
* **Contains** — case-insensitive text search. Useful when the exact wording might vary — e.g. a Service Category field where the real value is "Ongoing Fee Arrangement (OFA)" and you just want to catch anything containing "Ongoing".

## How conditions combine

* **AND-only.** Add three conditions and all three must be true — there's no "match any of these" option today.
* **No conditions = always applies.** Zero conditions on a trigger or action means it behaves exactly as it always did — conditions are opt-in.
* **Account only.** Every condition looks at the **Account** the trigger/action is evaluated against — never the Job, and never the Contact. This is deliberate: it's the one thing a real evaluation and a zero-cost [preview](/workflow-automation/testing-and-previewing.md) always have in common, since a Job or Contact might not exist yet when a trigger is being considered.

## Rollout status

* **Workflow Trigger conditions** — live, and verified against real client data (not just synthetic test records) before being switched on for any org.
* **Stage Action conditions** — 🆕 also live now, but freshly shipped — Account-field only for v1, and not yet proven against real production data the way trigger conditions have been. Test with Preview before trusting one on a live client workflow.

## See also

* [Workflow Triggers — Creating a Trigger](/workflow-automation/workflow-triggers-creating-a-trigger.md)
* [Stage Actions — Overview](/workflow-automation/stage-actions-overview.md)
* [Testing & Previewing](/workflow-automation/testing-and-previewing.md)