Skip to main content Skills Marketplace Descubra e explore skills de IA criadas pela comunidade.
Ocupações relacionadas SOC
Baseado na classificação ocupacional SOC
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Mostrar detalhes do prompt Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/BEKO2210/Firstbrain --skill n8n-validation-expertO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baixar Zip Baixando... name n8n-validation-expert description Expert guide for interpreting and fixing n8n validation errors. type skill created 2026-02-27T00:00:00.000Z domain productivity category automation risk unknown source community tags ["skill","productivity","automation","n8n","validation"]
n8n Validation Expert
Expert guide for interpreting and fixing n8n validation errors.
When to Use
You need to interpret or fix validation errors in an n8n workflow.
The task involves missing_required, invalid_value, expression failures, or iterative validate-fix loops.
You want concrete remediation guidance for workflow validation output.
Validation Philosophy
Validate early, validate often
Validation is typically iterative:
Expect validation feedback loops
Usually 2-3 validate → fix cycles
Average: 23s thinking about errors, 58s fixing them
Key insight : Validation is an iterative process, not one-shot!
Error Severity Levels
1. Errors (Must Fix)
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 error
Example :
{
"type" : "missing_required" ,
"property" : "channel" ,
"message" : "Channel name is required" ,
"fix" : "Provide a channel name (lowercase, no spaces, 1-80 characters)"
}
2. Warnings (Should Fix)
Doesn't block execution - Workflow can be activated but may have issues
Types :
best_practice - Recommended but not required
deprecated - Using old API/feature
performance - Potential performance issue{
"type" : "best_practice" ,
"property" : "errorHandling" ,
"message" : "Slack API can have rate limits" ,
"suggestion" : "Add onError: 'continueRegularOutput' with retryOnFail"
}
3. Suggestions (Optional) Nice to have - Improvements that could enhance workflow
optimization - Could be more efficientalternative - Better way to achieve same result
The Validation Loop
Pattern from Telemetry 7,841 occurrences of this pattern:
1. Configure node
↓
2. validate_node (23 seconds thinking about errors)
↓
3. Read error messages carefully
↓
4. Fix errors
↓
5. validate_node again (58 seconds fixing)
↓
6. Repeat until valid (usually 2-3 iterations)
Example
let config = {
resource : "channel" ,
operation : "create"
};
const result1 = validate_node ({
nodeType : "nodes-base.slack" ,
config,
profile : "runtime"
});
config.name = "general" ;
const result2 = validate_node ({
nodeType : "nodes-base.slack" ,
config,
profile : "runtime"
});
config.text = "Hello!" ;
const result3 = validate_node ({
nodeType : "nodes-base.slack" ,
config,
profile : "runtime"
});
This is normal! Don't be discouraged by multiple iterations.
Validation Profiles Choose the right profile for your stage:
minimal Use when : Quick checks during editing
Only required fields
Basic structure
Pros : Fastest, most permissive
Cons : May miss issues
runtime (RECOMMENDED) Use when : Pre-deployment validation
Required fields
Value types
Allowed values
Basic dependencies
Pros : Balanced, catches real errors
Cons : Some edge cases missed
This is the recommended profile for most use cases
ai-friendly Use when : AI-generated configurations
Same as runtime
Reduces false positives
More tolerant of minor issues
Pros : Less noisy for AI workflows
Cons : May allow some questionable configs
strict Use when : Production deployment, critical workflows
Everything
Best practices
Performance concerns
Security issues
Pros : Maximum safety
Cons : Many warnings, some false positives
Common Error Types
1. missing_required What it means : A required field is not provided
Use get_node to see required fields
Add the missing field to your configuration
Provide an appropriate value
{
"type" : "missing_required" ,
"property" : "channel" ,
"message" : "Channel name is required"
}
config.channel = "#general" ;
2. invalid_value What it means : Value doesn't match allowed options
Check error message for allowed values
Use get_node to see options
Update to a valid value
{
"type" : "invalid_value" ,
"property" : "operation" ,
"message" : "Operation must be one of: post, update, delete" ,
"current" : "send"
}
config.operation = "post" ;
3. type_mismatch What it means : Wrong data type for field
Check expected type in error message
Convert value to correct type
{
"type" : "type_mismatch" ,
"property" : "limit" ,
"message" : "Expected number, got string" ,
"current" : "100"
}
config.limit = 100 ;
4. invalid_expression What it means : Expression syntax error
Use n8n Expression Syntax skill
Check for missing {{}} or typos
Verify node/field references
{
"type" : "invalid_expression" ,
"property" : "text" ,
"message" : "Invalid expression: $json.name" ,
"current" : "$json.name"
}
config.text = "={{$json.name}}" ;
5. invalid_reference What it means : Referenced node doesn't exist
Check node name spelling
Verify node exists in workflow
Update reference to correct name
{
"type" : "invalid_reference" ,
"property" : "expression" ,
"message" : "Node 'HTTP Requets' does not exist" ,
"current" : "={{$node['HTTP Requets'].json.data}}"
}
config.expression = "={{$node['HTTP Request'].json.data}}" ;
Auto-Sanitization System
What It Does Automatically fixes common operator structure issues on ANY workflow update
n8n_create_workflown8n_update_partial_workflowAny workflow save operation
What It Fixes
1. Binary Operators (Two Values) Operators : equals, notEquals, contains, notContains, greaterThan, lessThan, startsWith, endsWith
Fix : Removes singleValue property (binary operators compare two values)
{
"type" : "boolean" ,
"operation" : "equals" ,
"singleValue" : true
}
{
"type" : "boolean" ,
"operation" : "equals"
}
2. Unary Operators (One Value) Operators : isEmpty, isNotEmpty, true, false
Fix : Adds singleValue: true (unary operators check single value)
{
"type" : "boolean" ,
"operation" : "isEmpty"
}
{
"type" : "boolean" ,
"operation" : "isEmpty" ,
"singleValue" : true
}
3. IF/Switch Metadata Fix : Adds complete conditions.options metadata for IF v2.2+ and Switch v3.2+
What It CANNOT Fix
1. Broken Connections References to non-existent nodes
Solution : Use cleanStaleConnections operation in n8n_update_partial_workflow
2. Branch Count Mismatches 3 Switch rules but only 2 output connections
Solution : Add missing connections or remove extra rules
3. Paradoxical Corrupt States API returns corrupt data but rejects updates
Solution : May require manual database intervention
False Positives
What Are They? Validation warnings that are technically "wrong" but acceptable in your use case
Common False Positives
1. "Missing error handling" Warning : No error handling configured
Simple workflows where failures are obvious
Testing/development workflows
Non-critical notifications
When to fix : Production workflows handling important data
2. "No retry logic" Warning : Node doesn't retry on failure
APIs with their own retry logic
Idempotent operations
Manual trigger workflows
When to fix : Flaky external services, production automation
3. "Missing rate limiting" Warning : No rate limiting for API calls
Internal APIs with no limits
Low-volume workflows
APIs with server-side rate limiting
When to fix : Public APIs, high-volume workflows
4. "Unbounded query" Warning : SELECT without LIMIT
Small known datasets
Aggregation queries
Development/testing
When to fix : Production queries on large tables
Reducing False Positives validate_node ({
nodeType : "nodes-base.slack" ,
config : {...},
profile : "ai-friendly"
})
Validation Result Structure
Complete Response {
"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
}
}
How to Read It
1. Check valid field if (result.valid ) {
} else {
}
2. Fix errors first result.errors .forEach (error =>console .log (`Error in ${error.property} : ${error.message} ` );
console .log (`Fix: ${error.fix} ` );
});
3. Review warnings result.warnings .forEach (warning =>console .log (`Warning: ${warning.message} ` );
console .log (`Suggestion: ${warning.suggestion} ` );
});
4. Consider suggestions
Workflow Validation
validate_workflow (Structure) Validates entire workflow , not just individual nodes
Node configurations - Each node validConnections - No broken referencesExpressions - Syntax and references validFlow - Logical workflow structure validate_workflow ({
workflow : {
nodes : [...],
connections : {...}
},
options : {
validateNodes : true ,
validateConnections : true ,
validateExpressions : true ,
profile : "runtime"
}
})
Common Workflow Errors
1. Broken Connections {
"error" : "Connection from 'Transform' to 'NonExistent' - target node not found"
}
Fix : Remove stale connection or create missing node
2. Circular Dependencies {
"error" : "Circular dependency detected: Node A → Node B → Node A"
}
Fix : Restructure workflow to remove loop
3. Multiple Start Nodes {
"warning" : "Multiple trigger nodes found - only one will execute"
}
Fix : Remove extra triggers or split into separate workflows
4. Disconnected Nodes {
"warning" : "Node 'Transform' is not connected to workflow flow"
}
Fix : Connect node or remove if unused
Recovery Strategies
Strategy 1: Start Fresh When : Configuration is severely broken
Note required fields from get_node
Create minimal valid configuration
Add features incrementally
Validate after each addition
Strategy 2: Binary Search When : Workflow validates but executes incorrectly
Remove half the nodes
Validate and test
If works: problem is in removed nodes
If fails: problem is in remaining nodes
Repeat until problem isolated
Strategy 3: Clean Stale Connections When : "Node not found" errors
n8n_update_partial_workflow ({
id : "workflow-id" ,
operations : [{
type : "cleanStaleConnections"
}]
})
Strategy 4: Use Auto-fix When : Operator structure errors
n8n_autofix_workflow ({
id : "workflow-id" ,
applyFixes : false
})
n8n_autofix_workflow ({
id : "workflow-id" ,
applyFixes : true
})
Best Practices
✅ Do
Validate after every significant change
Read error messages completely
Fix errors iteratively (one at a time)
Use runtime profile for pre-deployment
Check valid field before assuming success
Trust auto-sanitization for operator issues
Use get_node when unclear about requirements
Document false positives you accept
❌ Don't
Skip validation before activation
Try to fix all errors at once
Ignore error messages
Use strict profile during development (too noisy)
Assume validation passed (always check result)
Manually fix auto-sanitization issues
Deploy with unresolved errors
Ignore all warnings (some are important!)
Detailed Guides For comprehensive error catalogs and false positive examples:
ERROR_CATALOG.md - Complete list of error types with examplesFALSE_POSITIVES.md - When warnings are acceptable
Summary
Validation is iterative (avg 2-3 cycles, 23s + 58s)Errors must be fixed , warnings are optionalAuto-sanitization fixes operator structures automaticallyUse runtime profile for balanced validationFalse positives exist - learn to recognize themRead error messages - they contain fix guidance
Validate → Read errors → Fix → Validate again
Repeat until valid (usually 2-3 iterations)
Review warnings and decide if acceptable
Deploy with confidence
n8n MCP Tools Expert - Use validation tools correctly
n8n Expression Syntax - Fix expression errors
n8n Node Configuration - Understand required fields
Connections
Domain: [[Produktivitaet & Werkzeuge]]Kategorie: [[Automatisierung & Workflows]]Navigation: [[Skills Uebersicht]], [[Home]] 