Trigger different automatic actions based on a yes or no check

Checks a condition you set and automatically runs a different step depending on whether it's true or false.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig(("process is started")):::human s0["check condition"]:::task s1["run matching action"]:::task s2["return outcome"]:::task trig --> s0 s1 --> s2 gx{"× is condition true or false"}:::gate s0 --> gx p00["run true branch action"]:::task gx -->|"condition true"| p00 p10["run false branch action"]:::task gx -->|"condition false"| p10 jn{"○ action completed"}:::gate p00 --> jn p10 --> jn jn --> s1 out[/"outcome returned automatically"/]:::out pay{{"manual decision point automated"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
A stepA personOne path onlyPaths rejoinResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
General Automation
Connects
Command Line

The problem it solves

You have a step in your process where someone has to stop, check something, and decide what happens next. Doing that by hand every time slows the process down and depends on someone remembering the rule correctly.

Who it fits

A business that needs a manual decision point in a process handled automatically instead.

How it works

  1. Someone starts the process, or another system kicks it off
  2. The automation checks whether a specific condition is true or false
  3. Based on the answer, it runs a different follow-up action
  4. The outcome of whichever path was taken is returned automatically
What you get

Workflow branches that run without you watching

You get a decision point in your process handled automatically, running a different next step depending on the outcome.

What you get

A record of which path was taken and the outcome of whatever action ran.

What you need

A server that can run the automation and execute commands; no other accounts are required.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook