> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/tools/paths.md).
# Paths
The **Paths** tool allows your workflow to complete different tasks based on conditions set. It lets you handle different scenarios within an automated process, allowing for more complex and dynamic workflows.
While Paths allow you to split your workflow into separate segments, [Filter](/tools/filter.md) will only display a single step with conditional rules to be met before proceeding to the next step.
## Configure
Once added, the Paths tool will create multiple "paths" (also known as path rules). Each path [will process an automation based on the specified conditions](https://docs.getmesa.com/tools/filter) saved in the Rule fields and will be outlined with a gray border.
Create [multiple rule sets](/tools/filter.md#multiple-1) by clicking More options > Additional Rules.
All steps added within a path will be included in the gray border to visually demonstrate where the path begins and ends in a workflow.
Here is a scenario where it would be helpful to use the **Paths** tool.
1. [**Trigger**:](https://docs.getmesa.com/workflow-builder/triggers) An event starts or triggers your workflow. For example, a customer places an order on your Shopify store.
2. [**Condition or Decision Point**](/tools/filter.md#examples): At some point in the workflow, a condition is evaluated. This could be something like "Is the order's total value greater than $100?".
3. **Paths**: Based on the outcome of the condition, the workflow splits into different paths:
* **Path 1 Rule**: If the condition is true (e.g., the order's total value is greater than $100), the workflow follows this path.
* **Path 2 Rule**: If the condition is false (e.g., the order's total value is $100 or less), the workflow follows a different path.
* **Multiple Paths that evaluate to true**: If multiple Path conditions are true, the workflow follows each path.
4. **Actions within paths**: Each path can have its own set of actions, such as sending a specific email, sending a Slack message, notifying a team member, etc.
## Going Further
* We recommend re-labeling your paths (Path Rules) so that you can easily identify what each will do when your workflow runs. Click the 3 vertical-dot icon then Settings to update the path rule's name.
* If you need similar functionality in all paths, simply duplicate the path by clicking the 3 vertical-dot icon in the top right of the Path step and make adjustments as needed.
* Drag and drop any actions that exist outside of a path into a path when needed.
## Technical Notes
* If you delete a Paths step, all of the actions that follow it will be deleted as well.
---
# 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.getmesa.com/tools/paths.md?ask=&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.
