Airtable Toolkit
The Airtable toolkit lets agents manage records in Airtable bases and tables: create, find, update, delete, upload attachments, and call the Airtable REST API for operations without a dedicated tool.
Add it on the agent Toolkits tab, connect a Personal Access Token (PAT), then reference tools with @ in the personality prompt.
Prerequisites
- An Airtable account
- A Personal Access Token from airtable.com/create/tokens
- Recommended scopes:
data.records:read,data.records:write, andschema.bases:read(schema scope helps field discovery and type coercion) - Token access granted to the bases the agent should use
- An agent you can edit
Setup
- Create a PAT in Airtable with the scopes and base access you need.
- Open the agent → Toolkits → add Airtable.
- Create or select a connection and paste the PAT.
- Save,
@-mention Airtable tools in the personality prompt, and test with a known base and table ID.
Available tools
| Tool | Description |
|---|---|
| Create Record | Adds a record. Provide base ID, table ID or name, and fields (JSON). Typecast is on by default when schema is available. |
| Find Record | Finds records with an Airtable formula or a simple field/value match. Optional view and max records (page size up to 100). |
| Update Record | Updates a record by ID. Empty or null field values clear that field. |
| Delete Record | Deletes a record by ID. |
| Upload File to Column | Attaches a file to an attachment field via public URL or base64 content. |
| Custom API Call | Authenticated request to an Airtable REST endpoint not covered by a dedicated tool. |
Use cases
- Log support tickets or lead notes into a shared Airtable base from chat
- Look up a record by email or ticket ID before updating status
- Attach a generated file or screenshot to an existing row
- Call a niche Airtable endpoint through Custom API Call when no dedicated tool fits
Tips
- Grant the PAT only the bases the agent needs.
- Include
schema.bases:readso field types coerce correctly (checkboxes, numbers, multi-select, and similar). - Prefer base and table IDs from the Airtable UI when names are ambiguous.
- On Update Record, empty values clear fields — omit fields you want to leave unchanged.
- Do not put the PAT in prompts, logs, or shared screenshots.
Troubleshooting
| Symptom | What to check |
|---|---|
| 401 / invalid token | Regenerate the PAT and update the EKB connection |
| 403 on schema or fields | Add schema.bases:read (and record scopes) to the token |
| Cannot see a base | Confirm the PAT’s base access includes that base |
| Find returns nothing | Check formula syntax, table name/ID, and view filter |
| Custom API Call blocked | Use Airtable HTTPS hosts only; do not override Authorization headers |