> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/rules/rule-flow.md).

# Rule Flow

**Rule Flow** is a powerful tool rule that allows you to visually connect and orchestrate multiple decision rules—such as Decision Tables, Scripting Rules, Decision Trees, and even other Rule Flows—into a single, cohesive logic process. 

{% hint style="danger" %}
Rule Flow is an outdated rule, please use Decision Flows instead.
{% endhint %}

### **Try Decision Flow**

While **Rule Flow** lets you connect and execute rules in a simple flow, **Decision Flow** takes this further, giving you more power, flexibility, and possibilities.

With Decision Flow, you can:

* Orchestrate multiple rules in one flow
* Perform data transformations and calculations
* Run conditional logic, inline scripts, or external API/DB calls
* Access more node types and advanced connections

**Why Decision Flow is better:**

* **More versatile:** supports a wider variety of decision scenarios
* **Dynamic and powerful:** can handle complex logic easily
* **Runs on the** [**latest solver**](/doc/api/rule-solver-api/rule-solver-api.md)**:** Decision Flows run on new solver engine, where performance improved.

#### Convert Rule Flows to Decision Flows

You can easily convert your existing Rule Flows to Decision Flows using the **Rule Flow Converter**. This allows you to take advantage of all the advanced features of Decision Flow while keeping your existing logic.

Learn more about the [Rule Flow Convertor](/doc/rules/rule-flow/rule-flow-convertor.md)

#### What Rule Flow Enables

* **Modular Logic Design**: Break down complex decisions into smaller, reusable rule blocks that can be linked together visually.
* **Sequential Rule Execution**: Control the order in which rules are evaluated, allowing for multi-step decision processes.
* **Dynamic Data Handling**: Pass data between rules using input/output mappings to create flexible, context-aware workflows.

#### Key Features

* **Visual Rule Flow Designer**: Drag-and-drop interface for building workflows from existing rules.
* **Data Mapping Between Rules**: Define how data moves through the flow, enabling seamless input/output chaining.
* **Nested Rule Flows**: Use one Rule Flow inside another to keep your logic organized and scalable.
* **Import & Export**: Share Rule Flows easily via JSON, allowing for versioning, backup, and team collaboration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decisionrules.io/doc/rules/rule-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.