Condition & Routing

These nodes control the flow of your workflow — splitting into branches, checking conditions, and ending paths.

Condition (Decision Point)

Splits your workflow into a Yes path and a No path based on a condition you define.

When to use it: Any time the next step depends on a value — "Is this a purchase order?", "Is the amount over $10,000?", "Did the AI extraction succeed?"

How it works:

Add a Condition step to your workflow.
Define the condition using data from previous steps.
The workflow splits into two branches. Add steps to each by clicking + on the Yes or No path.

Available operators:

Operator	Meaning
`equals`	Exact match
`contains`	Value contains the text
`not_contains`	Value doesn't contain the text
`less than` / `greater than`	Numeric comparison
`exists` / `not_exists`	Whether the field has a value
`in` / `not_in`	Whether the value is in a list

Example: Route emails based on AI classification:


Condition: {{AI_CLASS.output.category}} equals "purchase_order"
  → Yes: Create Order
  → No: Create Task for human review

Conditions are the backbone of routing logic. A common pattern: classify with AI → Condition to check the result → different actions for each outcome.

Document Category Check

Validates a document against category rules — checking whether a document matches an expected type (invoice, packing list, BOL, etc.).

When to use it: Verifying that uploaded documents are correctly classified before processing them further.

End / No Operation

Terminates a workflow branch without doing anything.

When to use it: Ending one side of a Condition when no action is needed — for example, the "No" branch of a check that only matters when the answer is "Yes."

Need help?

If you have questions or run into issues, we're here to help:

Chat with us — use the support widget in the bottom-right corner of Glacis
Email — reach us at support@glacis.com
Related docs — Creating Workflows | Action Nodes