API coverage gaps

We are constantly expanding the monday.com API and monitoring coverage gaps based on feature requests from our developer community and customers. Below you'll find a list of commonly requested capabilities that the API does not currently support.

If something you are looking for is not available in the API:

Join the developer community to connect with other builders and the monday.com team.
Check if a feature request already exists by searching the community forum.
Open a new feature request if one doesn't exist — the team reviews and prioritizes these regularly.

We may be actively working on some of the items listed below. Check the developer community for the latest status updates.

Bulk import / update

A bulk upload file-based flow for item creation or modification is not yet available in the API but is expected to release in an upcoming version. This will allow you to upload a file (e.g., CSV) to create or update items in bulk on a board.

In the meantime, use create_item and change_multiple_column_values to programmatically create and update items. For importing from external systems (e.g., BigQuery, data warehouses), export your data to a structured format and use those mutations. For sources like email archives (PST), check the monday.com marketplace for third-party migration tools.

Automation management (create, delete, list)

The API does not currently expose mutations to create, delete, update, or list board automations (recipes). Automations can only be managed through the monday.com UI.

Exposing automation management via the API is actively being worked on and is expected to release in upcoming versions.

Trash management (restore and bulk delete)

The API supports archive_item and delete_item for individual items. However, there is no API support for:

Restoring items from the trash
Permanently deleting items from the trash
Bulk trash operations (delete or restore many items at once)

These operations are only available through the monday.com UI.

Board type conversion

Change board visibility after creation

The board_kind (public, private, share) is set at creation time via create_board and cannot be changed through the API afterward. The update_board mutation only supports updating name, description, communication, and item_nickname.

Convert classic boards to multi-level

There is no API endpoint or UI migration tool to convert an existing classic board to a multi-level board. To use multi-level features, create a new multi-level board and migrate items. See Working with multi-level boards for details on the multi-level architecture.

Unsupported board and user fields

Some fields that developers commonly request are not available in the GraphQL schema:

Board fields

Requested field	Status	Alternative
`last_accessed_at`	Not available	Use `order_by: used_at` on the `boards` query to sort by recent access
`is_template`	Not available	Use `template_id` on `create_board` to create from a template; use `created_from_board_id` (2026-04+) to check if a board was duplicated

User fields

Requested field	Status	Alternative
`is_2fa_enabled`	Not available	Security settings are managed through the admin panel
`authentication_method`	Not available	Not exposed in the public API
`account_id` (scalar)	Not available	Use `account { id }` to access the account identifier as a nested object

Dashboard board management

The update_dashboard mutation supports changing a dashboard's name, visibility, folder, and workspace, but does not support adding or removing connected boards. Board connections can only be set at creation time via the board_ids argument on create_dashboard.

Built-in automation trigger specifications

The API documentation covers webhook event types and their payloads, but does not provide reference documentation for built-in Automations Center triggers (e.g., "When status changes to something"). This includes:

Trigger payload schemas and output field definitions
Configurable input defaults and options
Legacy-to-new-workflow trigger mappings

For custom integration triggers, refer to the apps integration documentation.

Workdoc webhook events and exports

The API does not currently support:

Doc-specific webhook events — Webhooks are scoped to board-level events. Use the version history queries to track document changes.
PDF export — Only markdown export is available via the API.
Binary image upload — Image blocks reference a public URL. Host images externally and pass the URL when creating blocks.

Column creation limitations

Bulk creation: There is no bulk column creation endpoint. Use create_column individually for each column.
Visibility at creation: Column visibility (hidden/shown) cannot be set at creation time via the API.
Custom vs native marker: There is no field on the Column type to distinguish custom columns from native/built-in ones.
Column audit data: The Column type does not include created_at or created_by fields. Use activity logs to audit column creation.

Token invalidation on app uninstall/reinstall

The behavior and timing of OAuth token invalidation when an app is uninstalled and reinstalled is not fully documented in the platform API docs. For details on the OAuth lifecycle, refer to the apps OAuth documentation.

Mobile OAuth flow

The API documentation does not cover mobile-specific OAuth flows, including:

Native mobile browser (Safari View Controller / Chrome Custom Tabs) behavior
PKCE support for mobile clients
Custom URI redirect schemes

For OAuth setup, see the authentication guide and the apps OAuth documentation.

Vibe design system reference

The Vibe design system (components, tokens, import paths, props) is maintained separately from the API documentation. For Vibe resources:

Component library and Storybook: vibe.monday.com
GitHub repository: monday-ui-react-core

The API docs cover the monday apps framework for building apps that use Vibe components.

Filtering by mirror and formula columns

Server-side filtering via items_page does not support mirror or formula columns. See the items page and column type documentation for mirror and formula for details and workarounds.

Workspace members query

There is no members field on the Workspace type. To retrieve workspace members, use the users_subscribers and owners_subscribers fields on the workspaces query.

Webhook limits

The documentation does not provide specific numeric limits for webhooks (e.g., maximum webhooks per board or account, delivery rate caps). For general API rate limits, see the rate limits page.