Skip to main content

Connect Airtable to GitHub Copilot

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

Set up

Add Airtable to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot 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 GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Airtable’s 46 tools through the plugin’s search and execute tools.

    GitHub Copilot 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 GitHub Copilot

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

Tools

46 Airtable tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot 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 GitHub Copilot

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination