Overview
Add Airtable to any ModuleX agent or workflow. CRUD against the Airtable REST API (api.airtable.com/v0): base + table discovery via /meta/, record list/get/create/update/delete via /<base>/<table>.
Authentication
Personal Access Token
Authenticate using your Airtable Personal Access Token. Create one at airtable.com/create/tokensRequired Credentials
Available Actions
list_bases — List all Airtable bases accessible with your API token
list_bases — List all Airtable bases accessible with your API token
Response
list_tables — List all tables in a specific Airtable base with their fields and views
list_tables — List all tables in a specific Airtable base with their fields and views
list_records — List records from an Airtable table with optional filtering and sorting
list_records — List records from an Airtable table with optional filtering and sorting
Parameters
100)asc)Response
get_record — Get a specific record from an Airtable table by its ID
get_record — Get a specific record from an Airtable table by its ID
create_records — Create one or more records in an Airtable table. Batched up to 10 per request.
create_records — Create one or more records in an Airtable table. Batched up to 10 per request.
update_records — Update one or more records in an Airtable table. Each record must include `id`; remaining fields can be nested under `fields` or at the top level.
update_records — Update one or more records in an Airtable table. Each record must include `id`; remaining fields can be nested under `fields` or at the top level.
Parameters
false)Response
Limits & Quotas
- Airtable caps batch record operations at 10 records per request;
create/update/delete_recordssplit larger inputs automatically. update_recordsaccepts both shapes per record:{"id": "rec…", "fields": {"X": 1}}(canonical) and{"id": "rec…", "X": 1, "Y": 2}(flat top-level fields). Both normalize to the canonical wire shape internally.delete_recordsuses?records[]=rec1&records[]=rec2query parameters (Airtable’s documented batch-delete contract).- Partial-batch failures surface as
success=False+ the count of records that completed before the error (viaupdated_count/deleted_count).