Connect your app to Airtable
Airtable combines a spreadsheet interface with a database. Connect it to Mythos when your team already keeps its working data in Airtable and needs a more focused interface: a catalog, an operations dashboard, a submission form, or a customer portal.
You can use the connection in the project chat while building and in the app you publish. See Connections in Mythos for how connection access and project links work.
With the Airtable connector, you can:
- Explore available bases and the tables, fields, and views inside them.
- Read, filter, sort, create, update, and delete records.
- Work with record comments.
- Create bases, tables, and fields when your Airtable permissions allow it.
The connection uses an Airtable personal access token, or PAT. Its scopes, selected bases, and the token owner’s Airtable permissions determine what is accessible. Connecting a token does not expand that access.
Examples to build
These prompts describe apps Mythos can build around your Airtable data. Connecting Airtable makes the data available; ask Mythos to create the interface and behavior you need.
Connect Airtable to Mythos
You need permission to create connections in your Mythos workspace. If an appropriate saved Airtable connection is already available to you, open it and link it to your project instead of setting up another token.
Before you start
Have an Airtable account with access to the intended bases and a PAT for the actions your app needs. API usage is subject to your Airtable plan and rate limits. Your Airtable subscription and charges remain with Airtable.
1. Create a personal access token
- Open Airtable’s personal access tokens page and choose Create new token.
- Give it a recognizable name, such as
Mythos inventory. - Select the scopes your app needs. For a dashboard, start with record and schema reads. Add write scopes only for the changes you want to support.
- Under Access, select the bases the app should use.
- Create the token and copy its value to a secure place.
Record comments need their own comment permissions. A token also needs access to the particular base: granting a scope alone is not enough.
For the complete scope and resource controls, see Airtable’s personal access token guide.
2. Save the connection
- From the Dashboard, open Connectors and select Airtable. If no saved connection is available, the setup form opens.
- Enter a Display name, such as
Inventory base. - Paste your token into Personal access token. Keep it out of chat messages and public files.
- Under Sharing, keep Private or select Share with others. You can give selected workspace members access, or choose Share with workspace.
- Click Connect Airtable. Mythos checks the token before saving it.
To use it in an app, open Chat actions (+) → Project connectors in your project. Select the saved connection and click Use in this project. Then describe the app you want to build.
Work with your bases and records
Start with the base and table names, the fields that matter, and whether people should be able to edit them. For example:
Use the Products table in my Inventory base. Show Name, Category, Price, and Stock. Customers can browse; only signed-in staff can change Stock.
This tells Mythos both what data to use and what access rules the app needs. Sharing an Airtable connection with a workspace member does not create customer login or record-level access rules in your published app.
If a table is missing, check the token’s base access and schema.bases:read scope. If records appear but an edit fails, check data.records:write and the Airtable permissions of the user who created the token. A successful connection check confirms the token, not access to every base or every action.
Limitations
- Each connection uses one PAT. App visitors do not sign in to their own Airtable accounts through it.
- Airtable’s rate and plan limits still apply. Large tables need pagination, and frequent updates should avoid repeatedly loading an entire base.
- Connecting Airtable does not install an automatic change listener. Ask for periodic refreshes when the app needs updated data; creating a new Airtable webhook is not available through this connector.
- Airtable Automations and scripting extensions are separate from the record and schema actions described here.
- PATs do not refresh automatically. If a token is revoked or its access changes, update the connection with a working token.
Manage the connection
Open Connectors → Airtable, then your saved connection. Linked projects → Unlink projects removes access from selected projects while keeping the connection. Disconnect stops Mythos from using the connection; your Airtable bases and records remain in Airtable.
If the token is replaced or revoked, disconnect the old connection and connect Airtable again with the new token. Link the new connection to the intended projects, ask Mythos to set up the Airtable features again, and publish the update. Features using the disconnected connection stop working until they are set up again.