Skip to main content
This guide walks you through obtaining all required credentials for the Airtable plugin.

Authentication Method

The Airtable plugin uses API key authentication.
  • api_key (default) — Personal access token (PAT) for the REST API

API Key (Personal Access Token)

Step 1: Create a Personal Access Token

  1. Open Airtable token management (or AccountDeveloper hubPersonal access tokens).
  2. Click Create token.
  3. Give the token a name (for example, Corsair).
  4. Add access to the bases (and scopes) your integration needs — at minimum, the bases you plan to read or write.
  5. Under Scopes, include the data permissions required by your workflows (for example, data.records:read, data.records:write, schema.bases:read).
  6. Create the token and copy it immediately. You will not see it again.
Storing credentials:
pnpm corsair setup --plugin=airtable api_key=patXXXXXXXX
Verify:
pnpm corsair auth --plugin=airtable --credentials

Webhook Signing Secret

When you configure a webhook in Airtable for a base, the provider gives you a signing secret used to verify incoming payloads.
  1. In Airtable, open the base → Automations or Extensions flow that posts to your webhook (per your Airtable webhook setup).
  2. Copy the webhook signing secret (or MAC secret) shown for that destination.
  3. Store it with Corsair so processWebhook can verify signatures.
Storing credentials:
pnpm corsair setup --plugin=airtable webhook_signature=your-signing-secret

Required Credentials Summary

CredentialRequired forWhere to find
Personal access tokenapi_key authcreate/tokens
Webhook signing secretWebhooksAirtable webhook / automation configuration for your base
For general information about how Corsair handles authentication, see Authentication.