Recipes: AND/OR conditions and graduating to the node editor

Combine conditions with AND/OR and nested groups (A and B) OR C, then convert a recipe into an advanced flow with “Edit as a flow”.

Jun 26, 2026

Watch this step in the video · AND/OR conditions

What you'll achieve

Recipes are the automations that live inside each Projects board: they read like a sentence, When… then…. This guide is for advanced users who need two things: combining several conditions with AND / OR (including nested ones), and graduating a recipe to the advanced flow editor when it outgrows the simple builder.

Before you start

  • You need edit permission on the board.
  • Open the board, click Automate, and create a recipe with New automation, or edit an existing one.

Combine conditions with AND / OR

  1. In the editor, after the trigger (e.g. When a column changes), click Add condition.
  2. At the top of the conditions block, choose how they're evaluated:
    • AND (all) → runs only when ALL match.
    • OR (any) → runs when ANY matches.
  3. Each condition is column → operator → value. You get operators such as is, is not, contains, is greater than, is before, is set, includes, and more.

Nest groups: (A and B) OR C

A single block can't express mixed logic. Use groups:

  1. Click Add group to create a sub-block of conditions.
  2. Inside the group, pick its own AND (all) or OR (any).
  3. Combine the group with the outer conditions to build, for example, (Status is Done and Priority is High) OR Owner is empty.
  4. To remove a sub-block, use Remove group.

Tip: start with the most restrictive condition. If a recipe never fires, it's almost always because you used AND where you meant OR.

Graduate to the node editor

When you need steps a linear recipe can't handle (several actions in sequence, waits, complex if/else branches), convert it into a visual flow:

  1. In the recipe, click Edit as a flow.
  2. Confirm the warning: the change is one-way. Once in flow mode, the automation is edited in the advanced flow editor and cannot return to the simple editor.
  3. The automation is then tagged Flow in the Automations list.

Verify

  • Change a value on a real task that meets your conditions and confirm the action runs.
  • Open History on the recipe to see whether the run came back completed or failed.

If it doesn't work

  • Never fires: check whether you set AND (all) when you wanted OR (any).
  • Fires too often: a condition is in the wrong group; review your logical parentheses.
  • No "Edit as a flow" option: the automation is already in Flow mode (already graduated).

Related

Was this helpful?

Related articles

Message us on WhatsApp