> For the complete documentation index, see [llms.txt](https://angoor-ai.gitbook.io/angoor-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://angoor-ai.gitbook.io/angoor-ai/basics/configuration/forms-attributes.md).

# Forms/Attributes

The **Forms** section enables teams to create structured data collection templates that integrate directly with AI prompts, task flows, and customer workflows. These forms act as reusable input modules that standardize and capture user data effectively for personalized automation.

## **Forms Dashboard**

The main **Forms** dashboard displays all created forms along with essential metadata:

* **Name:** Title of the form for internal reference.
* **Number of Fields:** Count of data fields configured in the form.
* **References:** How many times the form is used in workflows.
* **Creator:** Form author (if available).
* **Tags:** Custom labels to group forms for organization and retrieval.

<figure><img src="/files/GqVOXqZnATBRmaqt8UoL" alt=""><figcaption></figcaption></figure>

## **Creating a Form**&#x20;

**Step 1:** On the Forms dashboard, click the **“New”** button.

**Step 2:** In the modal that appears, enter the form **Name** and **Description** & click **“Submit”**&#x20;

**Step 3:** Click **“+ Add”** under *Form Elements* to insert a new field.

**Step 4:** Assign a **Field Name** for internal reference.

**Step 5:** Toggle **Mark as Mandatory** if the field must be filled by users.

**Step 6:** Select the appropriate **Data Type** (e.g., *String, Number, Boolean,* etc.).

**Step 7:** Repeat the steps for additional fields, then click **“Save”** to finalize your form..

<figure><img src="/files/djdg3FniAuZCKr5LfqZK" alt=""><figcaption></figcaption></figure>

## Field Types

A **Field Type** for each element, selected from multiple categories:

* **Core**: Basic data types (e.g., `String`, `Number`, `Date`, `Array`, `Phone`, `Email`, etc..
* **Platform Fields**: Internal objects (e.g., `User`, `Agent`, `Form`, `Channel`, `Flow`, `Tool`, `Report`, `Knowledge`, etc).
* **Executions**: Triggers or actions (e.g., `Flow Execution`, `Tool Execution`, `Agent Execution`, `Whisper Execution`, `Document To Text`, etc).

## Use Cases

* Collect structured inputs from users before routing to live agents.
* Capture names, emails, and preferences on landing pages.
* Gather issue-specific fields (e.g., product type, urgency).

## Best Practices

* Group related fields into one form for reuse across workflows.
* Use “Mandatory” fields only when critical to ensure smooth UX.
* Keep field types consistent to reduce validation errors.


---

# 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://angoor-ai.gitbook.io/angoor-ai/basics/configuration/forms-attributes.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.