Skip to main content

Airtable Token API Credentials

Airtable Token API credentials allow your SubverseAI agents to authenticate with Airtable using personal access tokens for direct API access.

Overview

Airtable Token credentials provide access to:
  • Direct API access with personal tokens
  • Simplified authentication flow
  • Personal workspace integration
  • High-frequency operations
  • Development and testing workflows

Dashboard Screenshot

Airtable Developer Hub Create personal access tokens in the Airtable Developer Hub

Steps to Create Airtable Token API Credentials

1. Create Airtable Account

  1. Visit Airtable
  2. Sign up or sign in to your account
  3. Create or select a workspace

2. Generate Personal Access Token

  1. Navigate to the Developer Hub
  2. Click Create new token
  3. Enter token details:
    • Name: Descriptive name (e.g., “SubverseAI Token Integration”)
    • Scopes: Select required permissions:
      • data.records:read - Read records
      • data.records:write - Create/update/delete records
      • data.bases:read - Read base information
      • schema.bases:read - Read base schema
  4. Select workspaces to grant access to
  5. Click Create token
  6. Copy the token immediately - it won’t be shown again

3. Get Base Information

  1. Open your Airtable base
  2. From the URL, copy the Base ID
  3. Note the Table IDs for tables you want to access

4. Add to SubverseAI

  1. Go to Credentials in your SubverseAI dashboard
  2. Click Create New Credential
  3. Select Airtable Token API from the credential types
  4. Enter a name for your credential
  5. Fill in the required fields:
    • Personal Access Token: Your Airtable token (starts with pat)
    • Base ID (optional): Default base ID for operations
  6. Click Test Connection to verify the credentials work
  7. Click Save Credential

Required Fields

  • Name: A descriptive name for your credential
  • Personal Access Token: Your Airtable personal access token
  • Base ID (optional): Default base ID for operations

Usage Tips

  • Use specific scopes to limit token permissions
  • Create separate tokens for different environments
  • Regularly rotate your access tokens
  • Use base and table IDs rather than names for reliability

Troubleshooting

Invalid Token: Ensure you copied the complete token including the pat prefix Permission Denied: Check that your token has the required scopes and workspace access Base Not Found: Verify the Base ID is correct and you have access to that base Rate Limit Exceeded: Airtable has API rate limits - implement retry logic

Next Steps

After creating your Airtable Token credentials:
  • Set up direct API integration workflows
  • Configure high-frequency data operations
  • Build real-time data synchronization
  • Monitor API usage and performance
  • Implement token rotation procedures