> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/workflow-concepts/workflow-steps/flow.md).

# Flow

Flow Steps provide essential control mechanisms that determine how your workflows operate and process data. These powerful tools enable conditional logic, iteration, human intervention, and error handling to create sophisticated workflow behaviors.

The Flow Steps include:

1. [**Condition**](/actions/workflow-concepts/workflow-steps/flow/conditional.md) -- create branching paths in your workflow based on logical expressions
2. [**Iteration**](/actions/workflow-concepts/workflow-steps/flow/iteration.md) -- loop through data sets to process items one by one
3. [**Human Review**](/actions/workflow-concepts/workflow-steps/flow/human-review.md) -- pause workflows for manual review and approval
4. [**Content Comparison**](/actions/workflow-concepts/workflow-steps/flow/content-comparison.md) -- identify and visualize differences between content versions
5. [**Error**](/actions/workflow-concepts/workflow-steps/flow/error-step.md) -- handle specific error scenarios with custom messaging

Flow Steps act as the decision-making framework for your workflows, allowing you to implement complex business logic, quality control checkpoints, and fallback mechanisms. By combining these steps, you can create workflows that respond intelligently to different scenarios, process large datasets efficiently, and maintain quality through human oversight.

Use Condition steps to route your workflow based on data values, Iteration steps to process lists of items, Human Review steps to ensure quality through manual checks, Content Comparison steps to highlight differences between content versions, and Error steps to gracefully handle exceptions with user-friendly messages.

{% hint style="info" %}
Note: Flow Steps are primarily designed for Workflow applications. Some steps may have limited functionality when used in Agents.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/actions/workflow-concepts/workflow-steps/flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.