> For the complete documentation index, see [llms.txt](https://docs.betsybot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betsybot.xyz/configurable-commands/data-commands/forms.md).

# Forms

{% hint style="info" %}
**Good to Know: A form resource must be created before you are able to create a data command that opens a form. More information around creating a form can be found in** [Server Resources](/extras/server-resources.md)
{% endhint %}

Forms are a new feature to Discord as of March of 2022 and as a proof of concept this forms data command was created to have the initial supports around this.

{% hint style="warning" %}
As of August 2022 Discord Forms still only support the string and textbox types. We are still waiting for Select and number types before moving too far with this feature as use cases are currently small.
{% endhint %}

{% hint style="warning" %}
As of August 2022 only a maximum of 5 fields are allowed in any Discord Form.
{% endhint %}

When a form has been submitted you will be able to view all the submissions in the admin panel.


---

# 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.betsybot.xyz/configurable-commands/data-commands/forms.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.