> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/pages-and-forms/create-a-form.md).
# Create a Form
In the App Editor, go to the **`Pages & Forms`** tab and use the :heavy\_plus\_sign:**`New`** icon to add a new page to your App.
Zingy App Editor - New Page button
Select **Form** as the type and provide a unique ID for your page.
{% hint style="warning" %}
Please note that the **ID of your form cannot be changed**, but you can change the display name for the page.
The ID is used internally to refer to the form. The ID also gets used as the default name in the page's URL when you publish the form. You are allowed to change the name in the form's URL. See [Page Publishing](/app-editor/page-settings.md#publishing) for more information.
{% endhint %}
Once the App editor creates your form, it will be shown amongst the list of pages and forms.
See [Working with Forms](/app-editor/page-editor/working-with-forms.md) for information about designing to your form.
---
# 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://docs.zingy.ai/app-editor/pages-and-forms/create-a-form.md?ask=&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.
