> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/appmixer-studio-features/what-is-flow.md). # What is a flow [Now that you know what Appmixer](/kb/the-basics/what-is-appmixer.md) is and [how all its interfaces work](/kb/the-basics/appmixer-interfaces.md), we'd love you to meet flows. Flows are the core of Appmixer offering you all you need to build an application without writing a single line of code, automate internal or external processes, and ultimately, build a scalable platform that delights your customers. {% embed url="" %} What is a flow? {% endembed %} A flow represents a business process that reacts to events, transforms incoming data, makes decisions, performs actions, stores data and/or loads data to external systems. Flows can be designed in the Appmixer drag\&drop visual Flow designer or created through the Appmixer API. For example, a flow can represent a process that waits for new incoming calls, asks for the user requirement, and based on the result, forwards the call to a relevant department. ![Flow example: Forward call to a relevant department based on user request](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-Mf33eBX1P0qAmWtJ6xO%2F-Mf33tliUNCqLHIazLAC%2F2-1.png?alt=media\&token=5aa2c869-f423-4074-b05d-c3a12e172067) Like it? Great! [Let's learn how to create your first flow](/kb/appmixer-studio-features/creating-a-flow.md). --- # 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.appmixer.com/kb/appmixer-studio-features/what-is-flow.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.