Overview
Validate individual node configurations before adding them to workflows. Supports two validation modes (minimal and full) with four validation profiles for different use cases. Includes automatic structure validation for complex n8n types like filters and resource mappers. Performance: Fast (< 100ms)Parameters
Node type with prefix.Example:
"nodes-base.slack", "nodes-base.httpRequest"Configuration object to validate.For simple nodes, use
{}. For complex nodes, include fields like:Validation mode.
Validation profile for
mode="full".Response
The validated node type
Type to use in workflow JSON (e.g., “n8n-nodes-base.slack”)
Human-readable node name
Whether the configuration is valid
Array of error objects (only in
mode="full")Array of warning objects (only in
mode="full")Array of improvement suggestions (only in
mode="full")Array of missing required field names (only in
mode="minimal")Validation summary (only in
mode="full")Examples
Response Example (Full Mode)
Response Example (Minimal Mode)
Automatic Structure Validation
The validator automatically checks complex n8n type structures:Filter (FilterValue)
Filter (FilterValue)
Validates filter conditions with 40+ operations:
- Binary operators: equals, notEquals, contains, regex, etc.
- Unary operators: isEmpty, isNotEmpty, isTrue, isFalse
- Numeric operators: larger, smaller, between
- Array operators: includes, excludes
Resource Mapper (ResourceMapperValue)
Resource Mapper (ResourceMapperValue)
Validates data mapping configurations between systems.
Assignment Collection (AssignmentCollectionValue)
Assignment Collection (AssignmentCollectionValue)
Validates variable assignment collections.
Resource Locator (INodeParameterResourceLocator)
Resource Locator (INodeParameterResourceLocator)
Validates resource selection modes (id, name, url, list).
Use Cases
- Validate node configuration before adding to workflow
- Quick check for required fields during development (use
mode="minimal") - Pre-production validation with strict profile
- Validate complex structures (filters, resource mappers)
- Get suggestions for improving node configuration
Best Practices
Call get_node first
Call get_node first
Always call
get_node() first to understand what fields are required.Use minimal mode during development
Use minimal mode during development
For rapid iteration, use minimal mode for quick checks.
Use strict profile before production
Use strict profile before production
Before deploying to production, validate with strict profile.
Pay attention to warnings
Pay attention to warnings
Warnings often prevent runtime issues. Review them carefully.
Common Pitfalls
Validation Profile Comparison
| Profile | Checks Required | Checks Optional | Type Validation | Structure Validation | Best For |
|---|---|---|---|---|---|
| minimal | Yes | No | Basic | No | Quick checks |
| runtime | Yes | No | Yes | Yes | Development |
| ai-friendly | Yes | Partial | Yes | Yes | AI agents (default) |
| strict | Yes | Yes | Yes | Yes | Production |
Related Tools
get_node
Get node schema first
validate_workflow
Validate complete workflows
n8n_autofix_workflow
Auto-fix workflow issues