# Conditions

Conditions are decision points in your workflow. They let you add "if/then" logic so your automation only does certain things when specific criteria are met. Without conditions, every trigger would run the exact same actions every time.

Think of a condition like a fork in the road: the workflow checks something (like an invoice total or a record status), and based on the answer, it goes down one path or another.

## How it works

1. **Drag a condition block onto the canvas** — Open the left sidebar and find the condition you want. Drag it onto the canvas between your trigger and your actions.
2. **Configure the condition** — Click the block and set up what to check. For example, "Is the grand total greater than $500?"
3. **Connect the two paths** — A condition block has two outputs: one for "Yes" (the condition is true) and one for "No" (the condition is false). Connect each output to different action blocks.

## When to use conditions

* **Filter by amount** — Only send an alert if the order total is above a certain threshold.
* **Check status** — Only run an action if the record is in a specific state (e.g., "Overdue" or "Draft").
* **Branch by type** — Send different emails depending on whether the customer is a homeowner vs. a business.
* **Detect changes** — Only notify someone when a specific field changes to a particular value (e.g., Status changed to "Approved").

## Related pages

* [Field Value Checks](/workflow-automation/workflow-builder/conditions/field-checks.md)
* [What Are Triggers?](/workflow-automation/workflow-builder/triggers.md)
* [What Are Actions?](/workflow-automation/workflow-builder/actions.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.proforgeerp.com/workflow-automation/workflow-builder/conditions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.