Sticky Note Automate

Used in Sticky Note, this automated workflow identifies potentially affected workflows after an upgrade, ensuring proper connections in multi-output nodes. It generates a comprehensive report accessible via a webhook, helping users maintain workflow integrity and functionality.

7/8/2025
9 nodes
Medium
webhookmediumsticky noten8nrespondtowebhookintegrationapi
Categories:
Webhook TriggeredMedium Workflow
Integrations:
Sticky NoteN8nRespondToWebhook

Target Audience

Target Audience


- n8n Users: If you are using n8n and have upgraded to version 0.214.3, this workflow is essential for you to ensure your workflows function correctly.
- Developers: Those who have implemented community nodes with multiple outputs will find this workflow particularly useful for identifying potential issues.
- Workflow Managers: Individuals responsible for maintaining and optimizing workflows in n8n will benefit from running this workflow to catch any misconfigurations.

Problem Solved

Problem Solved


This workflow addresses the issue of misconfigured workflows that may have occurred after upgrading to n8n version 0.214.3. It identifies workflows and nodes that might have been affected due to incorrect wiring, especially for nodes with multiple outputs like If, Switch, and Compare Datasets. By running this workflow, users can ensure that their workflows are functioning as intended and avoid potential errors in automation processes.

Workflow Steps

Workflow Steps


1. Webhook Trigger: The workflow starts by listening for a request at the webhook path /webhooks/affected-workflows.
2. Get All Workflows: Upon receiving a request, it retrieves all workflows from the n8n instance using the configured API key.
3. Parse Workflows: The workflow then analyzes each workflow to identify nodes that have multiple outputs and checks their connections for any empty outputs.
4. Generate Report: If any potentially affected nodes are found, a report is generated listing these workflows along with their affected nodes.
5. Serve HTML Report: Finally, the workflow serves an HTML report containing the findings, allowing users to easily access and inspect the affected workflows.

Customization Guide

Customization Guide


- API Key Configuration: Update the "Get all workflows" node to use your own n8n API key. You can find or create your API key in the n8n settings under "Settings > n8n API".
- Add Community Nodes: If you have installed community nodes that have multiple outputs, you should add them to the MULTI_OUTPUT_NODES constant in the "Parse potentially affected workflows" code node to ensure they are included in the analysis.
- Adjust Webhook Path: You can modify the webhook path in the "Webhook" node if you want to change how you access the report.
- HTML Report Styling: Customize the HTML report generated in the "Generate Report" node by editing the HTML content to match your branding or style preferences.