> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-workflows/how-to-use-transitions-in-a-workflow.md). # How to use transitions in a workflow A guide on how to transition between states in a workflow ## Adding transitions between states Transitions control the flow between states and they are crucial for enabling state changes within a workflow. To add transitions between states in your workflow, press the “Add”-button to the far right while editing a state.

Edit workflow state page

You will then be given the option to set up transitions from the state you are editing.

Edit workflow transition page

Select the state you want to transition to from your list of created states. Provide a label and a description to help identify and clarify the purpose of the transition. You can also set up permissions to limit who can use the selected transition. ## Transitions in workflow example In the previous tutorial, "[How to Set Up and Edit a Workflow](/tutorials/guides/how-to-use-workflows/how-to-set-up-and-edit-a-workflow.md)", we established states to define the various stages in a workflow. Now we will create a transition from the state "Draft" to "Enrichment In Progress." Below you can see an example of a workflow where we want to create a transition into the state "Enrichment In Progress". This transition has been given the label "Begin Enrichment" in order to clearly indentify the transition. The description field is used to distinguish transitions in case there are multiple under a single state.

Edit workflow transition

Below you can see an example of a state with a transition added to it.

Transition added to state

Now with the transitions created we continue setting up the rest, until we have the following example of a workflow. Below you can see all the states created with associated transitions between them.

Workflow with states and transitions

--- # 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.struct.com/tutorials/guides/how-to-use-workflows/how-to-use-transitions-in-a-workflow.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.