mirror of
https://github.com/czlonkowski/n8n-mcp.git
synced 2026-03-19 00:43:07 +00:00
fe1e3640af
Previous fix attempted to whitelist settings properties, but research revealed that the n8n API update endpoint does NOT support updating settings at all. Root Cause: - n8n API rejects ANY settings properties in update requests - Properties like callerPolicy and executionOrder cannot be updated via API - See: https://community.n8n.io/t/api-workflow-update-endpoint-doesnt-support-setting-callerpolicy/161916 Solution: - Remove settings object entirely from update payloads - n8n API preserves existing settings when omitted from updates - Prevents "settings must NOT have additional properties" errors Changes: - src/services/n8n-validation.ts: Replace whitelist filtering with complete removal - tests/unit/services/n8n-validation.test.ts: Update tests to verify settings removal Testing: - All 72 unit tests passing (100% coverage) - Verified with n8n-mcp-tester on cloud workflow (n8n.estyl.team) Impact: - Workflow updates (name, nodes, connections) work correctly - Settings are preserved (not lost, just not updated) - Resolves all "settings must NOT have additional properties" errors 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>