Airtable

Overview
How to connect
Automated checks
Useful links

DSALTA connects to Airtable using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.

Read-only access. DSALTA never modifies, creates, or deletes resources in your Airtable account.

What you’ll see. Airtable personal access tokens identify only their own owner, so DSALTA’s Access page lists the connected account (by email), not every individual person in your Airtable workspace. A full member roster requires an Airtable Enterprise account with additional scopes. Treat the Access list as the connected account and confirm its owner against your People page. DSALTA’s Inventory page lists the bases the token can read.

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads the Airtable account that authorised the connection — its email address, a single row on your Access page; and your Airtable resources, which appear on your Inventory page. An Airtable personal access token identifies only its own owner, so there is no roster to read, and whoami returns no name, role or status — the row shows the email in place of a name and is labelled an active Owner by DSALTA, not by Airtable.It calls these Airtable endpoints:

/v0/meta/whoami
/v0/meta/bases

Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Airtable environment.

Troubleshooting

Integration shows Disconnected

There is no Reconnect button. Open Integrations → Connected, click Manage on the Airtable card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Airtable. This can happen if the personal access token was deleted, expired, or had its scopes changed in Airtable.

Data is not syncing

Confirm the personal access token is still valid and still carries the user.email:read and schema.bases:read scopes. If the Inventory page is empty, check that the base(s) or workspace(s) are still added to the token’s Access section, then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.

Start in DSALTA

Open Integrations in the DSALTA sidebar, find Airtable, and click Connect to open the connect panel.

Open Airtable token creation

Go to airtable.com/create/tokens and create a personal access token. A free Airtable account works; no paid or enterprise plan is required.

Airtable Builder Hub, Developers > Personal access tokens, with the Create token button at the top right

Add the required scopes

In the Scopes section, add these two scopes: user.email:read (identifies the connected account on the Access page) and schema.bases:read (lists your bases on the Inventory page). Both are required. Do not add data.records:read. DSALTA never reads record data — the only Airtable calls it makes are /v0/meta/whoami and /v0/meta/bases.

Airtable's Create personal access token form showing the Name, Access and Scopes sections

Grant base access

In the Access section, add the base(s) or workspace(s) you want DSALTA to read. This is required: the token can see no bases until you add them here, and the Inventory page stays empty otherwise.

A token can only reach bases and workspaces the person who created it can already open — Airtable states this on the form itself: “You can only grant access to bases and workspaces that you have access to.” Create the token as someone who can see everything you want on the Inventory page, or use Add all resources, which covers all current and future bases in the workspaces that account owns.

Copy the token

Create the token, then copy it (it starts with pat). You will paste it in the next step.

Copy the token the moment it appears — Airtable shows the secret exactly once. Airtable’s own guide: “Once your token is created, we will only show it to you once, so we encourage you to copy it to your clipboard and store it somewhere safe. While you will be able to manage it in /create/tokens, the sensitive token itself is not stored for security purposes.” If you lose it, delete the token and create a new one.

Finish in DSALTA

Return to the connect panel you opened in step 1, enter the credential you just created, and confirm to complete the connection.

DSALTA's Link Airtable account panel with a single API Key field

Once connected, Airtable appears on the Connected tab and the checks below begin reporting after the first sync.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
User access to Critical System should be valid	Info	Checks that everyone with Airtable access is an active employee on the People page.
Offboarded users should not have active access	High	Checks that offboarded employees no longer have active Airtable access.

Topic	Link
Setup	Creating personal access tokens
General	Airtable website
DSALTA	Connection error messages

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting