Skip to main content
Data Fetcher needs to access your Airtable data when you’re not using the extension to schedule runs, use triggers, or webhook URLs. You’ll need to authorize Data Fetcher in the extension using either OAuth or a personal access token (PAT). You only need to do this once, as Data Fetcher will securely store your authentication details.
Your Data Fetcher workspace uses a single authorization (whether through OAuth or PAT) to access all your Airtable bases. So you need to give it access to every base you want to run scheduled / webhook URL / triggers in.
OAuth connections can occasionally be flaky due to token expiration or Airtable API instability, while personal access tokens tend to be more reliable for consistent long-term access to your Airtable data.

​
Authorize with OAuth

  1. Hover over the Data Fetcher extension, then click the settings icon (⚙️).
  2. Make sure the correct workspace is selected in the top-left dropdown.
  3. Click the Airtable access section on the left-hand menu.
  4. Under OAuth Connection, click + Authorize.
  5. On the modal that opens, click I understand, let’s authorize.
  6. A new tab/window will open - select + Add all resources to avoid access issues in the future.
  7. Click Grant access.
  8. Back in the Data Fetcher extension, you should see Connected under Airtable OAuth Connection.

​
Authorize with a personal access token (PAT)

  1. Go to Airtable’s token creation page.
  2. Create a new token with access to all bases and these scopes:
    • data.records:read
    • data.records:write
    • schema.bases:read
    • webhook:manage
  3. Hover over the Data Fetcher extension, then click the settings icon (⚙️).
  4. Make sure the correct workspace is selected in the top-left dropdown.
  5. Click the Airtable access section on the left-hand menu.
  6. Under Personal Access Token (PAT), click + Add.
  7. Paste in your Airtable personal access token.
  8. Click Save.
Your Airtable PAT will be saved in your Data Fetcher workspace.

​
Important: PAT takes precedence

If both OAuth and a PAT are configured for a workspace, Data Fetcher will always use the PAT for authentication. This means:
  • If you want to use OAuth, make sure no PAT is configured
  • If you want to switch from PAT to OAuth, you’ll need to remove the PAT first
To remove a PAT, go to workspace settings and click the delete icon (🗑️) next to it.