Skip to main content
Glama

n8n_create_workflow

Create a new workflow in n8n by defining nodes and connections to automate tasks and integrate systems.

Instructions

Create a new workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWorkflow name
nodesYesArray of workflow nodes
connectionsNoNode connections
settingsNoWorkflow settings
activeNoWhether workflow is active

Implementation Reference

  • The MCP request handler case for 'n8n_create_workflow', which calls the n8nClient.createWorkflow method.
    case 'n8n_create_workflow': {
      if (!args?.name || !args?.nodes) {
        throw new Error('name and nodes are required');
      }
      const result = await n8nClient.createWorkflow(args);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The n8nClient method that performs the actual POST request to the n8n API to create a workflow.
    async createWorkflow(data: any): Promise<any> {
      const response = await this.client.post('/workflows', data);
      return response.data;
    }
  • src/index.ts:468-481 (registration)
    The tool definition and input schema registration for 'n8n_create_workflow'.
      name: 'n8n_create_workflow',
      description: 'Create a new workflow',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Workflow name' },
          nodes: { type: 'array', description: 'Array of workflow nodes' },
          connections: { type: 'object', description: 'Node connections' },
          settings: { type: 'object', description: 'Workflow settings' },
          active: { type: 'boolean', description: 'Whether workflow is active' },
        },
        required: ['name', 'nodes'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but discloses minimal behavioral details. It states 'Create' implying mutation, but lacks information about what gets returned (workflow ID? full object?), validation rules for unique names, or potential side effects like automatic tagging or default settings assignment.

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

Conciseness3/5

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

At three words, the description is technically concise, but it represents under-specification rather than efficient communication. For a tool with 5 parameters including complex nested objects (nodes, connections), the length is inappropriately brief—every word earns its place only because there are so few of them.

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

Completeness2/5

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

Given the complexity (nested objects for nodes/connections, boolean activation state) and lack of output schema, the description fails to provide sufficient context. It doesn't hint at the n8n-specific domain (automation workflows), expected node structures, or what distinguishes a successful creation from a validation error.

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 description coverage is 100%, establishing a baseline of 3. However, the description adds no semantic value beyond the schema—it doesn't explain that 'nodes' refers to n8n automation steps, what structure 'connections' expects (likely a mapping of node IDs), or what valid 'settings' properties are available.

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

Purpose2/5

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

The description 'Create a new workflow' is tautological—it simply restates the tool name 'n8n_create_workflow' without adding specificity. While it identifies the resource (workflow) and action (create), it fails to distinguish from siblings like 'n8n_update_workflow' or clarify scope within the n8n automation platform.

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

Usage Guidelines2/5

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

No guidance provided on when to use this versus 'n8n_update_workflow' (for existing workflows) or prerequisites like requiring a project to exist first. No mention of whether the workflow can be created as active immediately or if 'n8n_activate_workflow' must be called separately.

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/Shravan1610/n8n-mcp-server'

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