Airtable is where a lot of operational truth lives: project trackers, content calendars, CRM-style tables, launch checklists, and internal workflows. That makes it a strong fit for an AI assistant that helps teams look up records, summarise views, spot stale work, and turn base activity into clear Slack updates without digging through filters and linked fields all day. If you are running OpenClaw yourself, Airtable is still a relatively approachable integration to wire up, but Cody is the faster path if you want the assistant experience instead of the API glue.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Airtable — it's considerably more involved.
Connecting OpenClaw with Airtable: Step by Step
Step 1: Create a Personal Access Token
Go to airtable.com/create/tokens and create a token. Select the scopes you need (data.records:read at minimum) and the specific bases you want the token to access. Airtable tokens are scoped to specific bases rather than your whole workspace.
Step 2: Get Your Base and Table IDs
Each Airtable base and table has a unique ID (found in the URL when viewing a base). Your proxy needs these to construct API requests. Document them in your skill file — e.g., Content Calendar base ID: appXXXXXXXX, Posts table: tblXXXXXXXX.
Step 3: Build the Proxy and Skill File
The Airtable API endpoint is https://api.airtable.com/v0/{baseId}/{tableIdOrName}. It supports filterByFormula for querying specific records. Write ~/.openclaw/skills/airtable.md with base and table names, their IDs, and the key field names Claude needs to know to filter and sort records correctly.
Challenges and Caveats
Formula Syntax Is Airtable-Specific
Airtable's filterByFormula parameter uses Airtable formula syntax — similar to Excel but with quirks. Claude can generate these, but they may need correction. Common issue: field names with spaces must be wrapped in curly braces ({Field Name}).
Pagination with Offset Tokens
Airtable returns a maximum of 100 records per request. For large tables, results are paginated with an offset token. Your proxy needs to handle multi-page retrieval for summarisation queries.
Skip All of This — Use Cody Instead
Cody gives your team an Airtable assistant in Slack, so people can search bases, summarise records, spot stale or missing updates, and draft tracker summaries without managing tokens, formula syntax, or Airtable API plumbing.
Related Guides
- Connecting OpenClaw with Google Sheets: A Practical Guide
- Connecting OpenClaw with Notion: A Practical Guide
- Connecting OpenClaw with Asana: A Practical Guide
Need the model-flexible version? See: How to Connect Airtable to OpenClaw: Setup, Models, and Workflow Guide.