Reference · built on requestConnectorWork & ticket management

monday.com

Boards, items, column values, groups, and updates from monday.com accounts through the monday GraphQL API and webhooks.

Request accessPricing ↗

About

monday.com is a work platform arranged around boards. A board holds groups of items, each item carries values in typed columns, and items can have subitems and updates, the threaded notes where teams discuss the work. Boards sit inside workspaces and are public, private, or shareable. Everything is reached through one GraphQL endpoint, https://api.monday.com/v2.

Through Fibric, an operator subscribes to board events, reads the item and its column values, and proposes a status change, a column edit, or an update for your approval. Each approved change is recorded with what changed, why, and the way back.

This is a reference listing. It documents what Fibric would read from monday.com and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Boards with their columns, groups, items_page, owners, and subscribers through the boards query, filtered by workspace_ids and state
  • Items with column_values, group, subitems, updates, creator, and timestamps through the items query, up to 100 ids per call
  • Column values as raw JSON plus a text representation, with type-specific fields such as label on a StatusValue
  • Updates on an item: body, text_body, creator, replies, and assets
  • Board webhooks for create_item, change_column_value, change_status_column_value, item_moved_to_group, create_update, and item_archived
  • A challenge handshake on webhook creation, and retries once a minute for 30 minutes when a delivery fails

Proposed actions

  • Target capability: propose a column change through change_column_value, change_simple_column_value, or change_multiple_column_values
  • Target capability: propose an update on an item through create_update, with parent_id for a reply
  • Target capability: propose moving an item through move_item_to_group or move_item_to_board
  • Target capability: propose a new item through create_item, or an archive through archive_item

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase overdue actions

    The operator reads a board's items by status column and date, proposes an update naming the owner and the slip, and moves the item to an overdue group once you approve.

    With Action Follow-up

  • Watch vendor service windows

    Vendor request boards carry a status and a due date per item. The operator flags items past their window and proposes a status change and an escalation update.

    With Vendor SLA Watch

  • Age out work orders

    Work orders tracked as items are grouped by age. The operator proposes reassignments for the oldest and adds an update on each with the reason.

    With Work Order Aging

  • Schedule inspections

    Inspection boards hold dates in a date column. The operator proposes the next visit and creates the item in the right group for your approval.

    With Inspection Scheduling

Requirements

  • A monday.com account and a user with API access; a personal token mirrors that user's board, column, and item permissions
  • Board ids for the boards the operator watches, since create_webhook subscribes one board at a time
  • An HTTPS URL of at most 255 characters that returns the challenge field when the webhook is created
Authentication
A personal API token from the Developer Center or the Administration tab, sent in the Authorization header, or an app token with OAuth scopes such as updates:read and updates:write.

Limits

  • Personal tokens share 10M complexity points per minute; trial, NGO, and free accounts get 1M, and a single query may not exceed 5M
  • Daily calls are capped by plan: 1,000 on Free, Basic, and Standard, 10,000 on Pro, 25,000 on Enterprise, resetting at midnight UTC
  • Concurrency is 40 requests on most plans, 100 on Pro, and 250 on Enterprise; every limit error returns retry_in_seconds
  • create_board, duplicate_board, and group duplication run at most 40 mutations per minute

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request monday.com ↗

Questions and answers

What is a complexity point?
monday.com prices each query by the data it touches rather than by request count. Personal tokens get 10M points per minute, app tokens 5M for reads and 5M for writes, and no single query may exceed 5M. A ComplexityException names the budget hit, and retry_in_seconds says when to try again.
Which events can a board webhook send?
Twenty-one types, including create_item, change_column_value, change_status_column_value, change_specific_column_value, item_moved_to_any_group, item_archived, item_deleted, create_subitem, create_update, and edit_update. Three take a config, for example a columnId for change_specific_column_value.
How do you write a status or date value?
With change_column_value or change_multiple_column_values, passing JSON shaped for the column type, or change_simple_column_value for a plain string. Pass create_labels_if_missing to add a new status label. Reads come back as raw value JSON and a text field.
Ask about monday.com

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with monday.com through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy