Skip to main content

​
Use Airtable in automations

Connect Airtable with a personal access token (PAT) to use its actions in Flow automations. The token’s scopes, selected resources, and Airtable account permissions determine which actions can succeed.

​
Prerequisites

  • An Airtable account with access to the bases your automation uses.
  • A Flow admin who can manage integrations.
  • A PAT with the scopes and resource access your automation needs.
  • The data.records:write scope to create or update records.
Webhook actions require webhook:manage. Enterprise actions require their own scopes, Airtable plan, and administrator permissions. Check the action’s requirements in Airtable’s Web API documentation. Base access does not grant enterprise access.

​
Provider setup

Create your token in the Airtable developer hub.
1

Create a personal access token.

Give the token a name that identifies its use in Flow.
2

Select the required scopes.

Add data.records:write to create or update records. Add webhook:manage for webhook actions. Select enterprise scopes only for the enterprise actions you need.
3

Select the bases the token can access.

Grant access only to the resources your automation needs. Selecting all resources does not give your account additional permissions.
4

Save the token securely.

Copy the token when Airtable displays it. Enter it only in the connection form.
For enterprise user and group actions, follow Airtable’s System for Cross-domain Identity Management (SCIM) requirements. For administrators of multiple Airtable enterprises, use a service account.

​
Connect in Flow

1

Open Integrations.

Search for Airtable (Personal Access Token). This connection is available to organizations with Preview access.
2

Select Connect.

Name the connection and choose which teams can access it.
3

Enter the personal access token.

Paste the token you created in Airtable.
4

Enable Automations for the intended team.

Open the connection and enable Automations for each team that needs it. Sharing a connection does not enable automations.
5

Select the permitted actions.

Review action access and approval requirements before using the connection in an automation.

​
Capabilities

Use the connection to manage records, enterprise users and groups, webhooks, and audit events. Each action has its own permissions and plan requirements. The enterprise token-revocation action is unavailable.

​
Automation connector reference

The generated Airtable action reference is coming soon. Use Airtable’s Web API documentation for provider action inputs and permissions.

​
Sync and behavior

This connection runs actions when an automation requests them. It does not sync Knowledge or Assets, or receive Airtable webhooks. Airtable checks token validity, scopes, resource access, and account permissions when each action runs. Saving a connection does not confirm permission to run every action. To rotate the token, create a replacement for the same Airtable account and reconnect in Flow. Test the actions your automations need with the replacement before revoking the old token. Revoking or regenerating a token can interrupt automations that use it.

​
Troubleshooting