What this does
Airtable uses a Personal Access Token to let another tool read or change data. The token is a key. Its scopes say what the key can do. Its resources say which bases it can open.
Create the token
- Open Airtable’s Builder Hub → Personal access tokens.
- Create a token with a clear name, such as
n8n production. - Choose the smallest scopes the connection needs. Reading records uses
data.records:read; changing records also needsdata.records:write. - Under Access, add only the bases the connection should use.
- Create the token and copy it once. Store it directly in the tool that needs it.
Airtable tokens do not expire automatically. Rotate them when a collaborator leaves, a token may have leaked, or the integration’s access changes.
Verify the connection
In n8n, create an Airtable credential and paste the token. Add a temporary Airtable step that lists one record from a test table. Run it once and check that the expected row appears.
If you see INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND, check the token scopes, base resource access, your collaborator permission, the base ID, and any organization-level API allowlist.
Security check
- Never put the token in a Code node, webhook URL, prompt, screenshot, or downloadable JSON.
- Use separate tokens for production and experiments when possible.
- Regenerating a PAT invalidates the old value immediately; update n8n at the same time.
Official reference: Airtable’s current Personal Access Token guide.