Monday

Monday.com models work as boards containing items (rows) with typed columns — a flexible but complex data model. For agents, the GraphQL API at api.monday.com/v2 provides access to boards, items, columns, groups, updates (comments), and workspaces. The column-type system (status, date, person, text, number, timeline, etc.) enables rich structured data but means agents must understand column semantics to write items correctly. Automations can trigger webhook events. The platform's flexibility means the same Monday.com instance can model project management, CRM, inventory, or any tabular workflow — agents must adapt to the specific board structure they're working with. Rate limits are complexity-based, similar to Linear's model.

Personal API tokens (generated in Administration → Developer → My Access Tokens) provide full account access via Authorization header. OAuth 2.0 is available for marketplace apps with scoped permissions. Token permissions inherit the user's role — admin tokens have full access, member tokens are restricted. No fine-grained scoping on personal tokens. API tokens do not expire. OAuth scopes include boards:read, boards:write, and workspace:read. For agents, personal tokens are the fast path for internal integration. The OAuth flow requires registering an app in the Monday.com marketplace developer portal. Webhook payload signing is available for verification. No IP-based access restrictions at the API level.

Developer documentation at developer.monday.com is comprehensive, covering the GraphQL API, webhooks, OAuth, and the app framework for building marketplace apps. The API playground provides interactive query building with schema exploration. Column type documentation details the value format for each type — essential reading for agents writing to boards. The Monday Apps framework enables building UI integrations that render within Monday.com. SDK support: official client for JavaScript, community libraries for Python and Ruby. Video tutorials complement the written docs. The main documentation challenge: finding the specific column value format for a custom column type requires navigating multiple documentation pages. Developer community forums are active.

GraphQL API with queries and mutations for boards, items, groups, columns, updates, and assets. Creating or updating items requires setting column_values as a JSON string with column-type-specific formats — status columns use index, date columns use date strings, person columns use person IDs. This is the main API friction: agents must know the column type and its value format to write data correctly. The items_page_by_column_values query enables filtered lookups. Pagination uses cursor-based patterns. Webhooks trigger on item create, update, and column value changes. Mutations support batch item creation via create_item calls within a single query. The API supports file uploads via a dedicated endpoint. Rate complexity budget is 5,000,000 units per minute.

GraphQL errors appear in the errors[] array with message and optional extensions fields. Rate limiting uses a complexity budget (5,000,000 units/minute) — each field in a query has a complexity cost. Simple queries are cheap; deeply nested queries across many boards consume budget quickly. The complexity_remaining value is returned in extensions. 429 responses indicate budget exhaustion. Column value validation errors are the most common mutation failure — invalid formats for specific column types (e.g., wrong date format, invalid status index) return descriptive error messages. Webhook delivery retries failed webhooks. Query performance degrades on boards with thousands of items — agents working with large boards should use pagination aggressively.