Skip to main content
Glama

n8n_deactivate_workflow

Idempotent

Stop a workflow from listening to triggers to prevent automatic execution while preserving configuration. Use before making structural changes to workflows.

Instructions

Stop a workflow from listening to triggers. Deactivating prevents automatic execution but preserves workflow configuration. Use before making structure changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWorkflow ID to deactivate

Implementation Reference

  • The deactivateWorkflow method that executes the tool logic - makes a POST request to the n8n API endpoint /workflows/{id}/deactivate to stop a workflow from listening to triggers
    async deactivateWorkflow(id: string) {
      return this.request(`${this.apiBase}/workflows/${id}/deactivate`, {
        method: 'POST',
      });
    }
  • Tool definition for n8n_deactivate_workflow with inputSchema (requires workflow ID), description, and annotations (title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
    {
      name: 'n8n_deactivate_workflow',
      description: 'Stop a workflow from listening to triggers. Deactivating prevents automatic execution but preserves workflow configuration. Use before making structure changes.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Workflow ID to deactivate' },
        },
        required: ['id'],
      },
      annotations: {
        title: 'Deactivate Workflow',
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: true,
      },
    },
  • src/server.ts:37-38 (registration)
    Routing in handleToolCall function that maps 'n8n_deactivate_workflow' tool name to client.deactivateWorkflow(args.id) handler call
    case 'n8n_deactivate_workflow':
      return client.deactivateWorkflow(args.id);
Behavior4/5

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

Annotations already indicate this is a non-destructive, idempotent operation with open-world semantics. The description adds valuable context beyond this: it explains that deactivation 'prevents automatic execution but preserves workflow configuration,' clarifying the behavioral outcome. No contradictions with annotations exist.

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

Conciseness5/5

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

The description is extremely concise (two sentences) and front-loaded with the core purpose. Every sentence earns its place: the first defines the action and effect, the second provides usage guidance. No wasted words.

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?

Given the tool's moderate complexity (a state-change operation), rich annotations, and full schema coverage, the description is mostly complete. However, without an output schema, it doesn't clarify what the tool returns (e.g., success confirmation or updated workflow state), leaving a minor gap.

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?

The input schema has 100% description coverage, fully documenting the single 'id' parameter. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline for high schema coverage without extra value.

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?

The description clearly states the specific action ('Stop a workflow from listening to triggers') and resource ('workflow'), distinguishing it from siblings like n8n_activate_workflow (which does the opposite) and n8n_delete_workflow (which removes it entirely). It precisely defines what deactivation means in this context.

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?

The description provides clear context for when to use this tool ('Use before making structure changes'), but it doesn't explicitly mention when not to use it or name alternatives like n8n_activate_workflow for reactivation. The guidance is helpful but not fully comparative.

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/node2flow-th/n8n-management-mcp-community'

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