> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/forms.md). # Forms - [Forms](https://guides.noloco.io/forms/forms.md): Collect data from your users with forms that add new records to your tables - [Customizing Form Fields](https://guides.noloco.io/forms/forms/customizing-form-fields.md): Customize and configure form fields for truly dynamic forms - [Passing Linked Record Values to a Form](https://guides.noloco.io/forms/forms/passing-linked-record-values-to-a-form.md): Pass a linked record value from a record page to your new record form - [Dynamic Form Field Filters](https://guides.noloco.io/forms/forms/dynamic-form-field-filters.md): Set up and use dynamic filters in your forms, reducing the options for your app users and simplifying form filling - [E-Signature Fields](https://guides.noloco.io/forms/forms/e-signature-fields.md): The E-signature input in Noloco allows users to capture signatures directly within your app. This feature can be used on both desktop and mobile devices, making it versatile and accessible. - [Public Forms](https://guides.noloco.io/forms/public-forms.md): Collect data from anyone --- # 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://guides.noloco.io/forms.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.