Skip to main content
Back to Search AI connectors list Airtable combines spreadsheet and database functionality for organizing structured data. The Airtable connector ingests table data from Airtable into Search AI, making it searchable.
SpecificationDetails
Repository typeCloud
Supported contentTables (Records)
RACL supportYes
Content filteringNo

​
Authorization Support

Search AI supports two authentication methods for Airtable:
  1. Personal Access Token (PAT)
  2. OAuth 2.0

​
Airtable Configuration

Personal Access Token
  1. Log in to the Airtable Builder Hub.
  2. Create a new PAT with the following scopes:
    • data.records:read
    • data.recordComments:read
    • schema.bases:read
OAuth 2.0
  1. Register a new integration for Search AI.
  2. 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
  3. Click Generate Client Secret after the client ID is created.
  4. Enable the following permissions:
    • data.records:read
    • data.recordComments:read
    • schema.bases:read
Refer to the Airtable OAuth integration guide for step-by-step registration instructions.

​
Configure the Airtable Connector in Search AI

On the Authorization page of the Airtable connector, provide the following fields and click Connect.
FieldDescription
NameUnique name for the connector
Authorization TypePersonal 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

Search AI supports permission-aware search for Airtable content when RACL is enabled. Airtable implements base-level access control — all records within a base inherit the same base-level permissions, and no granular record-level permissions are available. The sys_racl field is set to the base_id of the base to which the record belongs, serving as the permission entity for access control. For example: 
"sys_racl": [
    "appXXXXXXXXXXXXXX"    // base_id of the Airtable base
]
Since Airtable does not support automatic permission sync, use the Permission Entity APIs to associate users with the base_id permission entity so they can access the related content.