Skip to main content

Connect Airtable to Claude Cowork

Give Claude Cowork governed access to Airtable’s 46 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Airtable to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.

  1. 1

    Approve Airtable in Runlayer

    Add Airtable from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Airtable’s 46 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to Airtable

    Each user signs in to Airtable with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Airtable from Claude Cowork

    Airtable’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.

Tools

46 Airtable tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork users can call. 6 read data only and 1 can change or delete data.

  • Analyze table

    Run statistical operations (count, sum, average, min, max, etc.) on an Airtable table, optionally grouped by columns and filtered.

  • Create automation

    Creates and validates one automation in a base: a trigger plus ordered nodes — action nodes, repeatingGroup (run inner nodes once per item), and conditionalGroup (if/else-if/else branches).

  • Create base

    Creates a new Airtable base with the specified tables and fields.

  • Create field

    Creates a new field in an existing Airtable table.

  • Create interface

    Creates a new interface within a base.

  • Create page

    Creates a new page.

  • Create record comment

    Creates a comment on a specific Airtable record.

  • Create records for table

    Creates new records in an Airtable table.

See all 46 Airtable tools

Control

What Runlayer can see and stop in Claude Cowork

Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.

  • Gateway policy (available)

    Every Airtable call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination