Skip to main content

​
Pre-Built Tooling

CategoryDetails
AuthenticationOAuth 2.0 (Authorization Code with PKCE and refresh tokens) or Personal Access Token (Bearer)
Two-Way SyncYes
Events SupportedYes (Webhooks)
RealtimeYes
Supports Rate LimitingYes (5 requests per second per base)
Authentication Scopes Supporteddata.records:read (read records), data.records:write (write and delete records), data.recordComments:read (see comments), data.recordComments:write (create, edit, and delete comments), schema.bases:read (read schema), schema.bases:write (edit base structure), webhook:manage (manage webhooks), user.email:read (read user email)

​
Objects Supported

Alloy Automation supports syncing the following objects from Airtable:
  • Bases
  • Tables
  • Records
  • Fields
  • Views
  • Users
  • Webhooks
  • Attachments

​
Set Up Guide

​
Trial Access

QuestionAnswer
Offers free trial?Yes. Airtable offers a free tier with limited records and features. Sign up at https://airtable.com to test the integration.
Requires requires paid sandboxNo paid sandbox required.
Requires partnership to obtain authentication?No. OAuth 2.0 credentials and Personal Access Tokens can be obtained directly through your Airtable account settings.

​
Authentication (OAuth 2.0 or Personal Access Token)

For customers who want to completely whitelabel their OAuth experience, you can provide your own developer keys instead of using Alloy Automation’s.
  1. Go to Airtable Developer Hub (https://airtable.com/create/oauth) and create a new OAuth integration.
  2. Configure your OAuth application:
  3. Copy your Client ID and Client Secret.
  4. Enter your Client ID and Client Secret into Alloy Automation.

​
Option 2: Personal Access Token (PAT)

  1. Log in to your Airtable account and go to Account Settings.
  2. Navigate to the Developer section and click Generate token.
  3. Select the scopes and bases your token should have access to.
  4. Copy the generated Personal Access Token.
  5. Enter the token into Alloy Automation as a Bearer token.

​
PKCE Support

Airtable’s OAuth 2.0 implementation uses PKCE (Proof Key for Code Exchange) for enhanced security. Alloy Automation handles this automatically during the OAuth flow.

​
Scopes

Airtable uses granular scopes for different operations:
  • data.records:read and data.records:write for record operations
  • schema.bases:read and schema.bases:write for schema operations
  • webhook:manage for webhook operations
  • Additional scopes for comments and user information

​
Use Cases

​
1) Project management sync

Sync project data, tasks, and status updates between Airtable and other project management tools, keeping teams aligned across multiple platforms without manual data entry.

​
2) Customer data aggregation

Collect customer information from various sources and consolidate it into Airtable bases, creating a centralized customer database that’s accessible to your entire team.

​
3) Webhook-driven automation

Set up real-time triggers that respond to changes in Airtable records—such as new leads, status updates, or form submissions—and automatically initiate workflows in other systems.

​
4) Dynamic schema management

Programmatically create and modify Airtable base structures based on changing business needs, enabling flexible data models that adapt to your workflows.

​
5) Content and asset management

Use Airtable as a content repository with attachment support, syncing files and metadata across your content creation and publishing pipeline.

​
API Gotchas

  • ⚠️ Rate limiting: Airtable enforces a rate limit of 5 requests per second per base. Implement request queuing and backoff strategies to avoid hitting limits.
  • ⚠️ Webhook expiration: Airtable webhooks expire after 7 days of inactivity, Alloy Automation handles this logic behind the scenes.
  • ⚠️ Field ID vs. Field Name: When working with records, you can reference fields by name or ID. Field IDs are more stable as names can change.
For questions or troubleshooting, contact support@runalloy.com.
⌘I