# Airtable

> Connect Airtable with one sign-in and the apps you build with Vibely can read and write records in your Airtable bases.

Canonical: https://vibely.sh/connectors/airtable
Last updated: 2026-11-18

Read and write records in your Airtable bases.

[How to build an Airtable CRM](https://vibely.sh/blog/how-to-build-an-airtable-crm)

- Made by: [Airtable](https://www.airtable.com)
- Category: Productivity, Databases, Tickets & tasks
- Type: Native connector
- Sign-in: Required
- Works in: Web apps, iOS & Android apps
- Added: October 2026
- Set up in Vibely: [Read the connectors docs](https://docs.vibely.sh/integrations/connectors/catalog)

## Try Airtable

- Build a CRM app on top of my Airtable base
- Create a public directory from an Airtable table
- Add a form that saves submissions to Airtable

## About Airtable

Airtable connects to Vibely with one sign-in. Vibely’s connector gateway keeps the token and refreshes it, and the apps you build reach Airtable through an Edge Function in your project’s Supabase backend, so the project needs Supabase connected. Everyone using an app acts through that one connected account, which suits team tools and internal apps, and writes stay blocked until you set them to Allow in the connector’s settings. It works in web apps and in iOS and Android apps.

## What you can build on Airtable

### A CRM on your base

Deals in a pipeline you drag between stages, contacts and companies linked the way your base links them, and an activity log, all reading and writing the records your team already edits in Airtable.

### Internal tools over a table

Approval queues, request trackers and inventory screens with the forms, filters and roles you want, on records that stay in Airtable.

### Public pages from a table

A catalogue, directory or job board that visitors can open without signing in, by allowing just those reads. Everything else still needs a signed-in user.

### Web and mobile

The same connection works in web apps and in iOS and Android apps built with Expo.

## How it connects

1. **Connect Supabase**: Airtable calls run through an Edge Function in your project’s Supabase backend, so the project needs Supabase connected first.
2. **Sign in to Airtable**: Connect Airtable from Customize → Connectors and approve access to your bases. Vibely asks Airtable to read records, create and update records, and read base schema.
3. **Describe the app**: Name the base and its tables, and say who uses the app and what they need to do. The agent writes the Edge Function and an airtableFetch helper, then builds the screens on your real fields.
4. **Allow writes before you publish**: A published app has nobody to approve an action, so creating or updating records stays blocked until you set the connector’s writes to Allow in the project’s connector settings.

## What you should know first

### One shared Airtable account

The app acts as the account that connected Airtable, and everyone who uses the app reads and writes through it. That suits a team tool. It does not give each user their own Airtable access.

### Signed-in users by default

The Edge Function refuses callers without a session, so Airtable data sits behind your app’s sign-in unless you allow specific reads for public pages.

### Your data stays in Airtable

Vibely does not copy your base. The app reads and writes through the Airtable API, so a change made in Airtable and a change made in the app are the same record.

### The token stays with Vibely

Vibely’s connector gateway keeps the Airtable token and refreshes it. Your project holds only a gateway key, as an Edge Function secret.

## Permissions

What Vibely asks for when you connect Airtable.

- Read records
- Create and update records
- Read base schema

## Related connectors

- [Asana](https://vibely.sh/connectors/asana) - Create, update and report on Asana tasks, projects, sections and assignees.
- [Notion](https://vibely.sh/connectors/notion) - Read docs, specs and PRDs as context while building.
- [Algolia](https://vibely.sh/connectors/algolia) - Instant, typo-tolerant search: index records from an Edge Function and search them from the app.
