> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/forms/creating-a-form.md).
# Creating a Form
Gleantap Forms can be used for surveys, lead capture, newsletter opt-ins & a lot more.
**Step 1:** Navigate to **Forms & Pages > Forms**
**Step 2:** Click on the green '+' button on the top right of your screen to create a new form. In the pop-up that appears, either select a template to start off with or click on 'Start from scratch.'
**Step 3:** Fill out the details under the 'Basic Info' and 'Configure' sections.
**Step 4:** Under the 'Create' section, drag-and-drop fields from the list on the right over to the form on the left. When you hover over a field box in your form, you'll see 5 icons:
* The X icon will delete the field box form your form
* The ✎ icon will allow you to edit the label and placeholder text, indicate whether or not a field box is required, and edit other options
* The ❏ icon will allow you to duplicate the field box
* The ↑ icon will allow you to move the field box up one spot
* The ↓ icon will allow you to move the field box down one spot
**Step 5:** Once you are done creating the form, click the 'Save' button!
---
# 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://help.gleantap.com/forms/creating-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.
