> For the complete documentation index, see [llms.txt](https://docs.flexy.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexy.bot/modules/core/triggers/form.md).

# Form

**Introduction**

The "Form" trigger allows you to run the automation manually via panel. When you create an automation using this trigger, an entry will be added on the **Forms** page on the panel.

**Configuration**

* **Description**: A brief description of the form's purpose. Can be up to 1000 characters long.
* **Inputs**: Define the inputs or questions in the form. Each input requires:
  * **Key**: A unique identifier for the input. Automatically generated but can be customized.
  * **Name**: The name of the input field. Must be between 1 and 40 characters. This field is required.
  * **Schema**: The type of data expected for the input (e.g., text, number, choice). Must be specified from available data types.

Forms can have up to 30 inputs, allowing for detailed and structured data collection from users.

**Variables**

* **Inputs**: Inputs that will be required when using the form. This dynamic variable adapts based on the form's configuration, providing access to the submitted data for further processing or decision-making in the automation workflow.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flexy.bot/modules/core/triggers/form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.