> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/infraon-automation/workflow.md). # Workflow Workflows act as visual flowcharts of processes within Infraon. They are designed to automate and visualize a multi-step process as a sequence of activities, such as assigning tickets, triggering email or SMS notifications, and requesting approvals. With Infraon, workflows can be created using simple drag-and-drop elements, which can be added as a flowchart to indicate the sequence of activities. ## **How to Build a Workflow?** At this point, you can configure workflows for Ticket, Request, and Problem. Workflows can be triggered using single or multiple conditions within the service catalogue. ### **Components of Workflow** To build a workflow, the following components must be defined: #### **Trigger** Triggers are the initial action(s) that trigger the workflow. One or more triggers can be configured. At this point, only service catalogue-based triggers can be added. #### **Conditions** One or more conditions can be added to be validated while executing. To add a condition, define * **Operand** - Operand is the parameter that needs to be validated. In this case, Service Catalogue. * **Value** - Value of the Operand or the parameter's value to validate. * **Relation** - (and/or) Relation between the conditions (applicable only if multiple conditions are selected) --- # 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.infraon.io/infinity/user-guide/infraon-configuration/infraon-automation/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.