Skip to main content
Workflows make decisions with three tools: If / Else, Conditional, and an action’s Optional Filters. The difference that matters is whether each one can stop the steps after it.

Choose the right approach


If / Else is a gate

Use If / Else to send the workflow down one of two paths. Adding it creates a True path and a False path, and each connection carries its own condition, so only the path that matches runs. The steps on the other path are skipped.These connections carry a condition:
  • True and False, from If / Else, AI Decision Maker, and integration checks such as Google Workspace Check Email Availability
  • On Approved, On Declined, and On Timeout, from Wait for Approval
Unlabeled connections, and connections labeled Always, carry no condition and never stop a step.
A step runs only if every connection with a condition leading into it passes. If you connect three If / Else True paths to one action, all three checks must match, not just one.

Conditional is a check that never blocks

Use a Conditional when you need a check’s result later, or when several checks should lead to the same action. It checks its conditions, saves the answer as Is Success (true or false), and always lets the workflow continue. The steps after it decide what to do with the answer.To read the answer, open a later action’s Optional Filters, choose the Conditional step in the value picker, then choose Conditional > Is Success.

Optional Filters run an action only when they match

Most actions have an Optional Filters section. When the filters don’t match, the action is skipped, and so is everything after it on the same path. Steps on other paths are not affected.

How conditions combine

If / Else, Conditional, and Optional Filters share one condition editor:
  • Conditions in the same group must all match (AND).
  • Separate groups need only one to match (OR).
For example, to match tickets from noreply@okta.com with “verification code” in the subject, or any ticket from alerts@example.com:The whole condition matches if group 1 or group 2 matches. Combine groups this way to express any mix of “all of these” and “any of these”.

Merge branches into one step

Several paths can lead into one step. Whether that step runs depends on the conditions on the connections coming into it, not on how many paths ran.

Avoid: several If / Else steps joined to one action

Set Ticket Status has three connections with a condition, so it runs only when all three checks match. A ticket that matches one check is skipped.

Use: Conditionals connected to one action

Connections from a Conditional carry no condition, so they never stop the action. The action’s Optional Filters decide, and it closes the ticket if any check matched.To build this, you need a workflow with a trigger and the conditions for each check.
1

Add one Conditional per check

Connect each Conditional to the trigger and give it the conditions for one check. Name each step after what it checks, such as “Sender match”, so you can find it in the value picker.
2

Connect every Conditional to one action

Add a single action, such as Set Ticket Status, and connect each Conditional to it. The connections have no True or False label.
3

Read the results in the action's Optional Filters

Open the action’s Optional Filters and add one group per Conditional, each with Conditional > Is Success equals true. Separate groups are OR, so any one match runs the action. To require several checks at once, put their conditions in the same group.
4

Test one match at a time

Trigger the workflow with a ticket that matches only one check, then open the run and confirm the action ran.
You can also chain the Conditionals one after another before the action. Either layout works, because Conditionals never stop the workflow.

Rejoin after an If / Else

To bring an If / Else’s two paths back together, connect the last step on each path to the shared step. Those connections carry no condition, and only one path runs, so the shared step runs after whichever path was taken.

Skipped and failed steps

  • A skipped step ends its path. Nothing after it runs from that path, and steps on other paths keep going.
  • A step whose only parent failed doesn’t run. A step with several parents still runs as long as at least one of them didn’t fail.
  • A step that several paths lead into runs at most once per run.

Troubleshooting

Open the run and select the skipped step. A log entry that reads “Skipping step because of unsatisfied edge criteria” means a connection with a condition leading into the step did not pass.Check every connection into the step. If more than one comes from an If / Else True or False path, every one of them must pass. Rebuild the checks as Conditionals connected to the step, as shown in Merge branches into one step.
Check every value in the condition for leftover placeholder text, such as [placeholder: enter a subject] from a template or a generated workflow. Replace it with a real value, or the condition won’t match real tickets.
Last modified on November 18, 2026