Airtable

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: data.records:read, data.records:write, schema.bases:read, schema.bases:write.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
AIRTABLE_CLIENT_IDYesAirtable OAuth Client ID (from your OAuth integration) Docs.
AIRTABLE_CLIENT_SECRETYesAirtable OAuth Client Secret Docs.

Setup

  1. Choose who owns the Airtable OAuth app: On hosted Veryfront, Airtable uses the Veryfront-managed Airtable OAuth app: connect Airtable from the project's integrations and approve the Airtable consent screen, no environment variables needed. Set AIRTABLE_CLIENT_ID and AIRTABLE_CLIENT_SECRET only to use your own Airtable OAuth app, which is required for local and self-hosted runs.
  2. Register an OAuth integration: In Airtable, register a new OAuth integration.
  3. Set the redirect URL, scopes and secret: Add the scopes data.records:read, data.records:write, schema.bases:read and schema.bases:write. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/airtable for hosted Veryfront, or your app origin followed by /api/auth/airtable/callback for a local or self-hosted app. Generate a client secret, because the token exchange runs on a server. Set AIRTABLE_CLIENT_ID and AIRTABLE_CLIENT_SECRET from the app's credentials.
  4. Verify access: Run List Bases (read-only). It returns the bases the user shared during consent without changing them.

Provider notes

  • The connection requests data.records:read, data.records:write, schema.bases:read and schema.bases:write.
  • During consent the user picks which bases and workspaces the connection can reach; the tools see nothing else.
  • Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.

Provider API reference.

Tools

ToolAccessDescription
List Bases<br /><code className="reference-identifier">airtable__list_bases</code>ReadList bases
Get Base<br /><code className="reference-identifier">airtable__get_base</code>ReadGet base
List Records<br /><code className="reference-identifier">airtable__list_records</code>ReadList records
Get Record<br /><code className="reference-identifier">airtable__get_record</code>ReadGet record
Create Record<br /><code className="reference-identifier">airtable__create_record</code>WriteCreate record
Create Records<br /><code className="reference-identifier">airtable__create_records</code>WriteCreate records
Update Record<br /><code className="reference-identifier">airtable__update_record</code>WriteUpdate record
Delete Record<br /><code className="reference-identifier">airtable__delete_record</code>WriteDelete record
Create Table<br /><code className="reference-identifier">airtable__create_table</code>WriteCreate table
Update Table<br /><code className="reference-identifier">airtable__update_table</code>WriteUpdate table
Create Field<br /><code className="reference-identifier">airtable__create_field</code>WriteCreate field

Verify the connection

Call a read tool such as airtable__list_bases with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.