N8N WORKFLOW ANALYSIS — EXECUTED LOCAL EXAMPLE Jamil Fayad | Personal productivity project Execution: 2026-10-30T14:19:58.693287+00:00 Walkthrough: https://jamilfayad.com/projects/n8n-workflow-autofix.html INPUT AND METHOD Sanitized copy of an existing generated Security Infrastructure Automation Workflow. 16 nodes. Seven sensitive fields replaced with non-secret placeholders. Sanitized input SHA-256: f9eb85dac8933da2b2d7eb42d84a2ccea7793590651af794e96c494b4cc82065 Original analyzer and schema fixer modules imported unchanged. Sequence: analyze_workflow -> apply_schema_fixes -> analyze_workflow. No model call, n8n API call, workflow activation or external workflow action. OBSERVED OUTPUT 11 findings before; 5 schema edits; 6 findings after; 16 nodes retained. Edits: remove active; remove versionId; remove the credential binding from Store Compliance Results; remove the credential binding from Log Event; add missing pinData. REMAINING FINDINGS AND REVIEW One informational error-handling finding spanning ten nodes. Four informational warnings on HTTP nodes with absent authentication fields. One critical-labelled credential heuristic matching the headerAuth mode string. That mode-name match does not demonstrate an exposed secret. Header-based authentication requires separate validation; absent authentication fields do not prove that every request is unauthenticated. Removing credential bindings can break a valid workflow. These edits are not independently established security repairs or official n8n import requirements. SEPARATE DIAGNOSTIC FIXTURE Four HTTP authentication fields were explicitly set to the literal string "none". The missing-authentication check tests truthiness and missed these settings. The credential heuristic instead produced false-positive labels for mode strings. This was a separate diagnostic input, not the unchanged primary workflow. LIMITATIONS This is a personal tool execution, not a client case study. No n8n runtime import/execution, production deployment or business outcome verified. Python 3.13.3 and NetworkX 2.6.3 were used. The tool declares NetworkX >=3.1.0; this proves the selected local execution, not a matching full-app environment. Counts are tool findings and edits, not vulnerabilities fixed or measured savings. Official export/import guidance: https://docs.n8n.io/workflows/export-import/