> 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 on a raven with the **customer** resource and the **json** value type. {% endhint %}

FieldRAven: Airtable sync is only available on a raven with the **customer** resource and the **json** value type.

### 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

FieldsRaven: Create an empty Airtable base — 1.Create an empty base

2.rename first column to match your incoming data first key

3.Delete the fields/columns that Airtable created by default and create your own fields/columns

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

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

## Save the Airtable credential 1. Open **Settings** in FieldsRaven. 2. Under **Integration credentials**, enter the Airtable personal access token. 3. Select **Update integration credentials**. FieldsRaven never displays a stored integration credential. Leave the field blank on a later visit to preserve the current token; enter a nonblank value only when you want to replace it. {% hint style="warning" %} An older Raven that already stores its own Airtable token continues to use that token. The legacy Raven credential overrides the credential in Settings, and replacing the Settings credential does not rotate the legacy value. {% endhint %} ## Raven setup Enable Airtable sync on the customer JSON Raven and leave its token field blank to use the shop credential from Settings. The Airtable app ID, table ID, and header mapping remain Raven-specific.

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

### Airtable table header fields Add your Airtable header fields into the raven, separate each field by a comma {% hint style="danger" %} **The submitted JSON's keys must match the raven's header fields exactly** — every key, no extras, none missing. The comparison lowercases and trims both sides and ignores order, so `First Name` matches `first name`, but not `first_name`. One extra or missing key means **the record is never sent to Airtable**. Nothing surfaces on the storefront: the metafield saves normally and the Airtable row simply never appears. This is a common reason an Airtable sync "does nothing". Add a field to your form, add it to the raven's header fields too. {% endhint %} ## Validation FieldsRaven will validate all Airtable settings before creating the Raven, if any of the settings is invalid, you'll get an error message

## 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.