Configuration Tools

Get detailed node information and template configurations. Access node schemas, documentation, version history, and complete workflow templates.

`get_node`

Unified node information tool with progressive detail levels and multiple modes. Get node schema, documentation, search properties, or version information.

No Setup Required

Parameter	Type	Default	Description
`nodeType`*	`string`	—	Full node type: "nodes-base.httpRequest" or "nodes-langchain.agent"
`detail`	`string`	`standard`	Detail level `minimalstandardfull`
`mode`	`string`	`info`	Operation mode `infodocssearch_propertiesversionscomparebreakingmigrations`
`includeTypeInfo`	`boolean`	`false`	Include type structure metadata (+80-120 tokens per property)
`includeExamples`	`boolean`	`false`	Include real-world template examples (+200-400 tokens per example)
`propertyQuery`	`string`	—	For mode=search_properties: search term
`maxPropertyResults`	`number`	`20`	For mode=search_properties: max results
`fromVersion`	`string`	—	For compare/breaking/migrations: source version
`toVersion`	`string`	—	For compare mode: target version

Standard detail (recommended)

javascript

get_node({nodeType: "nodes-base.httpRequest"})

Minimal for quick metadata check

javascript

get_node({nodeType: "nodes-base.slack", detail: "minimal"})

Full detail with examples

javascript

get_node({nodeType: "nodes-base.googleSheets", detail: "full", includeExamples: true})

Get readable documentation

javascript

get_node({nodeType: "nodes-base.webhook", mode: "docs"})

Search for authentication properties

javascript

get_node({nodeType: "nodes-base.httpRequest", mode: "search_properties", propertyQuery: "auth"})

Compare specific versions

javascript

get_node({nodeType: "nodes-base.httpRequest", mode: "compare", fromVersion: "3.0", toVersion: "4.1"})

Use Cases

•Configure nodes for workflow building (use detail=standard)
•Find specific configuration options (use mode=search_properties)
•Get human-readable node documentation (use mode=docs)
•Check for breaking changes before version upgrades (use mode=breaking)
•Understand complex types with includeTypeInfo=true

✓Best Practices

•Start with detail="standard" - it covers 95% of use cases
•Only use detail="full" if standard is missing required properties
•Use mode="docs" when explaining nodes to users
•Check version history before configuring versioned nodes

Common Pitfalls

•detail="full" returns large responses (~100KB) - use sparingly
•Node type must include prefix (nodes-base. or nodes-langchain.)
•includeExamples only works with mode=info and detail=standard
•Version modes require nodes with multiple versions in database

`get_template`

Get workflow template by ID with configurable detail level. The returned workflow can be directly imported into n8n through the UI or API.

No Setup Required

Parameter	Type	Default	Description
`templateId`*	`number`	—	The numeric ID of the template (get IDs from search_templates)
`mode`	`string`	`full`	Response detail `nodes_onlystructurefull`

Get complete workflow (default)

javascript

get_template({templateId: 1234})

Get just the node list

javascript

get_template({templateId: 1234, mode: "nodes_only"})

Get nodes and connections

javascript

get_template({templateId: 1234, mode: "structure"})

Use Cases

•Download workflows for direct import into n8n
•Study workflow patterns and best practices
•Get complete workflow JSON for customization
•Clone popular workflows for your use case

✓Best Practices

•Use search_templates first to find the right template ID
•Use mode="nodes_only" for quick overview
•Use mode="full" when you need to import or analyze the workflow

Common Pitfalls

•Template IDs may change when database is refreshed
•Some templates may use deprecated node versions
•Credentials in templates are placeholders - configure your own