Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, or the validation loop process.
npxskills add davila7/claude-code-templates--skill n8n-validation-expertLoading…
Expert guide for interpreting and fixing n8n validation errors.
Validate early, validate often
Validation is typically iterative:
Key insight: Validation is an iterative process, not one-shot!
Blocks workflow execution - Must be resolved before activation
Types:
missing_required - Required field not providedinvalid_value - Value doesn't match allowed optionstype_mismatch - Wrong data type (string instead of number)invalid_reference - Referenced node doesn't existinvalid_expression - Expression syntax errorExample:
{
"type": "missing_required",
"property": "channel",
"message": "Channel name is required",
"fix": "Provide a channel name (lowercase, no spaces, 1-80 characters)"
}
Doesn't block execution - Workflow can be activated but may have issues
Types:
best_practice - Recommended but not requireddeprecated - Using old API/featureperformance - Potential performance issueExample:
{
"type": "best_practice",
"property": "errorHandling",
"message": "Slack API can have rate limits",
"suggestion": "Add onError: 'continueRegularOutput' with retryOnFail"
}
Nice to have - Improvements that could enhance workflow
Types:
optimization - Could be more efficientalternative - Better way to achieve same result7,841 occurrences of this pattern:
1. Configure node
↓
2. validate_node_operation (23 seconds thinking about errors)
↓
3. Read error messages carefully
↓
4. Fix errors
↓
5. validate_node_operation again (58 seconds fixing)
↓
6. Repeat until valid (usually 2-3 iterations)
// Iteration 1
let config = {
resource: "channel",
operation: "create"
};
const result1 = validate_node_operation({
nodeType: "nodes-base.slack",
config,
profile: "runtime"
});
// → Error: Missing "name"
// ⏱️ 23 seconds thinking...
// Iteration 2
config.name = "general";
const result2 = validate_node_operation({
nodeType: "nodes-base.slack",
config,
profile: "runtime"
});
// → Error: Missing "text"
// ⏱️ 58 seconds fixing...
// Iteration 3
config.text = "Hello!";
const result3 = validate_node_operation({
nodeType: "nodes-base.slack",
config,
profile: "runtime"
});
// → Valid! ✅
This is normal! Don't be discouraged by multiple iterations.
Choose the right profile for your stage:
Use when: Quick checks during editing
Validates:
Pros: Fastest, most permissive Cons: May miss issues
Use when: Pre-deployment validation
Validates:
Pros: Balanced, catches real errors Cons: Some edge cases missed
This is the recommended profile for most use cases
Use when: AI-generated configurations
Validates:
Pros: Less noisy for AI workflows Cons: May allow some questionable configs
Use when: Production deployment, critical workflows
Validates:
Pros: Maximum safety Cons: Many warnings, some false positives
What it means: A required field is not provided
How to fix:
get_node_essentials to see required fieldsExample:
// Error
{
"type": "missing_required",
"property": "channel",
"message": "Channel name is required"
}
// Fix
config.channel = "#general";
What it means: Value doesn't match allowed options
How to fix:
get_node_essentials to see optionsExample:
// Error
{
"type": "invalid_value",
"property": "operation",
"message": "Operation must be one of: post, update, delete",
"current": "send"
}
// Fix
config.operation = "post"; // Use valid operation
What it means: Wrong data type for field
How to fix:
Example:
// Error
{
"type": "type_mismatch",
"property": "limit",
"message": "Expected number, got string",
"current": "100"
}
// Fix
config.limit = 100; // Number, not string
What it means: Expression syntax error
How to fix:
{{}} or typosExample:
// Error
{
"type": "invalid_expression",
"property": "text",
"message": "Invalid expression: $json.name",
"current": "$json.name"
}
// Fix
config.text = "={{$json.name}}"; // Add {{}}
What it means: Referenced node doesn't exist
How to fix:
Example:
// Error
{
"type": "invalid_reference",
"property": "expression",
"message": "Node 'HTTP Requets' does not exist",
"current": "={{$node['HTTP Requets'].json.data}}"
}
// Fix - correct typo
config.expression = "={{$node['HTTP Request'].json.data}}";
Automatically fixes common operator structure issues on ANY workflow update
Runs when:
n8n_create_workflown8n_update_partial_workflowOperators: equals, notEquals, contains, notContains, greaterThan, lessThan, startsWith, endsWith
Fix: Removes singleValue property (binary operators compare two values)
Before:
{
"type": "boolean",
"operation": "equals",
"singleValue": true // ❌ Wrong!
}
After (automatic):
{
"type": "boolean",
"operation": "equals"
// singleValue removed ✅
}
Operators: isEmpty, isNotEmpty, true, false
Fix: Adds singleValue: true (unary operators check single value)
Before:
{
"type": "boolean",
"operation": "isEmpty"
// Missing singleValue ❌
}
After (automatic):
{
"type": "boolean",
"operation": "isEmpty",
"singleValue": true // ✅ Added
}
Fix: Adds complete conditions.options metadata for IF v2.2+ and Switch v3.2+
References to non-existent nodes
Solution: Use cleanStaleConnections operation in n8n_update_partial_workflow
3 Switch rules but only 2 output connections
Solution: Add missing connections or remove extra rules
API returns corrupt data but rejects updates
Solution: May require manual database intervention
Validation warnings that are technically "wrong" but acceptable in your use case
Warning: No error handling configured
When acceptable:
When to fix: Production workflows handling important data
Warning: Node doesn't retry on failure
When acceptable:
When to fix: Flaky external services, production automation
Warning: No rate limiting for API calls
When acceptable:
When to fix: Public APIs, high-volume workflows
Warning: SELECT without LIMIT
When acceptable:
When to fix: Production queries on large tables
Use ai-friendly profile:
validate_node_operation({
nodeType: "nodes-base.slack",
config: {...},
profile: "ai-friendly" // Fewer false positives
})
{
"valid": false,
"errors": [
{
"type": "missing_required",
"property": "channel",
"message": "Channel name is required",
"fix": "Provide a channel name (lowercase, no spaces)"
}
],
"warnings": [
{
"type": "best_practice",
"property": "errorHandling",
"message": "Slack API can have rate limits",
"suggestion": "Add onError: 'continueRegularOutput'"
}
],
"suggestions": [
{
"type": "optimization",
"message": "Consider using batch operations for multiple messages"
}
],
"summary": {
"hasErrors": true,
"errorCount": 1,
"warningCount": 1,
"suggestionCount": 1
}
}
valid fieldif (result.valid) {
// ✅ Configuration is valid
} else {
// ❌ Has errors - must fix before deployment
}
result.errors.forEach(error => {
console.log(`Error in ${error.property}: ${error.message}`);
console.log(`Fix: ${error.fix}`);
});
result.warnings.forEach(warning => {
console.log(`Warning: ${warning.message}`);
console.log(`Suggestion: ${warning.suggestion}`);
// Decide if you need to address this
});
// Optional improvements
// Not required but may enhance workflow
Validates entire workflow, not just individual nodes
Checks:
Example:
validate_workflow({
workflow: {
nodes: [...],
connections: {...}
},
options: {
validateNodes: true,
validateConnections: true,
validateExpressions: true,
profile: "runtime"
}
})
{
"error": "Connection from 'Transform' to 'NonExistent' - target node not found"
}
Fix: Remove stale connection or create missing node
{
"error": "Circular dependency detected: Node A → Node B → Node A"
}
Fix: Restructure workflow to remove loop
{
"warning": "Multiple trigger nodes found - only one will execute"
}
Fix: Remove extra triggers or split into separate workflows
{
"warning": "Node 'Transform' is not connected to workflow flow"
}
Fix: Connect node or remove if unused
When: Configuration is severely broken
Steps:
get_node_essentialsWhen: Workflow validates but executes incorrectly
Steps:
When: "Node not found" errors
Steps:
n8n_update_partial_workflow({
id: "workflow-id",
operations: [{
type: "cleanStaleConnections"
}]
})
When: Operator structure errors
Steps:
n8n_autofix_workflow({
id: "workflow-id",
applyFixes: false // Preview first
})
// Review fixes, then apply
n8n_autofix_workflow({
id: "workflow-id",
applyFixes: true
})
runtime profile for pre-deploymentvalid field before assuming successget_node_essentials when unclear about requirementsstrict profile during development (too noisy)For comprehensive error catalogs and false positive examples:
Key Points:
Validation Process:
Related Skills:
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).