> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/integrations/airtable/working-with-forms.md).
# Working with Forms
Working with [Forms](https://help.adalo.com/component-basics/how-to-create-and-edit-forms-and-fields) with an Airtable Database is about the same as when working with a standard database built in Adalo, but there are a few differences. \
\
Currently, sending attachments such as images or other files to a database in Airtable using a form is not supported at this time. When adding a form into your app on Adalo, many fields will automatically appear on your form that will need to be removed.
This includes:\
\- Image properties\
\- Attachment properties\
\- id\
\- Created Time\
\- Relationship properties\
\- Formulas
\
**Update forms**
Forms are the primary way your users can edit records in your app's database. Images and attachments cannot be add through forms when using an Airtable database, but you are able to update records that have them. As stated above, image fields must be removed from forms to work properly. If you find that updating these records is removing the images, you will want to make sure that your Endpoints are set up correctly. How to set up your endpoints is covered in the [*Connecting to Airtable*](https://help.adalo.com/integrations/external-collections-with-apis/airtable/connecting-to-airtable) help document.
---
# 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.adalo.com/integrations/airtable/working-with-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.