Shapes

Filter and organize records

Rules

A decision table: business rules that set fields and can reject records, without code.

Nodes › LogicOpen in Neblex
Good for
Business rules people can read
Role
Works on the records in a flow
Find it in
Nodes › Logic

When to use it

  • Pricing tiers, discounts, eligibility or routing follow rules the business changes often.
  • The rules should live in a table that people edit, not in a flow.
  • Conflicting or missing rules should be visible on each record.

Reach for something else when

Example

A rule sets tier = gold for totals of at least 1000; another rejects negative totals with the reason negative total.

  1. Data table
  2. Rules
  3. Branch
  4. HubSpot

How it works

Settings
Rules (condition, fields to set, reason, reject), or Read the rules from a step (for example a Data table query of a rules table, one rule per record with when, set, reason, reject); Which matching rules apply: the first, every one in order, or exactly one (more is a conflict); Rejected records: tag them, send them to the Rejected output, or fail the step.
Output
Every record, with the matching rules' fields set, _rules (their reasons), _rejected, _reject_reason and _rules_conflict.
Example
total at least 1000 sets tier = gold; total less than 0 rejects with the reason negative total.
More in the guide

Add it to a flow

  1. Open the flow from Build › Workflows.
  2. Open Nodes and find Rules under Logic, or search for it. Click it or drag it onto the canvas.
  3. Drag from the previous step's output handle to its input, then open its settings with ✎ Edit.
  4. Run the flow and click the step to see the records it received and produced.