> For the complete documentation index, see [llms.txt](https://docs.fieldsraven.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldsraven.app/airtable.md).

# Airtable

{% hint style="info" %}
Airtable sync is only available a field that has customer resource and JSON value type.
{% endhint %}

<figure><img src="/files/JYagJEZzXR0tCWzfE3i3" alt=""><figcaption><p>FieldRAven: Airtable sync is only available a field that has customer resource and JSON value type.</p></figcaption></figure>

#### 1. If you don't already have an account, create an account and then:

1. Create an empty base
2. Rename first table column/field to match your incoming data first key
3. Delete the fields/columns that Airtable created by default and create your own fields/columns
4. Make sure the type of the field/column matches the types of your incoming data values

<figure><img src="/files/SKQc3D8kitvtjkaJEpdX" alt="FieldsRaven: Create an empty Airtable base"><figcaption><p>1.Create an empty base</p></figcaption></figure>

<figure><img src="/files/1MhDBSRRlSoudbOT8VS6" alt=""><figcaption><p>2.rename first column to match your incoming data first key</p></figcaption></figure>

<figure><img src="/files/U3ZhC01KBsMuqomoS7Hf" alt=""><figcaption><p>3.Delete the fields/columns that Airtable created by default and create your own fields/columns</p></figcaption></figure>

<figure><img src="/files/donHfTlXRSOwt83cU2E8" alt=""><figcaption><p>Final table headers</p></figcaption></figure>

#### Create personal access token, make sure that the scope includes `data.records` read/write and `schema.bases` read/write

<figure><img src="/files/DSoWEKHifVfT754p7dkF" alt="Airtable personal access token settings"><figcaption><p>Airtable personal access token settings</p></figcaption></figure>

{% hint style="warning" %}
Make sure the PAT you are creating has access to the base/app you want FieldsRaven to sync with
{% endhint %}

<figure><img src="/files/30UODoc3iqVKBKcOhrGu" alt=""><figcaption></figcaption></figure>

### Raven setup

<figure><img src="/files/qlvDUeskGanQDhwO0Ggu" alt=""><figcaption><p>Raven: Airtable setup</p></figcaption></figure>

#### Grab Airtable app ID and table ID from the url

<figure><img src="/files/TfH4hss5UiRToVsCXBj3" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/TfeNcQLFPJWUugNIVz7j" alt=""><figcaption></figcaption></figure>

#### Airtable table header fields

Add your Airtable header fields into the raven, separate each field by a comma

### Validation

FieldsRaven will validate all Airtable settings before creating the Raven, if any of the settings is invalid, you'll get an error message

<figure><img src="/files/y4y6QnHQsfsRKppOjew4" alt=""><figcaption></figcaption></figure>

### Airtable automations

Syncing your metafields with Airtable gives you access to all of the automations – depending on your Airtable plan – that Airtable has to offer, it's pretty powerful.

<figure><img src="/files/xSv2a0tCzqhj5vDPqH84" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fieldsraven.app/airtable.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
