← Mintlify MCPCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Mintlify MCP
Snapshot Sep 30, 2026 · 22:48 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "managing-workflows",
"description": "Use when creating, updating, enabling, disabling, triggering, or debugging Mintlify Workflows (scheduled or push-triggered docs automations) through the Admin MCP, or when checking why a workflow run failed.",
"included_files": [],
"skill_md_contents": "---\nname: managing-workflows\ndescription: Use when creating, updating, enabling, disabling, triggering, or debugging Mintlify Workflows (scheduled or push-triggered docs automations) through the Admin MCP, or when checking why a workflow run failed.\n---\n\n# Managing Workflows\n\n## Overview\n\nWorkflows are deployment-level automations managed through code mode (`execute_code`) — no checkout needed, and changes apply to the live deployment immediately.\n\n**REQUIRED BACKGROUND:** read the `using-code-mode` skill first for script return semantics and `{ subdomain }` targeting.\n\n## Methods (namespace `workflows`)\n\n| Method | Notes |\n|--------|-------|\n| `listWorkflows({})` | All workflows on the deployment |\n| `getWorkflow({ workflowSchemaId })` | One workflow |\n| `createWorkflow({ name, on, ... })` | Enforces plan limits and trigger validation |\n| `updateWorkflow({ workflowSchemaId, ... })` | Dashboard validation path |\n| `setWorkflowEnabled({ workflowSchemaId, enabled })` | Enabling re-checks plan limits |\n| `triggerWorkflow({ workflowSchemaId })` | Manual run; enforces monthly run limits |\n| `deleteWorkflow({ workflowSchemaId })` | Soft delete |\n| `listWorkflowRuns({ workflowSchemaId?, status? })` | Run history, filterable |\n\nTriggers (`on`) are either push-based (`{ push: [{ repo, branch?, isDeploymentGitSource? }] }`, max 10 repos) or cron (`{ cron: '0 9 * * 1' }`). Fetch the exact current schema with `search_code_operations { query: 'create workflow', namespace: 'workflows' }` before creating — the full `inputSchema` comes back in the hit.\n\n## Example: find why runs are failing\n\n```\nconst wfs = await workflows.listWorkflows({});\nconst runs = await workflows.listWorkflowRuns({ status: 'failed' });\n({ workflows: wfs, failedRuns: runs });\n```\n\n## Common mistakes\n\n- Guessing the `createWorkflow` payload — it is a large validated union; pull the schema via `search_code_operations` first.\n- Forgetting these writes are live — disabling or deleting a workflow takes effect immediately.\n- Triggering repeatedly to \"retry\" — manual triggers count against monthly run limits.\n- Checking out an editor session first — workflows are code-mode, not session-scoped.\n"
}SHA-256: 25475acb369ea680a1c97b1cb52317ed7193bdb249ef283f33535bbb6e50a053