Skip to main content
A rule node sends users down different paths based on conditions about the user, their device or the request.
A rule node with a Saved payee rule and Yes and No branches
Rules use the latest data each time the flow reaches them, so a rule after a step sees what happened in that step.

​
Create a yes/no rule

A node with one rule has Yes and No branches. Users who match the rule follow Yes, and everyone else follows No.
  1. Select the rule node, then select Add rule and choose Blank rule. To reuse an existing rule’s conditions, pick it under Start from a copy.
  2. Enter a Name.
  3. Select Add condition, pick a field, then choose an operator and a value.
  4. Choose AND to match when all conditions are true. Choose OR to match when any is true. To mix both, select Add group and set the group’s own choice.
  5. Select Create rule.
The rule editor with two conditions joined by AND

This rule matches when both conditions are true

​
Add more rules

Add more rules to send users down more than two paths. Each rule gets its own branch, labeled with the rule’s name, and users who match none follow Else.
  1. Select the rule node, then select Add rule.
  2. Create the rule the same way as a yes/no rule.
  3. Use the arrows next to each rule to change the order. The node checks rules from top to bottom, and the first match decides the path.
A rule node named User location with US, AU, UK and Else branches

Users in the US, Australia and the UK each get their own branch

A rule node named User location with three rules, US, AU and UK

The node checks US first

​
Fields

Fields are grouped into categories in the field picker. Some need data that you pass in Start Flow’s attributes. See risk signals for how Authsignal calculates signals such as impossible travel.

​
Operators

The operators you can choose depend on the field’s type. In List and Not in list check a custom list. To compare a field with another field instead of a fixed value, open the menu next to the operator and choose Feature.