Skip to main content

​
Create the credential

In Airtable, open Developer hub → Personal access tokens, create a token for Platinur, and add data.records:read and schema.bases:read. Under access, select only the base Platinur should read. Create and copy the token. From the base URL, copy the base ID (it begins with app); use a table name or table ID for the table value. Do not grant record-write or base-write scopes.

​
Connect

  1. Open Integrations → New Source → Airtable.
  2. Enter the base ID, table name or ID, and personal access token.
  3. Test the connection and create the source.
  4. Discover the table in Schema, then run the first sync.
  5. Add a schedule if the table should refresh automatically.
Paste the values into Base ID, Table name or ID, and Personal access token. Test endpoint validates both the token and the selected base/table. Once saved, use Schema to confirm the records table and then run Sync. Platinur reads pages of up to 100 records and follows Airtable’s offset cursor. Airtable limits requests per base; the connector applies bounded retry behavior and never reports a partial load as successful.

​
Common failures

  • 401 unauthorized: create a fresh personal access token and paste it without quotes.
  • 403 or base not found: include the target base in the token’s access and add both required read scopes.
  • Table not found: use the exact table name, or a table ID, from the intended base.
  • 429 rate limit: wait for retries; avoid simultaneous integrations against the same base.

​
Rotate or revoke access

Create a replacement token with the same two read scopes and base restriction. Update the token on the source Config tab and Test endpoint before deleting the old token. To revoke access immediately, disable or delete the source and revoke the personal access token in Airtable. See Airtable’s personal access token guide and API limit guidance.