Airtable integration (in development)
The Airtable integration — turning it on, connecting an account with a personal access token, browsing bases and records from the sidebar, the CLI routes an agent uses, and the inbox and workflow notifications it raises.
On this page
What it is
An API integration that connects Omniscio to your Airtable workspace. Browse bases, view tables and records, search, comment on records, and receive inbox notifications for record changes — all from within Omniscio. Agents can interact with Airtable via CLI routes.
Where to find it
Status
In-development (unreleased). Enable: turn on Airtable in Settings → Lab (airtableEnabled), or set AMC_SHOW_AIRTABLE=1.
How to use it
- Enable the Airtable feature (Settings > Dev Features or
AMC_SHOW_AIRTABLE=1) - Connect your account: Settings → API Integrations → Airtable. Create a personal access token at airtable.com/create/tokens with scopes:
data.records:read,data.recordComments:read,schema.bases:read - Open the Airtable tab in the sidebar to browse your bases and records
How it behaves
Inbox source
airtable-inbox — Polls every ~10 minutes for recently-updated records. Enable via Settings → Features → Airtable > Inbox toggle. Kill switch: AMC_DISABLE_AIRTABLE_INBOX_POLL=1.
Troubleshooting
Each message below is the exact copy the app shows.
- "Connect Airtable in Settings > Optional Features > Airtable connection first." — no token is saved yet. Airtable's board panel is still in development, so connect from Settings → API Integrations → Airtable and paste the token there (the message's "Optional Features" is that section's older name).
- "Check your Airtable API token in Settings > Optional Features > Airtable." —
the token was refused (a 401 or 403), usually because it expired, was revoked, or
lacks a scope. Create one at airtable.com/create/tokens with
data.records:readandschema.bases:read, then re-enter it with Fix connection. - "Airtable is rate-limiting requests — wait a moment and try again." — the integration retries automatically; Airtable allows 5 requests per second per base, so a burst of edits is the usual cause.
- "Airtable rejected the request (HTTP 404) — check the connection's settings and try again." — the base ID is wrong or the token cannot see that base.
- "Couldn't reach Airtable — check your connection and try again." — the request never got an answer: offline, a proxy, or an Airtable outage.
- "Something went wrong talking to Airtable. Please try again." — the catch-all for any other response. Nothing was changed; retry.
Related
Other integrations that work the same way include Asana board, and every one of them stores its account token the way Automation credentials describes. If you are wiring an agent to a service yourself, Agent tools covers the same command-line route pattern.
Last verified 2026-10-06