Rule Engine

Define IF-THEN logic rules without code — lightweight conditional branching outside the main canvas.

Overview

The Rule Engine provides a simple, code-free interface for defining conditional logic that runs before, during, or after a workflow. Rules are expressed as IF-THEN statements — if a condition is met, take an action. This is complementary to the Script node in the Workflow Editor: use the Rule Engine for simple routing decisions, and Script nodes for complex data transformations.

Coming Soon

Rule Engine is currently in development. The UI is visible in the Automation mode sidebar but rule authoring and evaluation are not yet active.

Planned Features

Visual rule builder — drag-and-drop condition rows with dropdowns for field, operator, and value. No JSON or code required.
Condition types — string (contains, equals, starts with), numeric (greater than, between), date (before, after, this week), and boolean comparisons.
Actions — route to a different workflow, set a variable, send a notification, or skip the current run entirely.
Rule sets — group multiple rules with AND / OR logic. A rule set can be attached to a workflow as a pre-run gate or a post-run router.
Test mode — evaluate a rule set against a sample payload before activating it in production.

Rule Engine vs. Script Node

Use the Rule Engine when the decision is purely about routing (which path to take next). Use a Script node inside the Workflow Editor when you need to transform or compute new values from existing data. The two approaches complement each other.

Frequently Asked Questions

Is the Rule Engine available to use right now?

Not yet. The Rule Engine screen is visible in the Automation mode sidebar so you can see where it will live, but rule authoring and evaluation are not active in this release. It is listed as a planned feature — check back as future updates activate the visual rule builder and condition/action logic described on this page.

How is the Rule Engine different from a Script node in the Workflow Editor?

The Rule Engine is meant for pure routing decisions — evaluating a simple IF-THEN condition to decide which path a workflow should take next, with no code required. A Script node, by contrast, is for transforming or computing new values from existing data using JavaScript. Use the Rule Engine for straightforward branching logic and Script nodes when you need real data manipulation; the two are designed to complement each other rather than replace one another.

Will I need to write code to build a rule?

No. The planned visual rule builder uses drag-and-drop condition rows with dropdowns for field, operator, and value — no JSON or scripting required. Supported condition types will include string comparisons (contains, equals, starts with), numeric comparisons (greater than, between), date comparisons (before, after, this week), and boolean checks.

Can I group multiple conditions together, and test a rule before turning it on?

Yes, that is part of the planned design. Rule sets will let you combine multiple individual rules using AND / OR logic, and a rule set can be attached to a workflow either as a pre-run gate (blocking execution unless conditions are met) or a post-run router (choosing the next step based on the outcome). A test mode will also let you evaluate a rule set against a sample payload before activating it in production, so you can validate behavior safely before it affects live workflows.