Workflow Dependency Warnings/Tracking/Graphing

Feature Requests
1

The idea is:

Provide users info about dependencies due to the “Execute Workflow” node. For example maybe something like:

  • An option when viewing a flow “Display dependent workflows”
  • A warning when deleting a workflow “There are ___ active workflows that currently execut this flow”
  • A dependncy digraph view showing a map of which flows depend on which other flows

My use case:

It’d help to generate documentation of complex flows. It’d reduce risk of changes accidentally affecting live flows.

I think it would be beneficial to add this because:

It’d reduce risk of changes accidentally affecting live flows.

Any resources to support this?

viz.js could generate a chart showing dependencies.

Are you willing to work on this?

2

hello @jzrts

As of now you can get that info from the DB with the query like:

select 
w.id,
w.name, 
w.active, 
w.wf_nodes->>'name' as ExecFunctionName,
w.wf_nodes->'parameters'->>'workflowId' as executedWF
from (
	select id,name,active,json_array_elements(nodes) as wf_nodes
	from workflow_entity
) w
where w.wf_nodes->>'type' = 'n8n-nodes-base.executeWorkflow' AND w.active::bool = true
order by id asc
1 „Gefällt mir“
3

This is helpful, thanks!

Another related suggestion: a button or link in the Execute Workflow node to pop open the workflow dependecy would be convenient. It’d help navigate throw the actual execution flow.

4

I built a workflow that might help. Give it a try? n8n Subworkflow Dependency Graph & Auto-Tagging | n8n workflow template

5

This resonates with a problem I’ve been exploring too.

I’m building Fluxpect, an external change-intelligence layer for n8n teams. It is not a replacement for an in-editor workflow dependency graph, but a complementary layer: it maps external vendor dependencies to workflows, monitors relevant public source changes, and helps show which workflows and clients may need review before something breaks in production.

The workflow-to-workflow dependency graph described here would make that operational picture even stronger.

I’m currently looking for a few n8n teams to test the beta and give candid feedback. I’d especially like to understand which dependency relationships and change signals would be most valuable in day-to-day operations.

If this is relevant to your team, I’d be happy to compare notes: