Airtable

Airtable is a connector: it links a MeDo app to one Airtable account, so the app can list the bases it can reach, inspect a base's tables and fields, browse and filter records, and create, update, or delete records in reviewed batches. It works with records, not with the base's structure.

#What you can build

• A records dashboard. Choose a base and table, see the real fields and records, and load another page when needed.
• A data-entry form. Validate the supported fields and preview the record before submitting it to an existing table.
• A content tracker. Group returned records by an existing status field and review a status change before saving it.
• An approved directory. Publish selected fields from a table you approve for sharing, behind a focused search interface.

Airtable fits when a team already runs on a base and needs a purpose-built front end for one table — intake, review queues, directories, light CRM. It is not a schema editor, see Limits.

#Build examples

Copy one of these into the prompt box. The first one is the smallest useful starting point.

Use @Airtable to build a private records dashboard where I choose an Airtable base and table, see its real fields and records, and load another page when needed.

Use @Airtable to build a data-entry form for an existing Airtable table that validates supported fields and previews the record before I submit it.

Use @Airtable to build a private content tracker that groups returned records by an existing status field and lets me review a status change before saving.

Use @Airtable to build a directory from an Airtable table I approve for sharing, exposing only selected fields and a focused search interface.

#Prepare and connect

You need an Airtable account that can already open the base the app should use, and the app needs access to that base when you connect.

1. Open Skills & Connectors in the sidebar and search for Airtable.
2. Open the card and click Connect.
3. Sign in to Airtable and approve the access MeDo asks for, including the bases the app needs.
4. The button changes to Connected.

Then tell MeDo which base and table to use, or let the app list the bases it can see and offer a picker.

If you start building before connecting, MeDo shows an Airtable connection button under its reply. You can connect there instead.

#Use it in your app

• The app uses your connected account, not each visitor's Airtable login. Everyone who opens the dashboard sees the same base. Keep private records and editing controls behind your app's own sign-in and limited to the intended people.
• Pick the table explicitly. A base often holds several tables, and the app needs to know which one it is reading and writing.
• Match the real schema. Ask the app to read the table's fields first and then build the form around them; that avoids columns that do not exist.
• Record lists are pages. Ask for a bounded page, the fields you actually need, and a load-more control.
• Writes are confirmed first. MeDo previews creates and updates, and deletes only the records you confirmed.
• App notes stay in the app. Review status, assignments, and internal comments belong in your app's own tables, keyed to the real record.

#Limits and troubleshooting

"Connection required" appears in the app. Ask the app owner to open the connector card and click Connect, then reload.

A base or table is missing from the picker. The connection only sees bases the account granted. Reconnect and include the base, or check the account's access in Airtable.

A field is rejected when saving. Only the supported field types can be written. Attachments, linked-record objects, and long lists are not. Read the table's fields first and use a plain value.

A record change did not appear. Writes are not retried automatically. Open the base, confirm what actually changed, and only then repeat the edit.

A delete asks for confirmation. Deletion removes the record permanently. MeDo confirms the exact records first.

#Related

• Connector catalog — the other connectors and what they are for.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing access & roles — restrict who can read and change connected data.