One workflow that adapts to every run

Stop maintaining a separate workflow for every scenario. With conditional logic, steps and whole sections appear only when they apply — driven by the data your team collects or the steps they complete. Everyone sees exactly what they need, and nothing they don't.

Start free trial. * No credit card required.

Support Ticket — Run Live
Categorize the request
Issue typeHardware
Shown because Issue type is Hardware
Run hardware diagnostics
Arrange replacement part
Hidden for this run
Reset software configuration

One smart workflow beats six brittle ones

Copying a workflow for every variation — by region, by product, by yes-or-no answer — means every edit has to be made in every copy. Conditional logic folds those branches into a single workflow that reveals the right steps at run time.

Without conditional logic
  • A separate workflow per scenario to keep in sync
  • Everyone wades through steps that don't apply
  • People skip or guess, and quality slips
With conditional logic
  • One workflow, edited once, that branches itself
  • Only the relevant steps ever appear in a run
  • Clear, focused runs your team can trust

Add a rule in three steps

1

Pick what controls it

Choose a step or a workflow field to drive the rule. A step controls things once it's completed; a field controls them by the value someone enters or selects.

2

Set the condition

Compare the collected data — equal to, greater than, before a date, includes a choice, is blank, and more — or simply require that the controlling step is completed.

3

Choose what it shows

Point the rule at the step or section to reveal, and check off as many steps as you like. In a run those steps stay hidden until the condition is met.

Rules you can read like a sentence

You never touch a formula. Pick a source, an operator, and a value, and Manifestly restates the rule back to you in plain language before you save it — so what you built is exactly what you meant.

  • The editor offers only the operators that make sense for the field's type.
  • A live “in words” summary confirms the rule as you build it.
  • Manifestly blocks circular rules, so a step can never depend on itself.
New rule
Step or field that controls the display Priority
where Priority
must be equal to
value High
when field: Priority
equal to: High
displays the section: Escalation & approval

Branch on the data you already collect

Every data field you add to a step or workflow can drive a rule. Once a teammate answers, Manifestly evaluates the condition and reveals the steps that fit — a number over a threshold opens an approval, a “No” opens a remediation section, a past-due date surfaces a follow-up.

You can also gate purely on completion: a step stays hidden until the controlling step is checked off.

Purchase Request — Run
Enter purchase amount
Amount (USD)$8,400
completing: Enter purchase amount
with value for ‘Amount’ greater than: 5000
displays: Route to finance for approval
Route to finance for approval

Compare any field, the way that field works

The condition editor adapts to the field type — text and choices compare by value, numbers and dates compare by size and time, and any field can be checked for whether it's filled in.

Operators
equal to does not equal includes greater than greater than or equal to less than less than or equal to before after is blank is not blank

Numbers and dates unlock the comparison operators; lists and choices add includes; dates read as before and after.

Field types you can branch on
Short textvalue match Choose from listsingle or multi Numberthresholds Date & timebefore / after Email & URLvalue match Data Table choicevalue match

File, image, and signature fields drive rules by whether they're filled in.

Reveal a single step — or a whole section

Point a rule at one step, or at a section header to show or hide everything beneath it at once. And a single condition can control several steps: set it up once from the controlling step and check off every step it should reveal.

  • Show or hide an entire section from one rule on its header.
  • Fan one condition out to many steps in a single pass.
  • Rules survive workflow duplication and JSON export, import, and shared-workflow sync.
QuestionDoes the site need an on-site visit?
= Yes
reveals this whole section
Section: On-site visit
Schedule the technician
Confirm access and safety check
Capture site photos

Predictable at run time, transparent afterward

Conditional steps stay out of the way until they're needed, then appear the moment the condition is satisfied — and the change is written to the run's activity so you always know why a step showed up.

  • Hidden steps don't clutter the run or count against progress until they apply.
  • Every reveal is recorded in the run activity for a clean audit trail.
  • The editor validates rules up front, so values always fit the field they compare.
Escalation approval hidden
Priority set to “High”
Escalation approval now shown
Activity: “Step became applicable when Priority was set to High.”

Where teams branch their workflows

Support & triage

The category chosen at intake decides which resolution steps appear.

Pick “Hardware” → the diagnostics and replacement steps show; the software steps stay hidden.

Approvals & finance

A dollar amount over a threshold opens an extra sign-off.

Amount greater than $5,000 → a finance-approval step appears before the request can close.

Onboarding & HR

Role and location reveal the paperwork that actually applies.

Role is “Remote” → skip the badge and desk steps, show the equipment-shipping section.

Conditional logic, answered

A rule can be driven by a step — it takes effect once that step is completed — or by a data field, where it takes effect based on the value someone enters or selects. You can also require both: the step is completed and its collected data matches your condition.

Equal to and does not equal for any field; greater than / less than (and their “or equal to” variants) for numbers; before and after for dates; includes for lists and choices; and is blank / is not blank for any field. The editor only shows the operators that fit the field's type.

Yes. Set the condition up once from the controlling step and check off every step it should reveal. You can also point a rule at a section header to show or hide all the steps beneath it at once.

It stays out of the run until its condition is met, so it doesn't clutter the view or weigh on progress. The moment the condition is satisfied it appears, and the change is recorded in the run's activity.

No. Manifestly validates each rule and blocks circular dependencies — a step can't control itself, control its own parent, or form a loop through other rules.

Yes. Conditional rules travel with the workflow through duplication, JSON export and import, and shared-workflow sync, so your branching logic stays intact wherever the workflow goes.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

One Workflow That Adapts To Every Run

With Manifestly, your team will Never Miss a Thing.