> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Conditional workflows: what to evaluate before choosing a tool
- URL: https://blog.jestor.com/conditional-workflows-what-to-evaluate/
- Published: 2026-09-16T18:52:07.000Z
- Updated: 2026-09-16T18:52:07.000Z
- Author: Bruno Bannach

**Conditional workflows**, sometimes called conditional pipes, are processes where the path changes according to the data: an amount above a threshold routes to a director, a request of a certain type skips two stages entirely. Most tools claim to support them. What differs is how far the conditions can reach, and that is what to test.

## Why branching is where tools diverge

A linear process is easy to build anywhere. Stages in order, one after another.

Real processes are rarely linear. They branch on amount, on category, on who requested, on whether a document was attached. The gap between tools appears exactly at that branch, and it is invisible in a feature list.

Where branching is usually needed:

- Approval routing by amount and cost center
- Requests that skip stages when a condition is met
- Fields that appear only in certain situations
- Actions available only to specific roles at specific stages
- Different destinations depending on a classification

## What to test in a candidate tool

| Capability                      | Test to run                         | Why it matters                          |
| ------------------------------- | ----------------------------------- | --------------------------------------- |
| Condition on a value            | Route by amount range               | The most common requirement             |
| Condition on a connected record | Route by the client's category      | Conditions often live in another table  |
| Field visibility rules          | Show a field only when relevant     | Reduces error, not just clutter         |
| Conditional buttons             | Show an action only when valid      | Prevents wrong actions                  |
| Conditions per stage            | Different rules at different stages | Processes change shape as they progress |
| Read only states                | Lock fields after a decision        | Preserves the record after approval     |

## How to structure a branching process

1. **Map the decision points** before building anything, listing what each one depends on.
2. **Identify where the condition data lives**, since it is often on a connected record.
3. **Build the main path first**, then add the branches.
4. **Add field level conditions**, so each stage shows only what is relevant.
5. **Add conditional buttons**, so actions appear only when valid.
6. **Lock fields after decisions**, preserving the record.
7. **Test each branch with real cases**, including the rare ones.

## Why field level conditions matter as much as routing

Routing decides where a request goes. Field and button conditions decide what the person sees when it arrives. A process that routes perfectly but shows an approver twenty irrelevant fields still produces slow, error prone decisions.

## Why choose Jestor

In **Jestor**, conditions are not limited to stages. Any field can drive a rule, conditions can read connected records, and the same logic applies to routing, to which fields appear on a card, to which buttons are available and to which panels are shown. All of it is configured in the interface, without code.

## Frequently Asked Questions

### What is a conditional pipe?

A process whose path changes according to the data on the record, rather than running the same stages every time. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can conditions read data from another table?

In Jestor, yes. Conditions can reference connected records, not only fields on the record itself.

### Do conditions only control routing?

No. They can also control which fields, buttons and panels appear.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.