Airtable for Meta Muse
Community draft proposes: List accessible Airtable bases, read table records, and propose adding records with an appropriately scoped personal access token.
Guide description: The pinned community skill proposes listing Airtable bases, reading records from a specified table, and creating records with supplied fields. Each action depends on the token's scopes and base grants plus the token owner's underlying permissions; the base-list check does not verify table reads or writes.
Community draft. OpenTools has not verified a Muse installation or provider API result. An Airtable personal access token needs `schema.bases:read` to list bases, `data.records:read` to read records, and `data.records:write` to create records, plus access to each selected base and a user role that permits the action. A successful base list does not establish read or write access to a table.
View original source ↗How to set it up
Paste a promptDraft — these instructions come from the linked source and have not been independently live-tested by OpenTools.
Source maturity: 🧪 Draft: written from Airtable's public Web API docs; not yet live-tested end-to-end.
Before you start
- Personal access token with `schema.bases:read`, `data.records:read`, and `data.records:write`, access to the selected bases, and an Airtable user role that permits the intended action
Steps
- Review the pinned connectors/airtable/SKILL.md and its Files list (SKILL.md, bin/airtable.py).
- Create a personal access token with `schema.bases:read`, `data.records:read`, and `data.records:write` for the proposed actions; grant the specific bases and confirm your Airtable role permits record creation. Provide the token only through Muse’s secure flow if available.
- Ask Muse to fetch the pinned skill and its exact listed files. Treat this as an upstream proposed installation, not a verified one-click setup.
- Run the source status check `bin/airtable.py bases`; inspect the bases returned. This checks token authentication and visible bases only, not table read or record creation access.
Prompt to paste into Muse
Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/airtable/SKILL.md Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.
Account access: personal access token via the secure credential flow (`credentials.request_api_access`): create one at airtable.com/create/tokens with scopes `data.records:read`, `data.records:write`, and `schema.bases:read`, and grant it access to the bases you want to use
Allowed hosts: api.airtable.com
Source status check: `bin/airtable.py bases` lists bases visible to the token; success does not verify table read or record creation access
A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.
Services it connects with
These are the services the connector uses.
Airtable