Productivity

monday.com

by monday.com

Overview

The monday.com AI Connector brings core platform capabilities directly to agents and AI assistants. It supports searching boards, creating and updating items and columns, assigning owners, setting timelines, and posting updates — enabling a wide range of work management and CRM use cases across teams and departments. Teams of people and agents use monday.com as a task tracker and project tracking hub: planning campaigns and events, tracking milestones, dependencies, and workload, managing approval workflows and request intake, and sharing status updates across projects and portfolios — as well as a CRM for managing leads, contacts, and deals. Beyond day-to-day work management, the connector lets agents answer questions using monday.com's official knowledge base, plan and build automations and multi-step workflows, run and save reusable code actions, and configure other monday.com agents. Agents can convert meeting content into meeting tasks, create a campaign brief, produce a sprint summary, perform request triage, monitor SLA performance, and surface overdue work, at-risk work, and deadline risk across monday.com boards, items, owners, projects, and portfolios.

Tools

activate-sequence

ChatGPT

Activate a sequence. Changes status from INACTIVE to ACTIVE, enabling enrollment and step execution.

agent_catalog

ChatGPT

Browse the account-wide catalog of available trigger types and skills for monday platform agents. READ-ONLY — no agent_id required. Use this tool to discover what's available BEFORE wiring anything to a specific agent. ACTIONS: - list_triggers: { block_reference_ids? } — returns available trigger types. Each entry has block_reference_id (required for manage_agent_triggers action:"add"), name, description, field_schemas (describes field_values shape), and required_fields (fields to collect from the user). Note: only triggers that can be added programmatically appear here. OAuth/3rd-party triggers (Slack, Gmail, Salesforce, etc.) require user setup in the monday.com UI and will not appear here. - list_skills: {} — returns available skills with id, name, description. Never guess or invent a skill id — always look it up here before calling manage_agent_skills action:"add". USAGE EXAMPLES: - List all trigger types: { "action": "list_triggers" } - Fetch specific trigger: { "action": "list_triggers", "block_reference_ids": ["some-block-ref-id"] } - List all skills: { "action": "list_skills" } RELATED TOOLS: - manage_agent_triggers — use block_reference_id from list_triggers to attach a trigger to a specific agent - manage_agent_skills — use skill id from list_skills, or action:"create" to author a new skill, then attach to an agent - manage_agent — manage the agent entity itself (create, update, delete, activate, etc.)

all_api_read

ChatGPT

Execute read-only GraphQL queries against the monday.com API. Only queries are accepted — mutations are rejected with an error before the request is sent. Use get_graphql_schema and get_type_details tools first to understand the schema before crafting your query.

all_api_write

ChatGPT

Execute GraphQL mutations against the monday.com API to create, update, or delete data. Only mutations are accepted — queries are rejected with an error before the request is sent. Use get_graphql_schema and get_type_details tools first to understand the schema before crafting your mutation.

all_monday_api

ChatGPT

Execute any monday.com API operation by generating GraphQL queries and mutations dynamically. Make sure you ask only for the fields you need and nothing more. When providing the query/mutation - use get_graphql_schema and get_type_details tools first to understand the schema before crafting your query.

all_widgets_schema

ChatGPT

Fetch complete JSON Schema 7 definitions for all available widget types in monday.com. This tool is essential before creating widgets as it provides: - Complete schema definitions for all supported widgets - Required and optional fields for each widget type - Data type specifications and validation rules - Detailed descriptions of widget capabilities Use this tool when you need to: - Understand widget configuration requirements before creating widgets - Validate widget settings against official schemas - Plan widget implementations with proper data structures The response includes JSON Schema 7 definitions that describe exactly what settings each widget type accepts.

board_insights

ChatGPT

This tool allows you to calculate insights about board's data by filtering, grouping and aggregating columns. For example, you can get the total number of items in a board, the number of items in each status, the number of items in each column, etc. Use this tool when you need to get a summary of the board's data, for example, you want to know the total number of items in a board, the number of items in each status, the number of items in each column, etc.[REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper filters and knowing which columns are available.[IMPORTANT]: For some columns, human-friendly label is returned inside 'LABEL_<column_id' field. E.g. for column with id 'status_123' the label is returned inside 'LABEL_status_123' field.

build-crm-setup

ChatGPT

Build approved monday CRM boards from a propose-crm-setup proposal. Create the CRM boards from the most recent propose-crm-setup proposal. Requires its setup_token and explicit user confirmation. Never call this in the same turn as propose-crm-setup: the user must first see the proposal and approve it in a later message, and the original request to set up a CRM is not approval. Renaming a board repoints its board relations at the renamed board, and reusing existing boards still creates the remaining proposed ones. Results that plan or create boards return a newer setup_token; a later build-crm-setup retry passes that newest token. Before writing, it checks the final names again and returns COLLISION without creating anything for unresolved conflicts. It returns PROPOSAL_OUTDATED, also without creating anything, when the approved proposal can no longer be reproduced, and PLAN_EXPIRED when its token expired; in both cases propose again with the same setup_token. It builds each board through a template or the monday board generator, verifies the result, and adds only fields required for a usable CRM. Confirmation and build results carry warnings the user needs to hear. Once boards exist, the result suggests connecting the user's email, Gmail or Outlook by detected provider (unless a CRM email account is already connected), and a calendar through show_connect_integration; it also tells you to ask, each as its own question, whether to import Gmail contacts into the Contacts board and whether to add upcoming calendar meetings to the Deals board. It never imports data itself, and never deletes or overwrites an existing board. Scope: this tool builds CRM structure only. It does not import records from another CRM, build pure project-delivery workflows, model nested client-of-client accounts, split one motion into product or regional pipelines, enforce per-assignee privacy, or undo created boards. Saved views, automations, and mirror columns are not created by this version. Phone-first and field-sales teams can use the boards but should skip the optional email connection. Email and calendar consent must be completed by the user in a browser. Importing contacts from Gmail into the Contacts board is optional, offered after the boards are built, and happens only if the user agrees to it.

change_item_column_values

ChatGPT

Change the column values of an item in a monday.com board. [REQUIRED PRECONDITION]: For board-relation linking tasks, call link_board_items_workflow before using this tool.

create-sequence

ChatGPT

Create a new outreach sequence on a board. Create a new sequence on a board. Always created INACTIVE; use activate-sequence to enable it before the sequence can run. Call this tool directly with whatever arguments you have — do not pre-fetch boards or email accounts first. Never set ordinals or UUIDs. Never fabricate steps.

create-timeline-item

ChatGPT

Create a new structured activity entry (call, meeting, email) on a CRM item's timeline. Create a new structured activity entry on a CRM item's timeline. Returns the created timeline_item_id. For freeform notes (meeting outcomes, follow-ups), use create-timeline-note instead.

create-timeline-note

ChatGPT

Add an unstructured note (meeting outcome, follow-up reminder, or rep context) to a CRM item's timeline. Log a freeform text note on a CRM item's timeline — meeting outcomes, follow-up reminders, context for the next rep, or any unstructured observation.

create_action

ChatGPT

Save a reusable action (a stored code script). Variables are injected as environment variables (access via os.environ in Python, process.env in JS/TS). Recommended: Test your code with execute_code before saving to ensure it works correctly. Network access is restricted to the following hosts: [api.monday.com, mcp.monday.com/mcp]. Requests to any other host will be blocked. Example: name: "Get board items", description: "Fetches items from a board", language: "python", code: "import requests\nprint('done')"

create_automation

ChatGPT

Creates an automation on a monday board from a structured natural-language description. Use this tool only when you know: - boardId - the user's intended trigger - at least one intended action - any details the user provided that are relevant to the trigger, conditions, or actions The caller does not need to know the exact available automation blocks or their required fields. Describe the user's intent clearly — the tool will translate that intent into supported blocks and values. If a required detail is missing from the user's request, ask for clarification before calling the tool. If the tool returns status: "needs_clarification", present the unresolved fields to the user, gather answers, then call the tool again. Describe the automation in this format: Trigger: When <the event that should start the automation> Details: <relevant detail>: <value> Conditions: - Only if <condition that should be true> Details: <relevant detail>: <value> Actions: - <action the automation should perform>: <relevant detail>: <value> Rules: - Use one trigger. - Conditions are optional. - Multiple conditions mean AND. - Use one or more actions. - Do not use branching. - Use natural language, not block IDs or internal field names. - Actions may reference values from the trigger context, such as "{{item name}}", "{{creator}}", "{{status}}", "{{group}}", or "{{board}}". Terminology: - Trigger: the event that starts the automation, such as "when a new item is created". - Conditions: optional requirements that must be true before actions run. - Actions: what the automation does when it runs. Example: Trigger: When a new item is created Actions: - Send a notification: Recipient: John Snow Title: Important Update Message: The item "{{item name}}" was created. - Move the item to a group: Group: Top group

create_board

ChatGPT

Create a monday.com board

create_column

ChatGPT

Create a new column in a monday.com board

create_dashboard

ChatGPT

Use this tool to create a new monday.com dashboard that aggregates data from one or more boards. Dashboards provide visual representations of board data through widgets and charts. Use this tool when users want to: - Create a dashboard to visualize board data - Aggregate information from multiple boards - Set up a data visualization container for widgets

create_doc

ChatGPT

Create a new monday.com doc either inside a workspace or attached to an item (via a doc column). After creation, the provided markdown will be appended to the document. LOCATION TYPES: - workspace: Creates a document in a workspace (requires workspace_id, optional doc_kind, optional folder_id, optional docOwnerIds) - item: Creates a document attached to an item (requires item_id, optional column_id, optional docOwnerIds) USAGE EXAMPLES: - Workspace doc: { location: "workspace", workspace_id: 123, doc_name: "My Doc", doc_kind: "private" , markdown: "..." } - Workspace doc in folder: { location: "workspace", workspace_id: 123, doc_name: "My Doc", folder_id: 17264196 , markdown: "..." } - Item doc: { location: "item", item_id: 456, doc_name: "My Doc", column_id: "doc_col_1" , markdown: "..." } - Workspace doc with agent owner: { location: "workspace", workspace_id: 123, doc_name: "My Doc", markdown: "...", docOwnerIds: ["<agent_owner_user_id>"] }

create_folder

ChatGPT

Create a new folder in a monday.com workspace

create_form

ChatGPT

Create a monday.com form. Also creates a backing board to store responses. Returns the formToken for future mutations.

create_form_submission

ChatGPT

Submit a response to a monday.com WorkForm. Use get_form first to retrieve the WorkForm, then: - Inspect each question's showIfRules to determine which questions are conditionally shown based on previous answers. - Inspect each question's settings for any answer constraints (e.g. rating limits, select options, label limits). - Take note of any titles, descriptions, and content blocks to present the form naturally as you walk the user through it. - Take note of pages and question order to present questions in the correct sequence. Gather all answers upfront before calling this tool — do not submit one question at a time. Accepts a bare form token, a full WorkForm URL (e.g. https://forms.monday.com/forms/{form_token}?r=use1), or a shortened wkf.ms URL (e.g. https://wkf.ms/4tqP28t) — shortened URLs are automatically resolved by following the redirect. Returns the submission ID.

create_group

ChatGPT

Create a new group in a monday.com board. Groups are sections that organize related items. Use when users want to add structure, categorize items, or create workflow phases. Groups can be positioned relative to existing groups and assigned predefined colors. Items will always be created in the top group and so the top group should be the most relevant one for new item creation

create_item

ChatGPT

Create a new item with provided values, create a subitem under a parent item, or duplicate an existing item and update it with new values. Use parentItemId when creating a subitem under an existing item. Use duplicateFromItemId when copying an existing item with modifications.[REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper column values and knowing which columns are available.

create_items

ChatGPT

Create up to 20 new items in a single call. Each item is fully independent - it chooses its own groupId, parentItemId (for subitems), duplicateFromItemId (for bulk templating from an existing item), and createLabelsIfMissing. A single call can therefore span multiple groups, mix regular items with subitems under different parents, and mix fresh creates with duplicates of existing items. Each item returns its own item_id and item_url on success, or a raw error message on failure. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper column values and knowing which columns are available.

create_notification

ChatGPT

Send a notification to a user via the bell icon and optionally by email. Use target_type "Post" for updates/replies or "Project" for items/boards.

create_update

ChatGPT

Create a new update (comment/post) on a monday.com item. Updates can be used to add comments, notes, or discussions to items. You can optionally mention users, teams, or boards in the update. You can also reply to an existing update by using the parentId parameter.

create_view

ChatGPT

Create a new board view (tab) with optional filters and sorting. This creates a saved view on a monday.com board that users can switch to. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text Example filter for people column: { "rules": [{ "column_id": "people", "compare_value": ["person-12345"], "operator": "any_of" }] } Example filter for status column: { "rules": [{ "column_id": "status", "compare_value": [1], "operator": "any_of" }] }

create_view_table

ChatGPT

Create a new table-type board view with optional filters, sort, tags, and table-specific settings (column visibility/order and group-by). Use this instead of create_view when you need to configure table-specific settings. For a simple table view, create_view also works. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text Example settings.columns: { "column_properties": [{ "column_id": "status", "visible": true }], "column_order": ["name", "status", "date"] } Example settings.group_by: { "conditions": [{ "columnId": "status" }], "hideEmptyGroups": true }

create_widget

ChatGPT

Create a new widget in a dashboard or board view with specific configuration settings. This tool creates data visualization widgets that display information from monday.com boards: Parent Containers: - DASHBOARD: Place widget in a dashboard (most common use case) - BOARD_VIEW: Place widget in a specific board view Critical Requirements: 1. Schema Compliance: Widget settings MUST conform to the JSON schema for the specific widget type 2. Use all_widgets_schema first: Always fetch widget schemas before creating widgets 3. Validate settings: Ensure all required fields are provided and data types match Workflow: 1. Use 'all_widgets_schema' to get schema definitions 2. Prepare widget settings according to the schema 3. Use this tool to create the widget

create_workflow

ChatGPT

Creates a new empty workflow in a monday.com workspace. Use this when the user wants to build a new standalone workflow from scratch. Workflows are cross-board, workspace-level — distinct from automations (use create_automation for those). You only need a workspaceId to get started — all other fields are optional. Returns: - workflowObjectId: the workflow object ID - workflowDraftId: the current draft version ID — workflows start as drafts and must be published before they run Terminology: - Workflows vs. automations: workflows are standalone objects scoped to a workspace. Automations (create_automation) are per-board trigger/action rules. They are different products. - Draft: the editable, inactive version of a workflow. Changes are made on the draft version until it is published as the live version. - Privacy: PUBLIC — visible to all workspace members (default). PRIVATE — restricted access. SHAREABLE — accessible to guests outside the account. Note: if directing the user to the workflow in the UI, the correct URL path is custom_objects/, not workflows/ — e.g. {account}.monday.com/custom_objects/{workflowObjectId}.

create_workspace

ChatGPT

Create a new workspace in monday.com

deactivate-sequence

ChatGPT

Deactivate a sequence so it stops accepting new enrollments. Deactivate a sequence (sets status to INACTIVE, blocking new enrollments while existing enrollments continue). Convenience alias for update-sequence-status when direction is known to be INACTIVE.

delete_action

ChatGPT

Use to permanently delete a saved action by its ID. Delete a saved action. Example: id: "550e8400-e29b-41d4-a716-446655440000"

delete_view

ChatGPT

Delete a board view (tab) from a monday.com board. Use get_board_info to find the view ID before deleting.

duplicate-sequence

ChatGPT

Copy an existing sequence, including its steps, as a new INACTIVE sequence. Duplicate a sequence. Creates a copy with the same steps and configuration. The new sequence starts with INACTIVE status.

enroll-item-in-sequence

ChatGPT

Enroll one or more CRM contacts or leads into an outreach sequence. The sequence must be active. Returns per-item success/failure so partial failures do not silently drop contacts.

execute_code

ChatGPT

Run arbitrary code in a monday-authenticated sandbox, without saving. Prefer dedicated monday tools for individual reads, writes, and GraphQL queries/mutations — they render in the UI and are retried one step at a time. Reach for execute_code when code is genuinely the better tool: - Bulk / multi-item work — batch operations, dedup, aggregations, joins across boards (one script beats N tool calls that accumulate context and compound failure) - Data transformation — normalizing phones/dates, fuzzy matching, weighted scoring - File I/O — parsing uploaded CSV/XLSX to import items, producing downloadable exports - Multi-step workflows where each step's output gates the next The sandbox has authenticated access to the monday.com API. You can make HTTP requests with GraphQL queries and mutations — authentication is handled automatically. IMPORTANT: Network access is restricted to the following hosts: [api.monday.com, mcp.monday.com/mcp]. Requests to any other host (or a different path on a restricted host) will be blocked. Use this tool to query boards, items, columns, users, updates, and any other monday.com API resource. THE SANDBOX IS PER-CALL: a new empty container every call, destroyed when the call returns. Nothing written to disk survives, /tmp included. Never write a file in one call to read it in a later one, and don't invent staging paths for earlier tool results — none exist. To carry data forward, print it and pass it into the next call's code, or do the whole job in one call. Splitting a fan-out across calls only works if the later calls don't depend on the earlier ones' files. FAIL WITH A NON-ZERO EXIT. A run that prints an error and exits 0 is recorded as a success. The monday.com API returns HTTP 200 with an "errors" array, so check the parsed body rather than the status code and raise when it is present. Let exceptions propagate; don't wrap the script in a bare try/except. TIME LIMIT: 300s. A run that exceeds it is killed, so scope each call to finish well inside the limit instead of fetching everything in one script. Don't call mcp.monday.com from inside the sandbox to reach monday tools — you already have them, and a tool missing from your tool list won't be found there either. Example — monday.com GraphQL query, raising on errors (Python). Use this shape for every API call: code: "import requests\ndef gql(query):\n body = requests.post('https://api.monday.com/v2', json={'query': query}).json()\n if 'errors' in body:\n raise RuntimeError(body['errors'])\n return body['data']\nprint(gql('{ users(limit:5) { id name email } }'))" Example — monday.com GraphQL mutation (Python): code: "import requests\nmutation = 'mutation { create_board(board_name: \"New Board\", board_kind: public) { id } }'\nbody = requests.post('https://api.monday.com/v2', json={'query': mutation}).json()\nif 'errors' in body:\n raise RuntimeError(body['errors'])\nprint(body['data'])" Example — with vars (accessed via os.environ): code: "import os, requests\nuser_id = os.environ['user_id']\nresp = requests.post('https://api.monday.com/v2', json={'query': f'{{ users(ids: [{user_id}]) {{ id name email }} }}'})\nprint(resp.json())" vars: {"user_id": 12345} Example — simple (Python): code: "print('hello world')" Example — with files (input and output): code: "import json\ndata = json.load(open('/tmp/data.json'))\njson.dump({'count': len(data)}, open('/tmp/result.json', 'w'))" files: [{"path": "/tmp/data.json", "content": "W3siaWQiOiAxfV0="}] output_files: ["/tmp/result.json"] Example — auto-collect outputs (write anything you want returned under /outputs): code: "import os, json\nos.makedirs('/outputs', exist_ok=True)\njson.dump({'ok': True}, open('/outputs/result.json', 'w'))" return_outputs: true

explore_meetings

ChatGPT

Discover meetings by topic, or list/browse meetings by date and access. Returns meetings ranked by keyword relevance (matched against title and AI gist — not semantic). USE THIS FIRST for topic/theme questions ("what did we decide about pricing", "find meetings about the acme deal") AND for listing/browsing ("list my recent meetings", "meetings from last week", "my last 10 meetings"). When query is omitted, returns recent meetings filtered by date/access only — this is the tool for listing. Pass returned ids to get_meetings_content for full content, or to search_meetings_content for matching passages. Only indexed meetings are candidates.

finalize_asset_upload

ChatGPT

Finalize a file upload and create the asset on monday.com. Call this after uploading the file to the presigned URL from get_asset_upload_url. Requires the etag value from the PUT response headers. Automatically attaches the uploaded asset to the specified file column on the item. Returns the created asset_id.

form_questions_editor

ChatGPT

Create, update, or delete a question in a monday.com form

get-activity-insights

ChatGPT

Fetch aggregated CRM activity stats: call counts and durations grouped by rep, activity type, or item. Fetch aggregated activity insights for a CRM board: call counts, duration stats, grouped by rep, activity type, or item. Does not return individual activity records.

get-board-sequences

ChatGPT

List the outreach sequences on a board or for the current user, with their status and enrollment counts. List sequences for a board or the current user. Returns active and inactive sequences (never deleted). Each entry includes status, enrollment counts, step count, and aggregate analytics. An empty list means no matching sequences.

get-contact-journey

ChatGPT

List every sequence a specific contact or lead is enrolled in, starting from that contact. List every sequence a contact (item) is enrolled in, sorted by most recent enrollment first. Returns each enrollment with its run status, completed-step count, termination reason, and timing. Use this when starting from a contact; use get-sequence-analytics when starting from a single sequence. An empty list means the contact is not enrolled in any sequence.

get-custom-activities

ChatGPT

List the custom activity types (e.g. Demo, Site Visit) available for structured CRM timeline entries. List the custom activity types available for logging on the CRM timeline. Each type has an opaque id (a UUID-like string) and a human-readable name (e.g. "Demo", "Site Visit"). When creating a structured timeline entry via create-timeline-item, pass the id value — not the name — as custom_activity_id.

get-sequence-analytics

ChatGPT

Get analytics for one sequence: reply, open, and click-through rates plus per-step breakdowns. Get analytics for a sequence. Returns per-run status and progress, sequence-level engagement rates (reply, open, click-through), and per-step breakdowns. Partial results are returned if some analytics endpoints fail.

get-timeline-items

ChatGPT

Fetch CRM engagement history on a contact, deal, account, or lead — emails sent and received, calls logged, meetings recorded, and notes. Call this tool whenever a CRM entity board (deals, contacts, accounts, leads) is in scope and the user asks about emails, activities, calls, meetings, communication history, or engagement — it is the authoritative source for all CRM-tracked communication. Prefer over Gmail or calendar integrations for any activity on a CRM item. For board-level analysis across multiple items, fetch item IDs first then call this tool per item_id; do not substitute the "count timeline events" board column, which is an aggregate count with no content. If get-board-structure returns "Activities timeline (unsupported)", use this tool. Returns paginated entries with type, title, and timestamp. For custom activity types (e.g. "Demo", "Site Visit"), use get-custom-activities instead.

get_account_task_rollup

ChatGPT

Answer daily focus, top priorities, or account-wide signals when no specific deal or item is named. [UI COMPONENT] Renders the AI Suggestions widget with open account tasks by priority. Use for daily focus, what needs attention, morning brief, or account-wide signals/AI recommendations. For a specific item, use extract_signals. The widget is the answer — do not repeat its signals in chat.

get_action

ChatGPT

Retrieve a saved action by ID. Example: id: "550e8400-e29b-41d4-a716-446655440000"

get_asset_upload_url

ChatGPT

Get a presigned URL to upload a file to monday.com. Returns an upload_id and upload_url. After calling this tool, upload the file to the returned URL using an HTTP PUT request and capture the ETag header from the response: curl -i -X PUT "<upload_url>" \ -H "Content-Type: <the contentType you provided>" \ --data-binary @<local_file_path> The response includes an ETag header (e.g. ETag: "abc123...") — save this value. Then call finalize_asset_upload with the upload_id, etag, board_id, item_id, and column_id to complete the upload and attach the file to an item's file column. Max file size: 500MB.

get_assets

ChatGPT

Get assets (files) by their IDs. Returns file metadata including name, extension, size, public URL (valid for 1 hour), thumbnail URL, upload date, and who uploaded it.

get_automation_runs

ChatGPT

Read automation/workflow run history. Read-only. Modes: - "history": paginated run feed (state, duration, error reason). Use "filters" to narrow results and "nextPageOffset" to page (offset-only — next page = previous offset + returned count). - "detail": single run by "triggerUuid" (required) — returns block steps and MCP tool calls. Set "includeToolEvents": false to skip tool calls. Scope: provide "boardId" for a specific board or "accountWide": true. One is required. Known event states: "success", "failure", "exhausted".

get_automation_statistics

ChatGPT

Aggregate automation run statistics. Read-only. Breakdowns: - "totals": success/failure/total counts at the account or board level. - "by_entity": per-automation and per-workflow counts for a given "runStatus" (required: "success" | "failure" | "exhausted"). Use "excludeAutomationIds" to omit specific automations. Scope: provide "boardId" for a specific board or "accountWide": true. One is required. Optional "userIds" narrows results to specific creators.

get_board_activity

ChatGPT

Get board activity logs for a specified time range (defaults to last 30 days). Optionally filter by item ids or user ids to avoid fetching activity for the entire board.

get_board_info

ChatGPT

Get comprehensive board information including metadata, structure, owners, and configuration. Also returns the board's views (e.g. table views, filter views) — each view includes its id, name, type, and a structured filter object.

get_board_items_page

ChatGPT

Get all items from a monday.com board with pagination support and optional column values and item descriptions. Returns structured JSON with item details, creation/update timestamps, and pagination info. Use the nextCursor parameter from the response to get the next page of results when has_more is true. To retrieve an item description (the rich-text body/details of a monday.com item), set includeItemDescription to true — the response will include the item description document blocks with their content, type, and id. Use this whenever the user asks about an item description, body, details, or notes. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper filters and knowing which columns are available. [REQUIRED PRECONDITION]: For board-relation / cross-board linking tasks, call link_board_items_workflow before using this tool. VIEW-BASED FILTERING: If the user refers to a board view by name (e.g. "show me items in the Overdue view"), first call get_board_info to get the board views, find the matching view by name, then extract its filter field and pass it as the filters argument here.

get_column_type_info

ChatGPT

Retrieves comprehensive information about a specific column type. Use fetchMode "schema" (default) to get the JSON schema definition from the API — use this before creating or updating columns (e.g. create_column) to understand structure, validation rules, and available properties for column settings. Use fetchMode "guidelines" to get only guidelines.filter and guidelines.aggregation for building items_page filters and board insights counts (no schema, no GraphQL round-trip).

get_form

ChatGPT

Get a monday.com form by its form token. Form tokens can be extracted from the form's url. Given a form url, such as https://forms.monday.com/forms/abc123def456ghi789?r=use1, the formToken is the alphanumeric string that appears right after /forms/ and before the ?. In the example, the formToken is abc123def456ghi789.

get_graphql_schema

ChatGPT

Fetch the monday.com GraphQL schema structure including query and mutation definitions. This tool returns available query fields, mutation fields, and a list of GraphQL types in the schema. You can filter results by operation type (read/write) to focus on either queries or mutations.

get_meetings_content

ChatGPT

Fetch full content (summary, topics, action items, transcript) for meetings you already have ids for. Get those ids from explore_meetings (topic/listing/browse) or search_meetings_content (passages) first — this tool is NOT for discovery or listing. Pass the ids with the include_ flags for the content you need (defaults to the summary if none are set). Requested ids that are not returned are listed in missing_ids (not found, not accessible, or no completed recording); meetings whose content was dropped to keep the response within its size limit are listed in content_omitted_ids. The search param is a narrow case-insensitive substring fallback on title, participant name, or email — NOT topic/keyword search.

get_monday_dev_sprints_boards

ChatGPT

Discover monday-dev sprints boards and their associated tasks boards in your account. Purpose: Identifies and returns monday-dev sprints board IDs and tasks board IDs that you need to use with other monday-dev tools. This tool scans your recently used boards (up to 100) to find valid monday-dev sprint management boards. What it Returns: - Pairs of sprints boards and their corresponding tasks boards - Board IDs, names, and workspace information for each pair - The bidirectional relationship between each sprints board and its tasks board Note: Searches recently used boards (up to 100). If none found, ask user to provide board IDs manually.

get_monday_knowledge

ChatGPT

Ask a question about monday.com and get an AI-generated answer from the official knowledge base. Use kind="general" for questions about using monday.com — features, automations, UI, help center, and settings. Returns cited source articles with links. Use kind="developer_docs" for questions about the monday.com API — GraphQL queries and mutations, authentication, rate limits, webhooks, schema, API best practices, and building apps. Important: do not include PII data in the questions.

get_notetaker_meetings

ChatGPT

Retrieve notetaker meetings with optional detailed fields. Use include_summary, include_topics, include_action_items, and include_transcript flags to control which details are returned. Use access to filter by meeting access level (OWN, SHARED_WITH_ME, SHARED_WITH_ACCOUNT, ALL). Defaults to OWN. Supports filtering by ids, search term, and cursor-based pagination.

get_run_once_trigger_entities

ChatGPT

Lists the concrete entities (items, boards, docs, ...) the workflow's trigger can be fired on, so the workflow can be run once on one of them. Use this tool: - ALWAYS before calling run_workflow_once, to learn whether the trigger needs an entity and which entities are available. - When the user asks what the workflow would be run on. Do NOT use this tool for a board automation, such as one create_automation built: run-once applies to workflows only, and the id create_automation returns is not a workflowObjectId. Tell the user to trigger that automation on the board instead. The tool does NOT modify the workflow and does NOT run anything. The response is a JSON object: - status "ok": "requiresEntity" tells you whether run_workflow_once needs a triggerPayload, and "entities" is a list of { label, value } candidates. Show the labels to the user and let them pick; pass the picked entity's "value" object verbatim as run_workflow_once's triggerPayload. An empty "entities" list while requiresEntity is true means there is nothing to run on — tell the user instead of guessing a payload. - status "failed": "message" explains why the entities could not be listed. Relay it; do not call run_workflow_once.

get_sprint_summary

ChatGPT

Get the complete summary and analysis of a sprint. Purpose: Unlock deep insights into completed sprint performance. The sprint summary content including: - Scope Management: Analysis of planned vs. unplanned tasks, scope creep - Velocity & Performance: Individual velocity, task completion rates, workload distribution per team member - Task Distribution: Breakdown of completed tasks by type (Feature, Bug, Tech Debt, Infrastructure, etc.) - AI Recommendations: Action items, process improvements, retrospective focus areas Requirements: - Sprint must be completed and must be created after 1/1/2025 Important Note: When viewing the section "Completed by Assignee", you'll see user IDs in the format "@user-12345678". the 8 digits after the @is the user ID. To retrieve the actual owner names, use the list_users_and_teams tool with the user ID and set includeTeams=false for optimal performance.

get_sprints_metadata

ChatGPT

Get comprehensive sprint metadata from a monday-dev sprints board including: Data Retrieved: A table of sprints with the following information: - Sprint ID - Sprint Name - Sprint timeline (planned from/to dates) - Sprint completion status (completed/in-progress/planned) - Sprint start date (actual) - Sprint end date (actual) - Sprint activation status - Sprint summary document object ID Parameters: - limit: Number of sprints to retrieve (default: 25, max: 100) Requires the Main Sprints board ID of the monday-dev containing your sprints.

get_type_details

ChatGPT

Get detailed information about a specific GraphQL type from the monday.com API schema

get_updates

ChatGPT

Get updates (comments/posts) from a monday.com item or board. Specify objectId and objectType (Item or Board) to retrieve updates. For Board queries, you can filter by date range using fromDate and toDate (both required together, ISO8601 format). By default, Board queries return only board discussion. Set includeItemUpdates to true to also include updates on individual items. Returns update text, creator info, timestamps, and optionally replies and assets.

get_user_context

ChatGPT

Fetch current user information, account information, and their relevant items (boards, folders, workspaces, dashboards). Use this tool to: - Get context about who the current user is (id, name, title) - Get account info: plan tier, active member count, trial status, and active products - Get the number of active members in the account (returns active_members_count) - Discover user's favorite boards, folders, workspaces, and dashboards - Get user's most relevant boards based on visit frequency and recency - Get user's most relevant people based on interaction frequency and recency - Reduce the need for search requests by knowing user's commonly accessed items

get_workflow_run_once_status

ChatGPT

Reports how a run started by run_workflow_once ended: whether it succeeded, and if not, which step failed and why. Call this after run_workflow_once, passing the "automationId" it returned. The tool does NOT modify the workflow and does NOT run anything. It answers immediately with whatever is known so far, so a run in progress is a normal answer, not a problem: - "isTerminal": false — the run has NOT finished. This is NOT a failure. Wait "retryAfterMs" milliseconds and call this tool again with the same arguments. Keep doing that until isTerminal is true. Never report an outcome to the user while isTerminal is false; say the run is still going. - "isTerminal": true — the run is over and "state" is its final outcome. Report it and stop calling. Trust "isTerminal" over your own reading of "state". "state" is one of: - "success" — every step ran without error. - "failure" — a step failed. "errorReason" and the failing entry in "blocks" say which and why. - "exhausted" — the run gave up after retrying a step too many times. - "stopped" — the run was stopped before finishing, so the remaining steps never ran. - "zero_actions" — the trigger fired but the workflow's conditions matched nothing, so no step ran. Nothing is broken; the entity did not qualify. - "running" — a step is executing right now. - "waiting" — the run is parked on a wait step or waiting for a second event. This can last hours, which is why "retryAfterMs" is long here. Tell the user it is waiting rather than polling silently for hours. - "not_indexed_yet" — the run's record has not appeared yet, which is expected for the first few seconds after a run starts. It does NOT mean nothing ran. "blocks" lists the steps recorded so far, each with its own "state" and, when it failed, "errorReason". While isTerminal is false this list is partial and is progress, not a verdict. Use it to tell the user which step failed rather than only that the run failed. The response is a JSON object: - status "ok": the fields above. - status "failed": the status could not be read. "message" explains why. This says nothing about the run itself — do not report the run as failed because of it.

invoke_process_planner

ChatGPT

A reasoning-focused process planner with deep knowledge of monday.com workflow architecture. Given a description of a process, it returns a structured textual plan describing one or more related workflows that implement it. Use this tool for: - Planning a new workflow or multi-workflow architecture from a process description. - Deciding whether a process should be implemented as a single workflow or multiple related workflows. - Producing a concrete, block-level plan (trigger, steps, route keys) that another agent or human can build from. - Don't tell it about one time actions, like non-repeating resource creations that are needed to set up the process. This tool does NOT have access to any specific workflow's current state — it plans from scratch using all available blocks. It does not execute any changes.

invoke_workflow_expert

ChatGPT

Workflow expert for a single workflow. Given a prompt, answers questions about the workflow's structure and configuration, or makes changes to it (create, update, delete steps, and configure step fields). Delegate any prompt that asks about a workflow or asks to change it. Pass clear, descriptive instructions — the expert will decide the right response or operations. Field values reference resources (boards, columns, people, channels, projects, ...) from monday or any external app — all handled the same way. Pass each resource through as the user stated it; the expert resolves names to IDs and asks the user when it's ambiguous. Pro-tip: pass along any ID you already have to save a follow-up question — no need to look one up first. Constraints: works on ONE workflow at a time.

list_actions

ChatGPT

List all saved actions for the current user.

list_automations

ChatGPT

List all automations on a specific monday.com board, including their ids, titles, active state, and configuration. When NOT to use: Do not call this tool to get general board information unrelated to automations. Note: Some legacy automations may not appear — mention this if users ask about missing automations.

list_users_and_teams

ChatGPT

Tool to fetch users and/or teams data. MANDATORY BEST PRACTICES: 1. ALWAYS use specific IDs or names when available 2. If no ids available, use name search if possible (USERS ONLY) 3. Use 'getMe: true' to get current user information 4. AVOID broad queries (no parameters) - use only as last resort REQUIRED PARAMETER PRIORITY (use in this order): 1. getMe - STANDALONE 2. userIds 3. name - STANDALONE (USERS ONLY, NOT for teams) 4. teamIds + teamsOnly 5. No parameters - LAST RESORT CRITICAL USAGE RULES: • userIds + teamIds requires explicit includeTeams: true flag • includeTeams: true fetches both users and teams, do not use this to fetch a specific user's teams rather fetch that user by id and you will get their team memberships. • name parameter is for USER search ONLY - it cannot be used to search for teams. Use teamIds to fetch specific teams.

list_workspaces

ChatGPT

List all workspaces available to the user, ordered by membership (user's workspaces first). Returns workspaces with their ID, name, and description. [IMPORTANT] To search for workspaces by name, use the "search" tool with searchType WORKSPACES instead — it provides faster and more accurate results.

manage_agent

ChatGPT

Full lifecycle management for monday platform agents — create, read, update, delete, change state, and run. monday platform agents are user-built work orchestrators on monday.com — each has a profile (name, role, avatar), a goal, and a markdown execution plan. Agents in state ACTIVE can be triggered automatically. They are NOT local LangChain or MCP agents. ACTIONS (only pass fields that apply to the chosen action): - create: { action:"create", prompt, agent_model? } — AI-generated agent. Platform creates profile, goal, and plan from the prompt. - create_blank: { action:"create_blank", name?, role?, role_description?, avatar_url?, gender?, background_color?, user_prompt? } — manually defined agent. - get one: { action:"get", agent_id } - list owned: { action:"get" } - update: { action:"update", agent_id, name?, role?, role_description?, plan?, agent_model? } - delete: { action:"delete", agent_id } - activate: { action:"activate", agent_id } - deactivate: { action:"deactivate", agent_id } - run: { action:"run", agent_id } RULES: - "create_blank" with no fields creates a nameless blank agent — only do this intentionally. - "update" requires at least one of name/role/role_description/plan/agent_model. - "update", "delete", "activate", "deactivate", "run" all require "agent_id". - Created agents start INACTIVE. Follow with action:"activate" using the returned agent_id before they can be triggered. - ⚠️ DESTRUCTIVE — "delete" is permanent and irreversible. When the user refers to an agent by name, ALWAYS call action:"get" first to confirm the correct agent_id before deleting. - "run" is fire-and-forget. Returns trigger_uuid — no run-status query exists, treat successful enqueue as the only signal. - Agent state is one of ACTIVE, INACTIVE, ARCHIVED, or FAILED. DELETED only appears as the return value of action:"delete". USAGE EXAMPLES: - AI create: { "action": "create", "prompt": "Run my daily standup every weekday at 9am." } - Manual create:{ "action": "create_blank", "name": "Standup Bot", "role": "Project Manager", "gender": "female" } - Fetch one: { "action": "get", "agent_id": "42" } - List mine: { "action": "get" } - Rename: { "action": "update", "agent_id": "7", "name": "New Name" } - Activate: { "action": "activate", "agent_id": "7" } - Deactivate: { "action": "deactivate", "agent_id": "7" } - Run: { "action": "run", "agent_id": "7" } - Delete: { "action": "delete", "agent_id": "7" } RELATED TOOLS: - agent_catalog — browse available trigger types and skills before wiring them to an agent - manage_agent_triggers — manage which triggers fire this agent automatically - manage_agent_skills — manage which skills this agent can perform - manage_agent_knowledge — manage which boards/docs this agent has access to

manage_agent_knowledge

ChatGPT

List, grant, update, or revoke a monday platform agent's access to boards and docs. An agent's "knowledge" is the set of monday.com boards and docs it can read from or write to during a run. - list: Returns all resources the agent currently has access to, including permission level and resource type. - add: Grants the agent access to a board or doc with the specified permission level. - update: Changes the permission level on a resource the agent already has access to. Call action:"list" first to confirm the resource_id exists. - remove: Revokes the agent's access to a board or doc entirely. Call action:"list" first to confirm the resource_id exists. Permission types: - READ: Agent can read data from the resource. - READ_WRITE: Agent can read and write data to the resource. USAGE EXAMPLES: - List: { "action": "list", "agent_id": "7" } - Add board access: { "action": "add", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD", "permission_type": "READ" } - Update to read-write: { "action": "update", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD", "permission_type": "READ_WRITE" } - Remove access: { "action": "remove", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD" } RELATED TOOLS: - manage_agent — manage the agent entity itself (create, activate, deactivate, etc.) - manage_agent_triggers — manage which triggers fire this agent automatically - manage_agent_skills — manage which skills this agent can perform

manage_agent_skills

ChatGPT

Manage the full skill lifecycle for monday platform agents — create new skills in the catalog, attach skills to an agent, or detach them. Skills extend what an agent can do (e.g. sending emails, querying databases, posting to Slack). ACTIONS: - create: { name, content, description? } — creates a new custom skill in the account-wide catalog. The skill becomes available to all agents in the account. - add: { agent_id, skill_id } — attaches a skill to this agent. - remove: { agent_id, skill_id } — detaches a skill from this agent. WORKFLOW — attach an existing skill: 1. Call agent_catalog action:"list_skills" — find the skill_id of the skill to attach. 2. Call this tool action:"add" with agent_id and that skill_id. WORKFLOW — create a new skill and attach it: 1. Call this tool action:"create" with name and content — note the returned id. 2. Call this tool action:"add" with agent_id and that id directly (no catalog lookup needed). NOTE: There is no action to list which skills are currently attached to a specific agent — the platform does not yet expose that query. To browse all skills available in the account catalog, use agent_catalog action:"list_skills". USAGE EXAMPLES: - Create a skill: { "action": "create", "name": "Send Slack Message", "content": "## Instructions\nPost a message to a Slack channel.", "description": "Sends a message to Slack" } - Add a skill: { "action": "add", "agent_id": "7", "skill_id": "skill-abc-123" } - Remove a skill: { "action": "remove", "agent_id": "7", "skill_id": "skill-abc-123" } RELATED TOOLS: - agent_catalog action:"list_skills" — browse existing skills to find a skill_id before calling action:"add" - manage_agent_triggers — manage which triggers fire this agent automatically - manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)

manage_agent_triggers

ChatGPT

Manage the triggers attached to a monday platform agent — triggers define WHEN the agent runs automatically. ACTIONS: - list: { agent_id } — returns active triggers with node_id, block_reference_id, name, field_summary. - add: { agent_id, block_reference_id, field_values? } — attaches a trigger type to the agent. - remove: { agent_id, node_id } — detaches a trigger instance by node_id (NOT block_reference_id). WORKFLOW — add a trigger: 1. Call agent_catalog action:"list_triggers" — note block_reference_id, field_schemas, and required_fields. 2. Collect required field values from the user (e.g. board_id, column_id). 3. Call this tool action:"add" with block_reference_id and field_values. Note: add returns only { success } — no node_id for the new instance. Call action:"list" afterward if you need the node_id. WORKFLOW — remove a trigger: 1. Call action:"list" to see active triggers and note the node_id of the instance to remove. 2. Call action:"remove" with that node_id. NOTE: Only triggers that can be added programmatically appear in the catalog. OAuth/3rd-party triggers (Slack, Gmail, Salesforce, etc.) require user setup in the monday.com UI — they will not appear in agent_catalog and cannot be managed here. USAGE EXAMPLES: - List triggers: { "action": "list", "agent_id": "7" } - Add trigger: { "action": "add", "agent_id": "7", "block_reference_id": "status-change-ref", "field_values": { "board_id": "42" } } - Remove trigger: { "action": "remove", "agent_id": "7", "node_id": "node-abc" } RELATED TOOLS: - agent_catalog action:"list_triggers" — discover available trigger types and their required field_values before calling action:"add" here - manage_agent_skills — manage which skills this agent can perform - manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)

manage_automations

ChatGPT

Activate, deactivate, or delete an existing monday.com automation. Requires an automation id. When the user refers to an automation by name, always call list_automations first to resolve the id — never guess or infer ids. Actions: - activate: enables a paused automation so it starts responding to its trigger. - deactivate: pauses an automation while preserving its definition. - delete: permanently removes an automation — irreversible. When intent is ambiguous ("stop", "turn off", "pause"), prefer deactivate over delete.

move_object

ChatGPT

Move a folder, board, or overview in monday.com. Use position for relative placement based on another object, parentFolderId for folder changes, workspaceId for workspace moves, and accountProductId for account product changes.

plan_workflow

ChatGPT

Plans one or more monday.com workflows for a described process using an AI agent. The agent analyzes the prompt, decides how many workflows are needed, identifies the required boards and columns, selects the correct trigger and action blocks (with their IDs), and returns a structured implementation plan with Mermaid diagrams and build notes for each workflow. Use this before create_workflow to understand how to break a complex process into individual workflows and which resources to create first. Parameters: - prompt: describe the full end-to-end process in plain English. Maximum 2000 characters. Returns: - result: structured markdown plan with workflow breakdowns, block IDs, resource definitions, and a list of assumptions and gaps

propose-crm-setup

ChatGPT

Set up, configure, or design a CRM of any kind (sales pipeline, clients, leads, deals, contacts, accounts) in monday.com, including a bare "set up a CRM" request or a question about which CRM setup fits a business. Propose a CRM board layout for a monday.com account — which boards to create, their purpose, pipeline stages, and tracked field areas — in the user's own vocabulary. Covers setting up, configuring, or restructuring a CRM of any kind: sales pipelines, client, lead, or deal tracking, industry CRMs such as real estate, recruiting, agency, or fundraising, and the structure of a CRM used elsewhere such as HubSpot or Salesforce. Also answers which CRM setup fits a business. Read-only: does not create or modify boards, items, or columns; build-crm-setup does that after the user has seen the proposal and approved it in a later message. Works from no context at all: a bare "set up a CRM" is enough to start. The tool runs its own short interview and designs the whole board set, so no clarifying questions beforehand and no board-by-board assembly with individual board tools are needed. Does not compare CRM vendors: "what is the best CRM?" is a product question, not a setup request, and a tailored setup can follow once the user wants one. Does not find or source new leads. Returns NEEDS_INFO with exactly one targeted question when the context is too thin for a useful proposal, the expected first result for a bare request; caps at three questions per conversation. Returns PROPOSAL with a board list and a setup_token once there is enough context, plus warnings for defaults used in place of missing answers and for common setup mistakes. To change a proposal the user has seen, call it again with its setup_token and refinements. A setup_token that expired within the last week still carries the answers, and the plan is regenerated for approval. Returns INVALID_TOKEN, without a token, when the supplied setup_token cannot be used; omit it to restart. Returns CRM_REQUIRED when monday CRM is not enabled on the account. Scope: this tool builds CRM structure only. It does not import records from another CRM, build pure project-delivery workflows, model nested client-of-client accounts, split one motion into product or regional pipelines, enforce per-assignee privacy, or undo created boards. Saved views, automations, and mirror columns are not created by this version. Phone-first and field-sales teams can use the boards but should skip the optional email connection. Email and calendar consent must be completed by the user in a browser. Importing contacts from Gmail into the Contacts board is optional, offered after the boards are built, and happens only if the user agrees to it. Use individual board tools or a manual setup for pure project delivery and nested client-account structures.

publish_workflow

ChatGPT

Publishes a workflow draft, promoting it to the live version. Use this after create_workflow (and optionally update_workflow) to make the workflow active. Before publishing, the workflow is validated — if it has missing or misconfigured steps, publish will fail with a WORKFLOW_VALIDATION_FAILED error that includes structured issue details: which step failed, the issue type, and which inputs are missing. Use those details to guide the user on what to fix before retrying. Parameters: - workflowObjectId and workflowDraftId: returned by create_workflow — they identify which draft to publish. - shouldActivate: whether to activate the workflow immediately after publish. Defaults to true — pass false to publish without activating. Returns: - workflowObjectId: the workflow object ID (unchanged) - workflowLiveId: the new live version ID — this changes on every publish, so do not cache it Note: if directing the user to the workflow in the UI, the correct URL path is custom_objects/, not workflows/ — e.g. {account}.monday.com/custom_objects/{workflowObjectId}.

read_docs

ChatGPT

Get information about monday.com documents. Supports two modes: MODE: "content" (default) — Fetch documents with their full markdown content. - Requires: type ("ids" | "object_ids" | "workspace_ids") and ids array - Supports pagination via page/limit. Check has_more_pages in response. - If type "ids" returns no results, automatically retries with object_ids. - Set include_blocks: true to include block IDs, types, and positions in the response — required before calling update_doc. - Blocks default to 25 per page. Use blocks_limit and blocks_page to paginate through long documents. - Set include_comments: true to fetch all comments and replies on the document. Each comment is enriched with anchor info (block_id, selection_from, selection_length) indicating which block and text range it's attached to. Use comments_limit to control how many comments per item (default 50). MODE: "version_history" — Fetch the edit history of a single document. - Requires: ids with the document's object_id (use the object_id field from content mode results, NOT the id field). - The object_id is the numeric ID visible in the document URL. - Returns restoring points sorted newest-first. Use version_history_limit to cap results (e.g., "last 3 changes" → version_history_limit: 3). - Use since/until to filter by time range. If omitted, returns full history. - Set include_diff: true to see what content changed between versions (fetches up to 10 diffs, may be slower). - Examples: - { mode: "version_history", ids: ["5001466606"], version_history_limit: 3 } - { mode: "version_history", ids: ["5001466606"], since: "2026-03-11T00:00:00Z", include_diff: true }

run_action

ChatGPT

Execute a saved action by ID. Optionally pass variables (injected as environment variables, access via os.environ). Example: id: "abc-123", vars: {"board_id": 12345, "limit": 5}

search

ChatGPT

Search within monday.com platform. Can search for boards, documents, folders, workspaces, updates, and items. For searching/listing specific users and teams, use list_users_and_teams tool. For account-level info (plan, member count, products), use get_user_context tool. For groups, use get_board_info tool. ITEMS search requires a searchTerm and only returns id, title, and url. WORKSPACES search requires a searchTerm and only returns id, title, and description. UPDATES search requires a searchTerm and returns id, title (the update body), itemId, boardId, and creatorId. Optionally scope it with boardIds and/or creatorIds. IMPORTANT: ids returned by this tool are prefixed with the type of the object (e.g doc-123, board-456, folder-789, workspace-101, update-303, item-321). When passing the ids to other tools, you need to remove the prefix and just pass the number.

search_meetings_content

ChatGPT

Search inside meeting content (topics, summary, action items) and return matching passages with their source area. Keyword-ranked (not semantic). When query is omitted, returns content filtered by date/access. Use to find where something was said or decided ("which meeting mentioned the budget freeze", "find the auth migration discussion"). Pass returned ids to get_meetings_content for full context.

show-assign

ChatGPT

[UI COMPONENT] Renders an interactive smart assignment interface visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Helps assign tasks to the right people. Assignment suggestions are based on task details (like name) and person details (such as title, availability, etc).Use for requests to see or use an interactive assignment interface. Always show as much as data possible, while showing the person details like title etc. If you do not have the data available - use the list_users_and_teams tool.

show-battery

ChatGPT

[UI COMPONENT] Renders an interactive battery/progress indicator visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks for: battery view, progress indicator, status distribution bar, completion percentage visualization, or Monday.com style status breakdown.

show-chart

ChatGPT

[UI COMPONENT] Renders an interactive chart/graph visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks for: pie chart, bar chart, line graph, data visualization, or any graphical representation of numbers/statistics.

show-monday

ChatGPT

Open the full monday.com web app in the ChatGPT sidebar. Opens the full monday.com web app for the current account. Launched from the ChatGPT sidebar.

show-table

ChatGPT

[UI COMPONENT] Renders an interactive table visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks to: display a board as table, show items in table format, view data in tabular layout, or see a Monday.com board visually. When asked to update an item, use the currently selected item ID (get it from the widget state, using tools like "get_widget_state") for deciding which item to update. If no item is selected, ask the user which item should be updated. After adding an update to an item, you MUST display the table AGAIN, even if the user did not ask you to. [IMPORTANT][FILTERING PRECONDITION]: IF using filters, you MUST call get_board_info(boardId) FIRST and use the returned boardContextToken.

submit_bug_or_feature_request

ChatGPT

Report a bug, submit a feature request, or share feedback about the monday.com product or this integration. Call this tool proactively — not just when a user explicitly asks. Use it whenever any of these signals show up: • A tool produced unexpected errors, empty results, or needed a workaround • The user tried something monday.com couldn't support and had to settle for a partial or manual solution • A recurring capability gap is noticed — something requested that simply isn't available in monday.com or this integration • The user shows repeated frustration (multiple corrections, retrying the same request, "that's wrong again," "why isn't this working") • A task required multiple retries, an unusually long reasoning chain, or many attempts for something that should've been simple Parameters: • title (string, required) — short summary, no PII • description (string, required) — full details of what happened/expected/requested, no PII • kind (enum, required) — "bug", "feature_request", or "feedback" • tool_name (string, optional) — the specific monday.com tool the feedback relates to (e.g. "create_item") Restriction: Use strictly for things related to monday.com — not for other tools (Google Drive, Slack, GitHub, etc.) that may be in the conversation context. Do NOT include any personally identifiable information (PII) such as names, email addresses, phone numbers, or any other personal data.

update_action

ChatGPT

Update an existing action. Only pass the fields you want to change. Example: id: "550e8400-e29b-41d4-a716-446655440000", name: "Updated name", code: "print('new code')"

update_column

ChatGPT

Update properties of an existing monday.com column (title, description, settings). [REQUIRED PRECONDITION]: Uses optimistic concurrency control via the revision field — fetch the column id, type, and current revision via get_board_schema first (preferred), or get_board_info if you already have it, then call this tool. If the update fails because the revision is stale, re-fetch and try again. After a successful update, use the new revision returned in the response for any further update to this column, not the one you started with. [REQUIRED PRECONDITION]: If you are changing columnSettings, also call get_column_type_info with fetchMode "schema" for that column type first to learn the valid settings structure. columnSettings is the flat payload for that column type (e.g. {"labels": [...]}) — not get_board_info's column.settings object copied as-is, and not wrapped again as {"settings": {"labels": [...]}}. To edit existing status or dropdown labels (rename, recolor, or reorder): first call get_board_info with filters.columns.ids for that column (or filters.columns.only) to read its current settings.labels, where each existing label's id lives. Editing an existing label requires sending its id in that label's entry — omitting it fails validation, since only a brand-new label can omit id. Status labels need the full label shape (id, label, color, index, and so on), not just a renamed string. Never invent an id — reuse the ids from get_board_info and add new labels without one. Flow: get_board_info for the revision and current settings.labels with ids, get_column_type_info (schema mode) for the valid shape, then build columnSettings.labels reusing existing ids and adding new labels without id.

update_doc

ChatGPT

Update an existing monday.com document. Provide doc_id (preferred) or object_id, plus an ordered operations array (executed sequentially, stops on first failure). OPERATIONS: - set_name: Rename the document. - add_markdown_content: Append markdown as blocks (or insert after a block). Best for text, headings, lists, simple tables — no block IDs needed. - update_block: Update content of an existing text, code, or list_item block in-place. - create_block: Create a new block at a precise position. Use parent_block_id to nest inside notice_box, table cell, or layout cell. - delete_block: Remove any block. The ONLY option for BOARD, WIDGET, DOC embed, and GIPHY blocks. - replace_block: Delete a block and create a new one in its place (use when update_block is not supported). - add_comment: Create a new comment or reply on the document (doc-level, block-level, or text-selection). WHEN TO USE EACH OPERATION: - text / code / list_item → update_block. Use replace_block to change subtype (e.g. NORMAL_TEXT→LARGE_TITLE) - divider / table / image / video / notice_box / layout → replace_block (properties immutable after creation) - BOARD / WIDGET / DOC / GIPHY → delete_block only GETTING BLOCK IDs: Call read_docs with include_blocks: true — returns id, type, position, and content per block. BLOCK CONTENT (delta_format): Array of insert ops. Last op MUST be {insert: {text: "\n"}}. - Plain: [{insert: {text: "Hello"}}, {insert: {text: "\n"}}] - Bold: [{insert: {text: "Hi"}, attributes: {bold: true}}, {insert: {text: "\n"}}] - Mention user/doc/board: [{insert: {text: "Hey "}}, {insert: {mention: {id: 12345, type: "USER"}}}, {insert: {text: "\n"}}] — type is USER, DOC, or BOARD. id is numeric (user IDs from list_users_and_teams) - Inline column value: [{insert: {column_value: {item_id: 111, column_id: "status"}}}, {insert: {text: "\n"}}] - Supported attributes: bold, italic, underline, strike, code, link, color, background (not applicable to mention/column_value ops) IMAGE WITH ASSET: For asset-based images, use create_block with block_type "image" and asset_id (instead of public_url). add_markdown_content does NOT support asset images — for mixed content, alternate add_markdown_content (text) and create_block (image) operations in sequence. COMMENTS: - add_comment: Create a new comment or reply on the document. Three scopes: - Doc-level (no block_id): comment appears on the doc as a whole. - Block-level (block_id only): comment is anchored to a specific block. The block shows a comment indicator in the UI. - Text-selection (block_id + selection_from + selection_length): comment is anchored to a specific character range inside a text/code/list_item block. That text is highlighted with a comment marker. Block-level and text-selection comments only work on blocks with text content (text, code, list_item, title, quote). They do NOT work on: divider, page_break, table, layout, notice_box, image, video, or giphy blocks. Get block IDs from read_docs with include_blocks: true. Format body with HTML, not markdown. Use mentions_list for @mentions.

update_folder

ChatGPT

Update an existing folder in monday.com

update_form

ChatGPT

Update a monday.com form. Use the action field to specify the operation.

update_items

ChatGPT

Update column values for up to 40 items in a single call. Each update targets one item by itemId and sets one or more column values on it. Each update is independent - it can target its own board via boardId and set its own column values, so a single call can update many items across multiple boards, apply the same value to many items, or apply different values per item. Each update returns its own item_id and item_url on success or a raw error message on failure. To link board-relation columns, call link_board_items_workflow before using this tool. [REQUIRED PRECONDITION]: Before using this tool, if you are not familiar with the board structure (column IDs, column types, status labels), first use get_board_info with filters.columns.only to get column metadata without fetching views. This is essential for constructing valid column values.

update_view

ChatGPT

Update an existing board view (tab) — change its name, filter rules, or sort order. Provide only the fields you want to change. Omitted fields are left unchanged. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text Example filter for people column: { "rules": [{ "column_id": "people", "compare_value": ["person-12345"], "operator": "any_of" }] } Example filter for status column: { "rules": [{ "column_id": "status", "compare_value": [1], "operator": "any_of" }] }

update_view_table

ChatGPT

Update an existing table-type board view — change its name, filters, sort, tags, or table-specific settings (column visibility/order and group-by). Provide only the fields you want to change. Omitted fields are left unchanged. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text Example settings.columns: { "column_properties": [{ "column_id": "status", "visible": true }], "column_order": ["name", "status", "date"] } Example settings.group_by: { "conditions": [{ "columnId": "status" }], "hideEmptyGroups": true }

update_workflow

ChatGPT

Updates an existing workflow draft using an AI agent. The agent interprets the prompt and applies structural changes to the workflow — creating, updating, or deleting steps. Pass clear, descriptive instructions and the agent will decide which operations to perform, then return a summary of what it did. Use this after create_workflow to build out the workflow step by step. You can call it multiple times on the same draft to iteratively refine the workflow. Parameters: - workflowObjectId and workflowDraftId: both returned by create_workflow — they identify which draft to update. - prompt: describe what you want to change in plain English (e.g. "Add a trigger that fires when an item is created on the Marketing board"). Maximum 2000 characters. Returns: - workflowObjectId: the workflow object ID (unchanged) - workflowDraftId: the draft version ID (unchanged) - result: agent response describing the changes made Note: if directing the user to the workflow in the UI, the correct URL path is custom_objects/, not workflows/ — e.g. {account}.monday.com/custom_objects/{workflowObjectId}. Note: the workflow runs only after it is published to live version.

update_workspace

ChatGPT

Update an existing workspace in monday.com

validate_workflow

ChatGPT

Validates the current workflow's structure and step configuration. Reports issues such as a missing trigger or action block, a delay/wait-trigger block left as a leaf, an empty loop, unknown blocks, missing required inputs, type mismatches between a variable and the field it's bound to, cross-branch node-results references, or invalid variable values. Use this tool when: - The user asks "is my workflow ready?", "what's missing?", "can I publish?", "validate my workflow", or similar. - After you finished structural changes, to confirm the user still has things to configure. - Before suggesting the user publish/activate the workflow. The tool does NOT modify the workflow. It only inspects the current state. The response is always a JSON object with an "issues" array; an empty array means the workflow is fully configured. Each issue has a "code" discriminator with code-specific fields, and (when applicable) is enriched with stepVisibleId, stepTitle, and blockName for human-readable context.

vibe_ask

ChatGPT

Ask a read-only question about an existing Vibe app. Blocks for up to 45s (configurable via timeout_ms) awaiting the assistant reply. Status: COMPLETED with the reply, TIMEOUT if the workflow did not finish in time (call vibe_get later to retrieve it), or FAILED if the workflow errored or was cancelled. Optional model to pick the LLM for the answer.

vibe_create

ChatGPT

Creates a new Vibe app from a natural-language prompt. Returns immediately with app_id and editor_link — the URL of the Vibe builder/chat page for the new app (https://{accountSlug}.monday.com/vibe/app/{appId}); the user can open it right away to watch generation in progress. Generation itself runs asynchronously — poll vibe_get for status. Optional: workspace_id to create the app in a specific workspace, board_ids to connect existing boards (omit to auto-create), view_id to host a dashboard widget, and model to pick the LLM.

vibe_delete

ChatGPT

Delete a Vibe app and its associated assets. Destructive.

vibe_get

ChatGPT

Fetch a Vibe app by id. App metadata is always returned, including editor_link — the URL of the Vibe builder/chat page for this app (https://{accountSlug}.monday.com/vibe/app/{appId}); usable as soon as the app row exists. Pass include to add expensive slices: status (refreshes status + adds is_busy, default true), messages (with optional from_date), code_versions.

vibe_list

ChatGPT

List Vibe apps owned by the authenticated user. Supports pagination, search, status, and is_published filters.

vibe_publication

ChatGPT

Manage the publication state of a Vibe app on the caller account. action=publish requires the app to be deployed and respects the published-apps license limit. action=unpublish removes the app from the account.

vibe_rename

ChatGPT

Rename a Vibe app and return the updated app.

vibe_update

ChatGPT

Sends a follow-up message to modify an existing app. Fire-and-forget — returns immediately with user_message_id and editor_link (the Vibe builder/chat URL for this app, https://{accountSlug}.monday.com/vibe/app/{appId}). Returns APP_BUSY (409) if the app is currently generating; poll vibe_get first. Optional model to pick the LLM for this build.

workspace_info

ChatGPT

This tool returns the boards, docs and folders in a workspace and which folder they are in. It returns up to 100 of each object type, if you receive 100 assume there are additional objects of that type in the workspace.

all_api_read

Claude

all_api_write

Claude

all_monday_api

Claude

board_insights

Claude

change_item_column_values

Claude

create-sequence

Claude

create-timeline-item

Claude

create_board

Claude

create_boards_and_projects

Claude

create_column

Claude

create_custom_activity

Claude

create_dashboard

Claude

create_dashboards_and_portfolios

Claude

create_doc

Claude

create_folder

Claude

create_form

Claude

create_forms_and_intake

Claude

create_item

Claude

create_items

Claude

create_items_and_tasks

Claude

create_notification

Claude

create_notifications_and_updates

Claude

create_timeline_item

Claude

create_update

Claude

create_workflow

Claude

create_workflow_instructions

Claude

create_workflows_and_approvals

Claude

create_workspace

Claude

delete_column

Claude

delete_item

Claude

fetch_custom_activity

Claude

get-timeline-items

Claude

get_assets

Claude

get_board_and_project_status_insights

Claude

get_board_items

Claude

get_board_items_by_name

Claude

get_board_schema

Claude

get_graphql_schema

Claude

get_monday_knowledge

Claude

get_type_details

Claude

get_updates

Claude

get_user_context

Claude

get_users_by_name

Claude

list_automations

Claude

list_users_and_teams

Claude

list_workspaces

Claude

manage_agent

Claude

move_item_to_group

Claude

move_object

Claude

read_docs

Claude

search

Claude

search_meetings_content

Claude

send_feedback

Claude

update_doc

Claude

update_items

Claude

update_items_owners_and_status

Claude

vibe_create

Claude

workspace_info

Claude

Capabilities

WritesInteractive

Example Prompts

Click any prompt to copy it.

Links

Documentation ↗Privacy Policy ↗

App Stats

172

Tools

Prompts

ChatGPT, Claude

Platforms