# Run agents with Airtable

Airtable AI agents on Rush: connect Airtable once, then name it on any run. The agent works in its own cloud computer, with a record of every run.

[Connect Airtable](https://cloud.getrush.ai/console/settings/?section=connections) in the console under Settings → Connections.

## What an agent can do in Airtable

Work with Airtable bases: find bases, read, create and update records, add comments, create tables and fields, and build interfaces and automations.

## Jobs on Rush that use Airtable

- [Which Donors Gave Last Year but Not This Year? A Fundraising App's Monthly Airtable Check for Each Nonprofit](https://getrush.ai/run/find-lapsed-donors/airtable/)
- [Flag Products in Each Online Store's Airtable Catalog That Are Not Ready to List](https://getrush.ai/run/flag-incomplete-product-listings/airtable/)
- [Flag Loads at Risk of Missing Delivery in a Freight Broker's Airtable](https://getrush.ai/run/flag-late-loads/airtable/)
- [How Does a Property Manager Triage Each Morning's Maintenance Requests in Airtable?](https://getrush.ai/run/triage-maintenance-requests-each-morning/airtable/)

## How Airtable connects

Airtable is a remote MCP server, published by Airtable, at `https://mcp.airtable.com/mcp`. Connecting it signs in through the MCP OAuth flow on Airtable's side.

From Airtable: [Airtable's MCP documentation](https://airtable.com/developers/agents/mcp/getting-started).

Connect it once in the console under Settings → Connections, or from your server with `POST /me/connections`. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names `airtable` in `connections`, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

```http
POST https://api.phoenix.so/me/connections

{
  "type": "mcp",
  "name": "Airtable",
  "url": "https://mcp.airtable.com/mcp"
}
```

## Whose Airtable account the agent uses

Your Airtable connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Airtable, and a run started with an API key uses the Airtable of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link `POST /o/{org}/agents/{agent}/connections` returns. They sign in to their own Airtable, and that agent's runs use their account and nothing else: never yours, never another user's.

## More Productivity integrations

- [Gmail](https://getrush.ai/integrations/gmail/)
- [Google Calendar](https://getrush.ai/integrations/google-calendar/)
- [Google Drive](https://getrush.ai/integrations/google-drive/)
- [Outlook](https://getrush.ai/integrations/outlook/)
- [Microsoft Calendar](https://getrush.ai/integrations/microsoft-calendar/)
- [OneDrive](https://getrush.ai/integrations/onedrive/)
- [Notion](https://getrush.ai/integrations/notion/)

## Frequently asked questions

### How do I connect Airtable to Rush?

Open Settings → Connections in the console and connect Airtable, or send `POST /me/connections` with `{"type":"mcp","name":"Airtable","url":"https://mcp.airtable.com/mcp"}` and open the `authorize_url` it returns while signed in to the console. The connection reads `pending` until the sign-in finishes, then `connected`.

### Does every run get my Airtable account?

No. A run gets your Airtable connection only when it names it in `connections` (`"connections": ["airtable"]`), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

### What can an agent do in Airtable?

Work with Airtable bases: find bases, read, create and update records, add comments, create tables and fields, and build interfaces and automations. 4 published jobs use it; this page lists them.

### Can my app's users connect their own Airtable?

Yes. Make each user an agent from your template, and they sign in to their own Airtable through the link `POST /o/{org}/agents/{agent}/connections` returns. That agent's runs use their account alone.

## Keep reading

- [AI agents for operations teams: every job and app for them](https://getrush.ai/solutions/operations/)
- [How connections work: sign in once, then every run that names a connection gets it](https://getrush.ai/docs/concepts/connections/)
- [Start your first run from the developer API quickstart](https://getrush.ai/docs/quickstart/)
- [Pricing: one price per member, hours shared by the team](https://getrush.ai/pricing/)
- [How Rush compares with other cloud agents](https://getrush.ai/compare/)
- [Every app and MCP server Rush connects to](https://getrush.ai/integrations/)
