Found by n8n-mcp-tester agent: IF nodes in n8n store connections as:
IF.main[0] (true branch)
IF.main[1] (false branch)
NOT as IF.true and IF.false
Previous implementation (WRONG):
- branch='true' → sourceOutput='true'
Correct implementation (FIXED):
- branch='true' → sourceIndex=0, sourceOutput='main'
- branch='false' → sourceIndex=1, sourceOutput='main'
Changes:
- resolveSmartParameters(): branch now sets sourceIndex, not sourceOutput
- Type definition comments updated to reflect correct mapping
- All unit tests fixed to expect connections under 'main' with correct indices
- All 141 tests passing with correct behavior
This was caught by integration testing against real n8n API, not by unit tests.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add intuitive semantic parameters for working with IF and Switch nodes:
- branch='true'|'false' for IF nodes (maps to sourceOutput)
- case=N for Switch nodes (maps to sourceIndex)
- Smart parameters resolve to technical parameters automatically
- Explicit parameters always override smart parameters
Implementation:
- Added branch and case parameters to AddConnectionOperation and RewireConnectionOperation interfaces
- Created resolveSmartParameters() helper method to map semantic to technical parameters
- Updated applyAddConnection() to use smart parameter resolution
- Updated applyRewireConnection() to use smart parameter resolution
- Updated validateRewireConnection() to validate with resolved smart parameters
Tests:
- Added 8 comprehensive tests for smart parameters feature
- All 141 workflow diff engine tests passing
- Coverage: 91.7% overall
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Fixes#270
## Problem
Connection operations (addConnection, removeConnection, etc.) failed when node
names contained special characters like apostrophes, quotes, or backslashes.
Default n8n Manual Trigger node: "When clicking 'Execute workflow'" caused:
- Error: "Source node not found: \"When clicking 'Execute workflow'\""
- Node shown in available nodes list but string matching failed
- Users had to use node IDs as workaround
## Root Cause
The `findNode()` method in WorkflowDiffEngine performed exact string matching
without normalization. When node names contained special characters, escaping
differences between input strings and stored node names caused match failures.
## Solution
### 1. String Normalization (Primary Fix)
Added `normalizeNodeName()` helper method:
- Unescapes single quotes: \' → '
- Unescapes double quotes: \" → "
- Unescapes backslashes: \\ → \
- Normalizes whitespace
Updated `findNode()` to normalize both search string and node names before
comparison, while preserving exact UUID matching for node IDs.
### 2. Improved Error Messages
Enhanced validation error messages to show:
- Node IDs (first 8 characters) for quick reference
- Available nodes with both names and ID prefixes
- Helpful tip about using node IDs for special characters
### 3. Comprehensive Tests
Added 6 new test cases covering:
- Apostrophes (default Manual Trigger scenario)
- Double quotes
- Backslashes
- Mixed special characters
- removeConnection with special chars
- updateNode with special chars
All tests passing: 116/116 in workflow-diff-engine.test.ts
### 4. Documentation
Updated tool documentation to note:
- Special character support since v2.15.6
- Node IDs preferred for best compatibility
## Affected Operations
All 8 operations using findNode() now support special characters:
- addConnection, removeConnection, updateConnection
- removeNode, updateNode, moveNode
- enableNode, disableNode
## Testing
Validated with n8n-mcp-tester agent:
✅ addConnection with apostrophes works
✅ Default Manual Trigger name works
✅ Improved error messages show IDs
✅ Double quotes handled correctly
✅ Node IDs work as alternative
## Impact
- Fixes common user pain point with default n8n node names
- Backward compatible (only makes matching MORE permissive)
- Minimal performance impact (normalization only during validation)
- Centralized fix (one method fixes all 8 operations)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Issue #248: Settings validation error
- Add callerPolicy to workflowSettingsSchema to support valid n8n property
- Implement settings filtering in cleanWorkflowForUpdate() to prevent API errors
- Filter out UI-only properties like timeSavedPerExecution
- Preserve only whitelisted settings properties
- Add comprehensive unit tests for settings filtering
Issue #249: Misleading error messages for addConnection
- Enhanced validateAddConnection() with parameter validation
- Detect common mistakes like using sourceNodeId/targetNodeId instead of source/target
- Provide helpful error messages with correct parameter names
- List available nodes when source/target not found
- Add unit tests for all error scenarios
All tests passing (183 total):
- n8n-validation: 73/73 tests (100% coverage)
- workflow-diff-engine: 110/110 tests
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Implements 4 new features for n8n_update_partial_workflow:
New Operations:
- cleanStaleConnections: Auto-remove broken workflow connections
- replaceConnections: Replace entire connections object in one operation
Enhanced Features:
- removeConnection ignoreErrors flag: Graceful cleanup without failures
- continueOnError mode: Best-effort batch operations with detailed tracking
Impact:
- Reduces broken workflow fix time from 10-15 minutes to 30 seconds
- Token efficiency: 1 cleanStaleConnections vs 10+ manual operations
- 15 new tests added, all passing
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
The 5-operation limit was overly conservative and unnecessary. Analysis showed:
- Workflow is cloned before modifications (no original mutation)
- All operations validated before any are applied (true atomicity)
- First error causes immediate return (no partial state possible)
- Two-pass processing handles dependencies correctly
Changes:
- Remove hard-coded 5-operation limit check from workflow-diff-engine.ts
- Update tool descriptions and documentation to reflect unlimited operations
- Add tests verifying 50 and 100+ operations work successfully
- Add example showing 26 operations in single request
The system already ensures complete transactional integrity regardless of
operation count. Bottleneck is workflow size, not operation count.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Changed UpdateNodeOperation interface to use 'updates' instead of 'changes'
- Updated UpdateConnectionOperation for consistency
- Fixed implementation in workflow-diff-engine.ts
- Updated Zod schema validation
- Fixed documentation and examples
- Updated tests to match new property name
This resolves GitHub issues #159 and #168 where partial workflow updates
were failing, forcing AI agents to fall back to expensive full updates.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
