This article provides a complete, practical walkthrough of the Code Webhook Create Webhook n8n agent. It connects Compare Datasets, Switch, If across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between Compare Datasets, Switch, If, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• Compare Datasets
• Switch
• If

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   How to Identify and Fix Affected n8n Workflows After Upgrading to Version 0.214.3
   
   Meta Description:  
   Upgraded to n8n v0.214.3 and worried about broken workflows? This custom n8n diagnostic workflow helps you identify potentially miswired nodes caused by output misconfigurations. Learn how to use this tool step-by-step.
   
   Keywords:  
   n8n, n8n workflow, workflow migration, n8n bug, n8n version 0.214.3, n8n fix, multi-output node, n8n automation, detect broken workflows, no-code automation
   
   Third-Party APIs Used:  
   - n8n API
   
   Article:
   
   ---
   
   # How to Identify and Fix Affected n8n Workflows After Upgrading to Version 0.214.3
   
   ## Introduction
   
   In the world of automation, keeping your systems up to date is not only a best practice—it's essential. However, occasionally, software updates can introduce unexpected issues. Such was the case with a specific version of n8n: v0.214.3. While this upgrade introduced new features and fixes, it also unintentionally caused a critical issue affecting workflows containing nodes with multiple outputs.
   
   Workflows that included nodes such as If, Switch, or Compare Datasets could have been rewired incorrectly during the update. If you’ve been impacted by this migration bug or simply want to ensure your workflows are in good health, this article walks you through a dedicated n8n diagnostic tool to detect these issues.
   
   ---
   
   ## What Happened in v0.214.3?
   
   A regression in version 0.214.3 affected how n8n stored and displayed connections between nodes with multiple outputs. Specifically:
   
   - Nodes like If (2 outputs), Switch (4 outputs), and Compare Datasets (4 outputs) might have lost some unconnected output indexes.
   - These missing outputs could result in broken logic or incomplete branch executions, regardless of whether the workflow continued “working.”
   
   ---
   
   ## Automated Workflow Checker: Overview
   
   A diagnostic workflow was developed to analyze all workflows in an n8n instance and flag any nodes that may have lost their multi-output connections. This tool generates an HTML report listing the affected workflows and nodes so administrators can manually review and fix them.
   
   ### Key Features
   
   - Uses the n8n API to retrieve all existing workflows.
   - Identifies nodes with multiple outputs that may have unintentional output gaps.
   - Generates an HTML report listing affected workflows and nodes.
   - Runs as a webhook, allowing you to trigger it conveniently via a URL.
   
   ---
   
   ## Step-by-Step Guide to Use the Diagnostic Workflow
   
   To run the check, follow the steps below:
   
   ### 1. Add Your API Credential
   Edit the "Get all workflows" node and add your n8n API key under settings. This allows the workflow to retrieve your instance's entire workflow list.
   
   > 📝 Navigate to Settings > n8n API to generate or copy your existing API token.
   
   ### 2. Customize the Code Node (Optional)
   If your instance includes community nodes that have multi-output capabilities, you should manually add them to the MULTI_OUTPUT_NODES constant in the "Parse potentially affected workflows" node.
   
   Example:
   ```javascript
   const MULTI_OUTPUT_NODES = [
     { type: 'n8n-nodes-base.compareDatasets', outputs: 4 }, 
     { type: 'n8n-nodes-base.switch', outputs: 4 }, 
     { type: 'n8n-nodes-base.if', outputs: 2 },
     { type: 'custom-nodes.myMultiOutput', outputs: 3 } // ← Example
   ];
   ```
   
   ### 3. Activate the Workflow
   Once configured, activate the workflow in your n8n instance so it can respond to incoming requests.
   
   ### 4. Access the Report
   Open a browser and navigate to:
   
   ```
   https://{YOUR_INSTANCE_URL}/webhooks/affected-workflows
   ```
   
   This triggers the workflow via the webhook node and returns a styled HTML report showing:
   
   - Affected workflow ID and name
   - A list of potentially affected multi-output nodes
   - Direct links to each workflow within your n8n instance for fast inspection
   
   ### 5. Inspect and Fix
   Click each listed workflow to open it in n8n. Manually verify that the outputs on flagged nodes are correctly connected.
   
   In some cases, you may need to reconnect outputs that were silently removed in the background during the upgrade.
   
   ---
   
   ## Technical Workflow Breakdown
   
   Here's how the diagnostic workflow functions at a high level:
   
   1. **Webhook Node**: Triggers the process via a dedicated URL.
   2. **Get All Workflows Node**: Uses the n8n API to fetch all workflows configured in your instance.
   3. **Code Node – Parse Affected Workflows**: Analyzes multi-output nodes within each workflow to identify any with missing connections.
   4. **HTML Node**: Generates a structured report in HTML format.
   5. **Respond to Webhook Node**: Returns the formatted report to the user in their browser.
   
   This modular, no-code solution makes leveraging the full capabilities of n8n’s extensibility and webhook support easy—even when debugging sensitive platform-wide issues.
   
   ---
   
   ## Output Example
   
   Once executed, the report might look like this:
   
   ```html
   Affected workflows:
   - ID: 129: Invoice Processing [if_1, switch_3]
   - ID: 137: Subscription Management [compareDatasets_1]
   ```
   
   Each item is clickable, redirecting you directly into the n8n visual editor for that workflow.
   
   ---
   
   ## Conclusion
   
   The n8n v0.214.3 update provided essential improvements, but like any complex system, unintended consequences can occur. This diagnostic workflow provides a neat, reliable way to perform instance-wide health checks, helping you maintain the integrity of your automated processes.
   
   If you've recently upgraded or are managing a large instance with many multi-output nodes, we highly recommend running this workflow. A few minutes now could prevent hours of debugging later.
   
   Stay productive—and automated—safely!
   
   ---
   
   ## Frequently Asked Questions
   
   ### Q: Is this workflow delete-safe?
   A: Yes. This workflow only reads data using the n8n API and does not modify any workflows.
   
   ### Q: Can I use this on a community edition without authentication?
   A: No. You must provide an API key with appropriate permissions.
   
   ### Q: Can I run this regularly?
   A: Yes. You could even automate it on a schedule via Cron to maintain ongoing diagnostics.
   
   ---
   
   By incorporating preventative tools like this post-upgrade validator, you're more prepared to manage the evolving landscape of workflow automation.
   
   Happy automating!

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.