Publish Workflow (Platform MCP)
Publishes a workflow draft, promoting it to the live version so it starts running, using the Platform MCP.
Use this tool to publish a workflow draft, promoting it to the live version. Call it after create_workflow (and optionally update_workflow) to make the workflow active.
This tool runs against the monday.com dev (preview) API schema. Before publishing, the workflow is validated. If a step is missing or misconfigured, publish fails with a
WORKFLOW_VALIDATION_FAILEDerror that includes structured 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
| Parameter | Type | Required | Description |
|---|---|---|---|
| workflowObjectId | string | Yes | The workflow object ID returned by create_workflow. Identifies the workflow across all drafts and live versions. |
| workflowDraftId | string | Yes | The draft version ID to publish. Both workflowObjectId and workflowDraftId are required — together they identify the exact draft to publish. |
| shouldActivate | boolean | No | Whether to activate the workflow immediately after publishing so it starts running. Defaults to true. Pass false to publish without activating. |
Example
Publish a workflow draft and activate it:
{
"workflowObjectId": "12345",
"workflowDraftId": "67890",
"shouldActivate": true
}The tool returns workflowObjectId (unchanged) and workflowLiveId (the new live version ID). The live ID changes on every publish, so do not cache it.
Programmatic equivalent
This tool maps to the publish_workflow mutation on the monday.com dev (preview) API schema. There is no stable public GraphQL equivalent yet.
Updated about 4 hours ago
