> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/workflows/branch-a-workflow-on-a-previous-action-output.md).
# Branch a workflow on a previous action's result
Branch a workflow on the output of an earlier action, such as a custom action result or a created request, by picking that output from the variable picker in a branch condition
A branch can now look at what an earlier action returned, not only at the request or the employee. That lets a workflow take a different path depending on the answer it got from another tool.
### When this is useful
* A custom action checks a device and returns "Compliant" or "Not compliant", and you want a different next step for each.
* An action returns a ticket type from an external ticketing tool, and you route accordingly.
* A **Create a request** or **Create a group request** step opens something, and you branch on what it created.
### Set it up
1. Open your workflow and make sure the action that returns the value comes before the branch.
2. Add a **Branch** below that action.
3. In a branch condition, open the variable picker (type `/` in the field).
4. Pick the output you want. Outputs are grouped by the action they come from, so you choose something like **Create a new request > Request ID**. Hover over it to see the full path.
5. Choose the operator and the value, then save.
### Good to know
* You only see outputs from actions that run before the branch on the same path. Outputs from later actions or from other branches are not offered.
* Conditions on request or employee fields work exactly as before.
* Existing conditions based on outputs stay editable.
* With **is one of** and **is not one of** on a list-type output, Siit matches the exact value you selected. If your values are "Windows" and "Windows Server", choosing "Windows" will not match "Windows Server".
### Frequently asked questions
#### Why can't I see an output in the picker?
Check that the action runs before the branch, on the same path. If the action sits in another branch, or after this one, its outputs are not available.
#### Which actions return outputs I can use?
Custom actions return the outputs you define when you create them. See [Custom integrations and custom actions](/guides/integrations/custom-integrations-and-custom-actions.md).
### Need help?
Contact .
---
# 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.siit.io/guides/workflows/branch-a-workflow-on-a-previous-action-output.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.
