> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/app-logic/forms/action-flow.md).

# Action flow

An action flow can be used to create a piece of business logic

To start creating a action flow you need to navigate to the action flow tab of the from designer, there you can add a new action flow. The action flow can be given a name and a few other basic properties.

An action flow always starts with a logical operation, currently supported operations:

* If condition
* Switch condition

**If condition**

This condition can be compared to the old rule conditions but with a few new features. Creating powerfull expression is possible by combining multiple expressions, for example:

![](https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FQbMTbdGz5nLbw6GHJk7U%2Fimage.png?alt=media\&token=be899580-1e19-445c-8c95-0bf84a860076)

**Switch condition**

The switch condition can be used to handle multiple cases in one action flow. For example handling form states. 

**Combining conditions**

With action flows it is possible to combine conditions, for example:

![](https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FX4jOTBz9ANh6uZZQGB0s%2Fimage.png?alt=media\&token=09ca7fa3-adeb-49cb-a426-328bec26730b)

To make action flows more readable you can set the title of each of the operations

![](https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FZ5TGIRKtKLgP3azn8rIA%2Fimage.png?alt=media\&token=d52e0fc7-d6cf-4efe-a974-fc333e3e7c9f)


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/app-logic/forms/action-flow.md?ask=<question>&goal=<user_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.