Airtable

Import structured data from Airtable bases into AGO

Import records from Airtable bases and tables into AGO as knowledge documents. The connector supports custom field mapping, linked record resolution, and metadata extraction.

Feature	Details
Authentication	Personal Access Token (PAT)
Content type	Structured data (records)
Hierarchy	Flat (one document per record)
Multi-language	No
Linked records	Yes (fetches data from related tables)

Prerequisites

1. An Airtable account with access to the base you want to import
2. A Personal Access Token with data.records:read scope
3. The Base ID and Table ID to import

Generating an Access Token

1. Go to Airtable Token Settings
2. Click Create new token
3. Add the data.records:read scope
4. Add access to the specific bases you want to import
5. Copy the token (you won’t be able to see it again)

Finding Your Base ID and Table ID

Open your Airtable base in a browser. The URL looks like:

https://airtable.com/appXXXXXXXXXXXXXX/tblYYYYYYYYYYYYYY/...

• appXXX... is your Base ID
• tblYYY... is your Table ID

Setup Steps

1. Navigate to Knowledge > Sources > Create
2. Select Airtable as the connector type
3. Enter your Personal Access Token
4. Enter the Base ID and Table ID
5. Configure field mapping (see below)
6. Save and run a manual sync

Configuration

Setting	Required	Default	Description
Base ID	Yes	—	Your Airtable base ID (appXXX...)
Table ID	Yes	—	The table to import from (tblYYY...)
Title field	No	Name	Field to use as the document title
Content fields	No	All fields	Specific fields to include in document content
Metadata fields	No	None	Fields to extract as searchable metadata
Display view ID	No	None	View ID for generating “Open in Airtable” links
Linked fields	No	None	Configuration for linked record resolution

Linked Fields

Linked fields let you include data from related tables in the imported documents. For each linked field, specify:

• Field name: The linked record field in your main table
• Target table: The table ID containing the linked records
• Content fields: Which fields from the linked records to include

Example: if your “Articles” table has a “Related Products” linked field, you can configure it to pull in the product name and description from the “Products” table.

What Gets Imported

Each Airtable record becomes one knowledge document:

• Title: The value of the configured title field
• Content: Selected fields formatted as Markdown sections
• Metadata: Configured metadata fields stored as searchable attributes
• External link: “Open in Airtable” link (if a display view ID is set)

Content from linked records is appended to the document under its own section.

Best Practices

• Choose a descriptive, unique field as the title (avoid auto-generated IDs)
• Only include content-rich fields — skip status codes, dates, or technical IDs unless they add context
• Use metadata fields for attributes you want to filter or search by (e.g., category, status)
• Start with a small table to verify field mapping before importing large bases
• The connector prefetches all linked tables at once, so minimize the number of linked table configurations for faster imports

Troubleshooting

Authentication failed

• Verify your Personal Access Token is correct
• Check the token has data.records:read scope
• Ensure the token has access to the specific base

No records imported

• Check that the table contains records
• Verify the Base ID and Table ID are correct

Missing content or wrong fields

• Verify content field names match exactly (case-sensitive)
• Check that fields contain data
• For linked records, verify the target table ID is correct

Rate limit errors

• Airtable limits to 5 requests per second per base
• Schedule imports during off-peak hours
• Large tables are paginated automatically

---

Related

• Knowledge Connectors — All available connectors
• Knowledge Source Management — Managing sources