Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create Workflow

create_workflow

Create a new empty workflow in a monday.com workspace. Define title, privacy, owners, and folder, then publish to activate.

Instructions

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}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesThe ID of the workspace to create the workflow in.
titleNoWorkflow title. Defaults to "New Workflow" if not provided.
privacyKindNoWorkflow visibility: PUBLIC (default), PRIVATE, or SHAREABLE (accessible to guests outside the account).
descriptionNoOptional workflow description.
folderIdNoOptional folder ID to place the workflow in.
ownerIdsNoOptional list of user IDs to set as workflow owners.

Tool Definition Quality

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds value beyond annotations by explaining return values (workflowObjectId, workflowDraftId), workflow lifecycle (drafts must be published), and terminology. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and usage, includes helpful terminology and UI note. Slightly verbose but every section adds value; could be trimmed slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers return values, draft concept, alternative tools, and UI URL. Lacks permission/error details but appropriate for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds minor context (e.g., defaults, privacy descriptions) but does not significantly enhance parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Creates a new empty workflow' and distinguishes from sibling 'create_automation' by explaining workflows are standalone workspace-level objects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this when the user wants to build a new standalone workflow from scratch' and contrasts with automations, providing strong usage guidance. Lacks explicit 'do not use' scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mondaycom/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server