Skip to main content
Glama

n8n_activate_workflow

Activate an n8n workflow to enable automated processes by making it ready for triggering through its configured nodes.

Instructions

Activate a workflow so it can be triggered. The workflow must have a valid trigger node.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe workflow ID to activate

Implementation Reference

  • The handler function that executes the n8n_activate_workflow tool. Validates the workflow ID, calls the N8nApiClient to activate the workflow, and returns a formatted success response.
    n8n_activate_workflow: async (
      client: N8nApiClient,
      args: Record<string, unknown>
    ): Promise<ToolResult> => {
      const id = args.id as string;
      if (!id) {
        throw new Error('Workflow ID is required');
      }
    
      const workflow = await client.activateWorkflow(id);
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify({
              success: true,
              message: `Workflow "${workflow.name}" activated successfully`,
              workflow: {
                id: workflow.id,
                name: workflow.name,
                active: workflow.active,
              },
            }, null, 2),
          },
        ],
      };
    },
  • The tool schema definition specifying the name, description, and input schema (requires 'id' string) for the n8n_activate_workflow tool.
    {
      name: 'n8n_activate_workflow',
      description: 'Activate a workflow so it can be triggered. The workflow must have a valid trigger node.',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'The workflow ID to activate',
          },
        },
        required: ['id'],
      },
    },
  • src/server.ts:122-125 (registration)
    The runtime registration/dispatch logic in the MCP server that checks if the tool name exists in workflowToolHandlers and invokes the corresponding handler with the API client.
    if (name in workflowToolHandlers) {
      const handler = workflowToolHandlers[name as keyof typeof workflowToolHandlers];
      return handler(client, args);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the prerequisite of a 'valid trigger node' but fails to address critical aspects such as whether this operation requires specific permissions, what happens if activation fails, whether it's reversible, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with only two sentences, both of which are essential: the first states the core action, and the second adds a crucial prerequisite. There is no wasted language, and the information is front-loaded effectively, making it easy to grasp quickly.

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

Completeness3/5

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

Given the tool's complexity as a mutation operation with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose and a key prerequisite but lacks details on behavioral traits, error handling, or return values. While it meets a minimum threshold, it doesn't fully compensate for the absence of structured data, leaving room for improvement in completeness.

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, with the 'id' parameter clearly documented as 'The workflow ID to activate.' The description doesn't add any additional meaning beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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

Purpose4/5

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

The description clearly states the action ('Activate a workflow') and the resource ('workflow'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'n8n_deactivate_workflow' or 'n8n_update_workflow' beyond the obvious activation vs. deactivation distinction.

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

Usage Guidelines3/5

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

The description provides some contextual guidance by mentioning that 'The workflow must have a valid trigger node,' which implies a prerequisite for usage. However, it doesn't offer explicit guidance on when to use this tool versus alternatives like 'n8n_deactivate_workflow' or 'n8n_update_workflow,' nor does it specify any exclusions or edge cases.

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/alicankiraz1/cursor-n8n-builder'

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