Steps

Authenticate with a Personal Access Token scoped minimally to the needed permissions (e.g., data.records:read, data.records:write) -- legacy API keys are deprecated and no longer issued.
List or filter calendar records with GET https://api.airtable.com/v0/{baseId}/{tableNameOrId}, using formula or view parameters to scope to a given time period.
Create new entries (e.g., scheduled posts) with POST to the same endpoint, sending fields as a JSON object matching the base's column schema.
Update status fields (e.g., moving a piece from Draft to Published) with PATCH requests targeting specific record IDs.
Check the base's own generated API documentation (unique per base) at airtable.com/developers/web/api for the exact field names and types in your editorial calendar base.

Known gotchas

Field names and options (e.g., single-select values) are base-specific -- the generic Airtable API docs won't show your table's actual schema; always pull the base-specific docs.
Personal Access Token scopes are enforced strictly -- a token missing data.records:write will fail on create/update calls even if read access works fine.

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Manage an editorial calendar's records programmatically with the Airtable API

Steps

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?