Airtable Connector

Connect Airtable so Applied can read and update records in the bases your team uses for support, operations, or customer context.

Use this Connector when a Flow needs structured records from Airtable, such as customer eligibility, account status, order exceptions, or internal operational tables.

Common use cases

Look up records by email or another customer identifier.
List records from a selected base and table.
Create or update Airtable records from Flow outputs.
Keep operational decisions tied to a reviewed Airtable source.

Before you begin

Before connecting Airtable, make sure:

You know which base and table Applied should use.
The Airtable user creating the token has access to that base.
Your team knows whether Applied should only read records or also write them.
You have a test record available for validation.

Personal access tokens cannot grant more access than the Airtable user already has. If the user cannot view or edit a base in Airtable, the token cannot do it through the API.

Get an Airtable personal access token

Airtable personal access tokens are created in Builder Hub.

Open Airtable.
Go to Builder Hub or Developer Hub.
Open Personal access tokens.
Click Create token.
Name the token, such as Applied Labs.
Add the scopes Applied needs.
Select the specific base or workspace Applied should access.
Create and copy the token.

Use selected bases instead of all accessible bases whenever possible.

Choose Airtable scopes

Use the narrowest scopes that cover your Flow:

Add record data read access for record lookups and list actions.
Add record data write access only if Applied should create, update, or delete records.
Add schema scopes only if Applied needs to inspect or change base structure.

Schema changes also depend on the Airtable user’s role in the base. For example, creating fields requires enough base permissions in Airtable, not only token scopes.

Connect Airtable in Applied

Open Connectors.
Click New.
Choose Airtable.
Paste the personal access token into the API token field.
Create the connection.

When you use Airtable in a Flow, provide the base ID and table name or table ID for the action. The base ID is available from Airtable’s API documentation page for the base or from the base URL.

Validate the connection

After setup:

Run a lookup against a test table.
Confirm Applied returns only records from the intended base.
If write actions are enabled, create or update a test record.
Confirm the change appears in Airtable.

Common issues

The token works, but a base is missing

Edit the personal access token and add resource access for the selected base or workspace. Token scopes are not enough if the base is not included.

Reads work, but writes fail

Add record data write scope and confirm the Airtable user has edit access to the base.

The wrong table is queried

Check the base ID and table name or table ID used in the Flow. Airtable table names can be renamed, so table IDs are safer for long-running workflows.