Create a new n8n workflow from a template, resolving node and credential dependencies automatically.
Import template as new workflow with dependency resolution
| Name | Required | Description | Default |
|---|---|---|---|
| templateId | Yes | Template ID to import | |
| importInactive | No | Import as inactive workflow (default: true) | |
| credentialMapping | No | Map template credential IDs to existing credentials | |
| skipNodeValidation | No | Skip checking if nodes exist (advanced) |
Changes observed during successful MCP inspections.
v2.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'dependency resolution' but does not explain what that entails, whether the imported workflow is created active or inactive by default, whether credential mapping is required, or what the tool returns on success. The description is too thin for a creation-type operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or redundant information. Every word contributes to conveying the core action and a key behavioral nuance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description should provide more context about return behavior, default import state, credential requirements, and failure modes. The vague 'dependency resolution' phrase does not fill those gaps, so the tool is not sufficiently described for an agent to invoke it with full confidence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents all four parameters with 100% coverage, so the baseline is 3. The description's 'dependency resolution' phrase gives some conceptual context for credentialMapping and skipNodeValidation, but it does not add substantial parameter-level detail beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Import template') and result ('as new workflow'), with the additional qualifier 'with dependency resolution' that separates it from generic workflow creation tools. It clearly identifies the tool's unique purpose among siblings like create_workflow and export_workflow_as_template.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool should be used when a user wants to instantiate a new workflow from a template, but it does not explicitly state when to prefer this over create_workflow or how it relates to search_templates/get_template_details. There is no guidance on when not to use it or what preconditions must be met.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.