Skip to main content
A condition node sits between your trigger and your actions. It evaluates a value from the trigger output (or a previous action’s output) against a rule you define. If the condition passes, execution continues to the next node. If it fails, the automation stops at that branch — no actions downstream of it run. Use conditions to make automations precise. Instead of notifying someone every time any test fails, you can add a condition to only proceed when the failing case has priority CRITICAL. Instead of creating a page for every event, you can limit it to events where a specific field matches a pattern.

​
Adding a condition node

1

Open the automation builder

Open your automation and click the + button between two nodes in the visual canvas — or click Add Condition in the node panel on the right.
2

Choose the field to evaluate

Select the field you want to test. The picker shows all fields available from your trigger and any upstream actions — for example, testCaseTitle, priority, status, or a webhook payload field like payload.environment.
3

Select a comparator

Choose how to compare the field against your value. See the comparator reference below.
4

Enter the comparison value

Type the value to compare against. Values are case-sensitive unless you use a text matcher like contains or matches regex.

​
Comparator types

​
Field comparators

Use these to compare structured values like status enums, IDs, or numbers.
ComparatorDescription
equalsThe field value exactly matches the given value.
not equalsThe field value does not match the given value.
is emptyThe field is null, undefined, or an empty string.
is not emptyThe field has any non-empty value.
greater thanThe field value (numeric) is greater than the given number.
less thanThe field value (numeric) is less than the given number.

​
Text matchers

Use these when the field is a string and you need flexible matching.
ComparatorDescription
containsThe field string includes the given substring (case-insensitive).
does not containThe field string does not include the substring.
starts withThe field string begins with the given prefix.
ends withThe field string ends with the given suffix.
matches regexThe field string matches a regular expression.

​
Boolean logic

When you add multiple condition nodes in sequence, they are evaluated one after another — all must pass for execution to continue (AND logic). If you need OR logic — continue if any one condition passes — add a Condition Group node and place your conditions inside it. The group passes if at least one condition inside it passes.
Keep conditions atomic. One rule per node is easier to debug in the execution history than a complex compound expression. If a run stops unexpectedly, you can see exactly which condition node failed and why.

​
What happens when a condition fails

When a condition node evaluates to false:
  • Execution stops at that node for that branch.
  • No action nodes below the failed condition run.
  • The execution is recorded with status STOPPED and the condition node is marked as the stopping point.
  • You can inspect the input value that was evaluated and the rule that failed from the execution history.
A stopped execution is not the same as a failed execution. Stopping at a condition is the expected, healthy behaviour — the automation worked correctly, and the event simply did not meet your criteria.

​
Examples

Only proceed if a test case priority is CRITICAL:
FieldComparatorValue
priorityequalsCRITICAL
Only proceed if a page status is PUBLISHED:
FieldComparatorValue
statusequalsPUBLISHED
Only proceed if a webhook environment field is production:
FieldComparatorValue
payload.environmentequalsproduction
Only proceed if a test case title mentions a specific feature:
FieldComparatorValue
testCaseTitlecontainscheckout