> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/integrations/airtable.md).
# Airtable
Airtable is a spreadsheet-database hybrid, with the features of a database but applied to a spreadsheet. To use Airtable with PixieBrix, you’ll need to set up an integration.
### Finding Airtable Base Id
Your "base" is your board the holds the data. To find your baseId, go to the base or project in Airtable.
When on a base, you can find the ID in the URL. It’s the first string that comes between the `/` and starts with `app`.
Copy the whole string, everything between `airtable.com/` and the next `/`
### Configuring an Airtable Integration in PixieBrix
{% hint style="info" %}
To set up a cloud integration that your team can access, head to the [Admin Console](https://app.pixiebrix.com/). *If you'd rather set up something locally, use the Extension Console. Learn more about* [Configuring Integrations](/integrations/configuring-integrations.md).
{% endhint %}
From the **Integrations** section in the Admin or Extension Console, click the **+** **Add Integration** button in the top right corner**.**
Search for and select Airtable.
Name your configuration something clear to you and fill out the base id and the scopes you need access to.
Click **Save,** and your integration is ready for use in any Airtable mods or bricks. Some notable bricks include:
* Get Airtable Data
* Send Airtable Data
* Update Airtable Data
---
# 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.pixiebrix.com/integrations/airtable.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.
.png?alt=media&token=551382f9-9cb9-4469-afdd-2f7f2132eb94)
