Identify Potentially Affected Workflows After n8n Upgrade
Summary
This workflow helps n8n administrators detect workflows that may have been incorrectly rewired during the n8n version 0.214.3 migration. The migration inadvertently reconnected nodes with multiple outputs (e.g., If, Switch, Compare Datasets) in a way that could cause skipped branches. By scanning all workflows via the n8n API and analyzing connection patterns, the workflow generates an HTML report listing every potentially affected workflow with a direct link to inspect and fix it.
How It Works
- Webhook (No auth) — Starts the workflow when you visit
{YOUR_INSTANCE_URL}/webhooks/affected-workflows. No authentication is required for this webhook endpoint. - Get all workflows (API Key auth) — Uses an n8n API credential to fetch all workflows on the instance. The credentials must be an n8n API key created in Settings → n8n API.
- Parse potentially affected workflows (No auth) — A Code node runs JavaScript that iterates through each workflow's nodes and connections. It checks whether any known multi-output node type (If, Switch, Compare Datasets) has fewer connected outputs than expected. If a connection is missing (likely due to the migration bug), it marks the workflow as affected.
- Generate Report (No auth) — An HTML node defines a styled static page with a header and an empty
<ul>list. - Serve HTML Report (No auth) — The
Respond to Webhooknode injects the parsed affected workflows into the HTML template and sends the complete page back to the browser. The page contains clickable links to each affected workflow for quick review.
Setup Instructions
- Generate an n8n API Key — Go to Settings → n8n API and create a new API key. Copy the key.
- Create an n8n API credential — In n8n, go to Credentials → New → n8n API. Paste your API key. Name it (e.g., “n8n Admin”).
- Configure the “Get all workflows” node — Open the node and select the credential you just created. Leave filters empty to scan all workflows.
- (Optional) Add community nodes — If you have community nodes that also have multiple outputs (e.g., a custom router), edit the
MULTI_OUTPUT_NODESarray in the Parse potentially affected workflows Code node to include them. - Activate the workflow — Turn on the workflow activation toggle.
- Run the check — Open your browser and navigate to
https://{your-n8n-instance}/webhooks/affected-workflows. The report will appear immediately.
Use Cases & Customization
- Post-upgrade validation — Run this after any n8n upgrade to catch broken connections early.
- Workflow audit — Modify the Code node to detect other common misconfigurations (e.g., orphaned nodes, incorrect credentials).
- Alert integration — Replace the HTML report with a Slack message or email notification to alert the team automatically.
- Scheduled checks — Add a Schedule trigger to run this daily and send the report via webhook or email.
Workflow JSON
{
"meta": {
"instanceId": "ef45cd7f45f7589c4c252d786d5d1a3233cdbfc451efa7e17688db979f2dc6ae"
},
"nodes": [
{
"id": "b83bfb2d-6d1b-4984-8fc4-6cf0a35309dc",
"name": "Sticky Note",
"type": "n8n-nodes-base.stickyNote",
"position": [
1380,
960
],
"parameters": {
"width": 1074,
"height": 468,
"content": "# ⚠️ When and how to use this workflow\n\nIf you previously upgraded to n8n version `0.214.3`, some of your workflows might have accidentally been re-wired in the wrong way. This affected nodes which have more than 1 output, such as `If`, `Switch`, and `Compare Datasets`.\n\nThis workflow helps you identify potentially affected workflows and nodes that you should check.\n\n**❗️Please ensure to run this workflow as the instance owner❗️**\n\n1. Configure the \"Get all workflows\" node to use your n8n API key. (You can find/create your API key under \"Settings > n8n API\")\n2. If you have community nodes installed that have more than 1 output, add them to the constant `MULTI_OUTPUT_NODES` in the \"Parse potentially affected workflows\" code node.\n3. Activate the workflow\n4. Visit `{YOUR_INSTANCE_URL}/webhooks/affected-workflows` from your browser\n5. The report will list potentially affected workflows/nodes.\n 1. The square brackets after the workflow name list the potentially affected nodes\n 2. Inspect each reported workflow individually (you can click on a row to open it in a new tab)\n 3. **Verify that the correct outbound connectors are used to connect subsequent nodes.**"
},
"typeVersion": 1
},
{
"id": "ba065db3-be3c-4694-afbd-c9095526adf6",
"name": "Get all workflows",
"type": "n8n-nodes-base.n8n",
"position": [
1540,
1460
],
"parameters": {
"filters": {}
},
"credentials": {
"n8nApi": {
"id": "13",
"name": "n8n account"
}
},
"typeVersion": 1
},
{
"id": "0fdd3ac4-8c11-4c90-b613-fcbe479a71f6",
"name": "Webhook",
"type": "n8n-nodes-base.webhook",
"position": [
1380,
1460
],
"webhookId": "9f6c90b5-1d0a-4dca-8009-2ee39a4f8002",
"parameters": {
"path": "affected-workflows",
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
Automated n8n Workflow Backup to GitHub Repository
Overview This workflow automatically backs up every workflow in your n8n instance to a dedicated GitHub repository. It runs on a configurable schedule (or manually) and ensures that all your workflow JSON files are version-controlled and safely stored in a structured folder. The backup process intelligently handles both new workflows (creates a file) and existing ones (updates the file), making it ideal for disaster recovery, collaboration, or tracking changes over time. Step-by-Step Node Breakdown Schedule Trigger (No additional auth) — Triggers the workflow on a recurring interval. By default it runs hourly, but you can customize the schedule (e.g., daily at midnight) to suit your needs. Also supports manual execution via the Manual Trigger node. Manual Trigger (No auth) — Provides a manual button to run the backup immediately, useful for testing or on-demand backups. Get many workflows (Internal n8n API, no external credentials) — Fetches a list of all workflows from your n8n instance using the built-in n8n node. No separate API key is required; it uses the same authentication as your n8n session. Loop Over Items (No auth) — Iterates over each workflow in the list one at a time. This node processes workflows sequentially, preventing race conditions. Getafile (GitHub, OAuth2 / Personal Access Token) — Attempts to retrieve the existing workflow file from your GitHub repository at the path . If the file does not exist (i.e., a new workflow), the node’s error output is triggered. The expression in sanitizes the workflow name by replacing invalid characters (), converting to , and normalizing spaces. Convert to File1 (No auth) — Converts the retrieved GitHub file’s binary data back to a JSON object so it can be compared or overwritten. Extract from File1 (No auth) — Extracts the JSON content from the binary file, preparing it for an update operation. Edit a file (GitHub, OAuth2 / Personal Access Token) — If the workflow already exists on GitHub, this node updates the file with the latest JSON from your n8n instance. The commit message is dynamically generated (e.g., ). Convert to File (No auth) — Converts the current n8n workflow JSON into a binary file () with the workflow’s name as the filename. Create a file (GitHub, OAuth2 / Personal Access Token) — If the workflow is new (i.e., error output), this node creates a new file in the folder. The commit message includes the workflow name and . The workflow loops back to the Loop Over Items node to process the next workflow. The Sticky Note at the top serves as a comment. Setup Instructions GitHub account — You need a GitHub account and a repository (e.g., ) to store the backups. Create an empty repository or use an existing one. GitHub credential in n8n — Add a GitHub OAuth2 or Personal Access Token credential in n8n under Credentials > GitHub. Ensure the token has scope (or at least and ). Configure the nodes — - In Get many workflows, no changes needed. - In Getafile, Create a file, and Edit a file, update the and fields to match your GitHub username and repo name. - Optionally adjust the Schedule Trigger interval (set hours/minutes as desired). Error handling — The workflow references an external error workflow (). If you don’t have that, you should either create a simple error handler or remove the setting in the workflow settings. Use Cases & Adaptations Disaster recovery — Restore all workflows by downloading the JSON files from GitHub and importing them back into n8n. Version history — Track changes to workflows over time via GitHub commits and diffs. Multi-instance sync — Modify the workflow to run on multiple n8n instances, pushing to the same repo (be cautious with conflicts). Selective backup — Add a filter node after to only backup workflows with a specific tag or name pattern. Notification — Insert a Slack or email node after the loop to notify you when a backup completes or if an error occurs.
n8n Upgrade: Detect Affected Workflows with Broken Connections
Summary This workflow helps n8n administrators identify workflows that may have been affected by a past upgrade (specifically n8n version ) where multi-output nodes (like , , ) could have their output connections accidentally re-wired. It provides a self-service webhook endpoint that returns an HTML report listing all workflows with potentially broken connections, making it easy to audit and fix them. Node-by-Node Walkthrough Webhook (No auth) — Listens for HTTP GET requests at the path . When a user visits this URL in their browser, the workflow is triggered. The response mode is set to "Response Node", meaning the final output will be sent back directly. Get all workflows (API Key auth) — Uses the n8n API to fetch all workflows from the instance. You must configure this node with an n8n API credential (a personal access token created under Settings > n8n API). The node has no filters, so it retrieves every workflow. Parse potentially affected workflows (Code node, no auth) — A JavaScript code node that loops through each workflow, inspects its connections, and checks if any multi-output node (defined in the array) has empty outputs. If a node has fewer connected outputs than expected, it is flagged as potentially affected. The node outputs a JSON object with an array of affected workflows, each containing , , , and . Generate Report (HTML node, no auth) — Creates a static HTML document with a styled container, a heading, and an empty list. This serves as the shell for the interactive report generated by the next node. Serve HTML Report (Respond to Webhook node, no auth) — Takes the HTML template from the previous node and injects JavaScript that parses the affected workflows data (from the code node) and dynamically builds a list of clickable links. Each link opens the workflow in a new tab so the admin can inspect and fix the connections. The response headers are set to . Setup Instructions Prerequisites: You must have admin access to the n8n instance (the workflow must be run by the instance owner). Create an n8n API key: Go to Settings > n8n API in your n8n instance and generate a personal access token. Copy the token. Configure the "Get all workflows" node: Add an n8n credential of type "API Key" and paste the token. Leave the filters empty. Customize multi-output nodes (if needed): The code node contains a list with the default nodes (, , ). If you have community nodes with multiple outputs, add them to this array with their correct output count. Activate the workflow: Toggle the workflow to active. Use the report: Open your browser and navigate to . The page will list all affected workflows. Click on a row to open the workflow in a new tab — inspect the connections and re-wire them if needed. Use Cases & Variations Post-upgrade audit: Run this workflow after every n8n upgrade to catch connection issues early. Customized detection: Extend the array in the code node to include any custom node type that has multiple outputs. Slack/Email notification: Instead of serving an HTML report, you could send the list of affected workflows to a Slack channel or email using additional nodes. Scheduled scanning: Replace the Webhook trigger with a Schedule trigger to run the check daily and automatically notify the admin.
Weekly Zigbee2MQTT Backup to SFTP Server
Overview This workflow automates the weekly backup of your Zigbee2MQTT configuration. It triggers every Monday at 2:45 AM, sends a backup request to the Zigbee2MQTT bridge via MQTT, waits for the response containing a base64-encoded ZIP file, decodes it, and uploads the backup to an SFTP server. The workflow includes error handling to stop execution and log failures if anything goes wrong. This is ideal for home automation enthusiasts or administrators who want to ensure their Zigbee network configuration is safely archived off-site or on a central server. Node Breakdown CRON Monday 2:45 am () — No auth. Runs the workflow every Monday at 02:45 AM using the cron expression . This ensures backups happen automatically without manual intervention. Send Zigbee2MQTT backup request () — MQTT Client credentials (broker URL, port, username/password). Publishes the message to the topic . This triggers the Zigbee2MQTT bridge to generate a backup. MQTT Trigger - Backup Response () — MQTT Trigger credentials (same broker). Listens on the topic for the backup data. The trigger waits for a message and passes it to the next node. Parse JSON Object from Message Text () — No auth. Runs JavaScript to parse the incoming MQTT message, extracting the nested field from the JSON payload. This isolates the base64-encoded ZIP content. Convert to File - base64 to binary () — No auth. Takes the property from the parsed JSON (which contains the base64 string) and converts it to a binary file. The output is a ZIP file ready for upload. SFTP zip file content () — SFTP credentials (username/password or private key). Uploads the generated ZIP file to the specified SFTP server path: . The filename includes a timestamp with colons replaced by underscores. Error Handler () — No auth. If any node above fails, this node stops the workflow with the message . It acts as a safety net to prevent partial or corrupted backups. Setup Instructions SFTP Server: You need an SFTP server (e.g., a NAS, cloud VM, or any SSH‑enabled server). Create a user account and note the host, port, username, and password/private key. In n8n, configure an SFTP credential with these details. MQTT Broker: You need a running MQTT broker (e.g., Mosquitto). The workflow connects to the same broker that your Zigbee2MQTT instance uses. In n8n, create an MQTT credential with broker URL, port, username, and password. Zigbee2MQTT: Ensure your Zigbee2MQTT bridge is accessible via MQTT and that it supports the backup request feature (Zigbee2MQTT must be running and connected to the same broker). n8n Configuration: Import this workflow into your n8n instance. Update the SFTP path if needed, and verify the cron schedule matches your desired backup day/time (currently Monday 2:45 AM). Test: Run the workflow manually once to confirm the backup process completes without errors. Check your SFTP server for the uploaded ZIP file. Use Cases & Variations Home Automation Backup: Regularly archive Zigbee network configuration to recover from device failures or coordinator changes. Off-Site Redundancy: Replace the SFTP node with a cloud storage node (e.g., Google Drive, AWS S3) for off‑site backups. Notification on Success/Failure: Add a Telegram or email node after the SFTP upload to inform you of backup completion or errors. Multiple Backup Destinations: Chain additional FTP nodes to send the backup to multiple locations. Different Schedule: Change the cron expression to run daily, or at a specific time on multiple days (e.g., for Monday and Friday).