| Specification | Details |
|---|---|
| Repository type | Cloud |
| Supported content | Tables |
| RACL support | Yes |
| Content filtering | No |
Authorization Support
Search AI supports two authentication methods for Airtable:- Personal Access Token (PAT)
- OAuth 2.0
Airtable Configuration
Personal Access Token- Log in to the Airtable Builder Hub.
- Create a new PAT with the following scopes:
data.records:readdata.recordComments:readschema.bases:read
- Register a new integration for Search AI.
- Set the OAuth Redirect URL based on your region or deployment:
- JP Region:
https://jp-bots-idp.kore.ai/workflows/callback - DE Region:
https://de-bots-idp.kore.ai/workflows/callback - Production:
https://idp.kore.com/workflows/callback
- JP Region:
- Click Generate Client Secret after the client ID is created.
- Enable the following permissions:
data.records:readdata.recordComments:readschema.bases:read
Configure the Airtable Connector in Search AI
On the Authorization page of the Airtable connector, provide the following fields and click Connect.| Field | Description |
|---|---|
| Name | Unique name for the connector |
| Authorization Type | Personal Access Token or OAuth 2.0 |
| Personal Access Token | (If PAT selected) Token generated in Airtable |
| Client ID / Client Secret | (If OAuth 2.0 selected) Credentials from the registered integration |
Content Ingestion
After authorization, go to the Configuration tab. Click Sync Now for an immediate sync, or set up a Schedule Sync for future runs.RACL Support
Access to all ingested Airtable content is controlled by the tableId of the table the content belongs to. This value is stored in thesys_racl field as a permission entity. Use the Permission Entity APIs to associate users with this permission entity to grant access to the related content.