Airtable support

Last updated date:

Connect, reconnect, and troubleshoot Airtable without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the Airtable workspaces and bases Seedling should read.
  • Create a personal access token or OAuth grant with schema.bases:read and data.records:read plus the recommended metadata, comment, and email scopes.
  • Grant the token access to the intended resources; scopes alone do not authorize a base.
  • Do not send Airtable credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Airtable API documentationAirtable's current Web API and access-token guidance.

2. Connect Airtable

  1. In Seedling, open Connections and choose Airtable.
  2. Choose personal or workspace scope and paste the authorized access token.
  3. Connect and confirm the verified Airtable identity.
  4. Allow the initial base, schema, view, record, and comment synchronization to complete.

3. Authorization and connection problems

No bases returned
Confirm the token has schema.bases:read and is explicitly granted access to at least one base or workspace.
Records missing
Confirm data.records:read and resource access for the affected base; a valid token can still have no access to that resource.
Comments or users missing
Add data.recordComments:read or user.email:read as applicable, then reconnect with the updated grant.

4. Missing or delayed data

  1. Confirm the base is included in the token's selected resources.
  2. Confirm the relevant table, view, or record remains visible to the token owner.
  3. Check whether a schema change, deleted field, or removed collaborator explains the difference.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create a replacement token with the same or narrower scopes and resource selection.
  2. Replace the credential on the exact Airtable connection and confirm the same provider identity and bases.
  3. After Seedling verifies the replacement, revoke the old token in Airtable.