productivity
Airtable CLI for CI
Use the Airtable CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 6 read 1 write Manual OAuth token auth
Airtable CLI for CI
Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.
Use this shape when a pipeline needs to read or update an external service. The Airtable CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Airtable CLI for CI
kosmokrator integrations:configure airtable --set access_token="$AIRTABLE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call airtable.airtable_list_bases '{}' --json Discovery Before Execution
Agents and scripts can inspect Airtable docs and schemas before choosing a function.
kosmo integrations:docs airtable --json
kosmo integrations:docs airtable.airtable_list_bases --json
kosmo integrations:schema airtable.airtable_list_bases --json
kosmo integrations:search "Airtable" --json
kosmo integrations:list --json Useful Airtable CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
airtable.airtable_list_bases | Read | none | List all Airtable bases the token has access to. |
airtable.airtable_get_base | Read | base_id | Get details for a single Airtable base by ID. |
airtable.airtable_list_records | Read | base_id, table, view, filter_by_formula, max_records, offset, fields, sort | List records from an Airtable table with optional filtering, sorting, and pagination. |
airtable.airtable_get_record | Read | base_id, table, record_id | Get a single Airtable record by ID. |
airtable.airtable_create_record | Write | base_id, table, fields | Create a new record in an Airtable table. |
airtable.airtable_list_views | Read | base_id | List views for an Airtable base. |
airtable.airtable_get_current_user | Read | none | Get the profile of the currently authenticated Airtable user. Useful for verifying credentials and displaying account information. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.