⚠️ When and how to use this workflow
Configured with Html, N8N, Respond To Webhook, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Integration
- Trigger
- Code
- Transform
- Web / API
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Get all workflows | Integration | N8N | See node parameters |
| Webhook | Trigger | Webhook | See node parameters |
| Parse potentially affected workflows | Code | Code | See node parameters |
| Generate Report | Transform | Html | See node parameters |
| Serve HTML Report | Web / API | Respond To Webhook | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
n8nApi
Workflow notes
⚠️ When and how to use this workflow
⚠️ When and how to use this workflow
If 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.
This workflow helps you identify potentially affected workflows and nodes that you should check.
❗️Please ensure to run this workflow as the instance owner❗️
- Configure the "Get all workflows" node to use your n8n API key. (You can find/create your API key under "Settings > n8n API")
- If you have community nodes installed that have more than 1 output, add them to the constant
MULTI_OUTPUT_NODESin the "Parse potentially affected workflows" code node. - Activate the workflow
- Visit
{YOUR_INSTANCE_URL}/webhooks/affected-workflowsfrom your browser - The report will list potentially affected workflows/nodes.
- The square brackets after the workflow name list the potentially affected nodes
- Inspect each reported workflow individually (you can click on a row to open it in a new tab)
- Verify that the correct outbound connectors are used to connect subsequent nodes.
👆
👆
In case you have community nodes installed, add them to MULTI_OUTPUT_NODES
👆
👆
Configure this node to use your n8n API credential
👆
👆
Find the generated report at {YOUR_INSTANCE_URL}/webhooks/affected-workflows
⚠️ When and how to use this workflow
⚠️ When and how to use this workflow
Purpose and structure
This folder contains the ⚠️ When and how to use this workflow workflow. Its executable nodes use code, html, n8n, respondToWebhook, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Webhook
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0296_Code_Webhook_Create_Webhook.json MIT; preserve source notices.