> 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/forms-events.md).

# Events - actions

Add conditional actions for logic and automation to forms based on events

### Trigger actions on an event

Actions are triggered by events such as:

* On click 
* On load - open
* On update
* On (value) change

Select the applicable event and add actions:

### Actions on fields

Select the tab **"Events"** in the right side bar.

For the available actions click [**here**](/any2info-academy/no-code-platform/app-studio/application-design/forms/fields-toolbox/general/events-actions.md).

### Actions (conditional) on form pages

Select the tab **"Action flows"** in the right side bar. 

Configure conditional actions as [action flows. ](/any2info-academy/no-code-platform/app-studio/app-logic/forms/action-flow.md) 

For the available actions click [**here**](/any2info-academy/no-code-platform/app-studio/application-design/forms/fields-toolbox/general/events-actions.md).

### Trigger action flows on an event

Select a form page or a form field.

Select the tab **"Events"** in the right side bar 

Add or edit an action

Select perform action and choose "**Trigger action flow**"

Select the appropriate Action flow

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FCntobvadtzbvzkxuLpVl%2Fimage.png?alt=media&amp;token=37e660e1-1de9-4be8-bdf2-a9074e84cbee" alt=""><figcaption></figcaption></figure>


---

# 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/forms-events.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.