AutoVerse Workflow Controller icon

AutoVerse Workflow Controller

Enterprise workflow orchestration, execution control, and monitoring for n8n

Actions44

Workflow → Dependency Graph

AI-generated

Summary

Builds a dependency graph of workflow-to-workflow references across the n8n instance and flags possible circular calls. It is read-only.

Inputs

None.

Output shape

One item with dependencyGraph: workflowCount, edges and possibleLoops. Each edge has fromWorkflowId, toWorkflowId and a reason string naming the calling node. Each loop entry has workflowId, workflowName and a reason.

The operation has no parameters. It does not use the workflow selector. It fetches workflows through the n8n API with up to 40 pages of 100, so very large instances may be truncated. An edge is created for any node whose parameters hold workflowId, workflow or workflowID as a non-empty string or number. Expression values and resource-locator objects are not parsed, so those references may be missed. Loops are reported only for direct self-calls and two-workflow reciprocal references, not longer cycles. Requires n8n API credentials (n8nApi).

Examples

Example 1: Audit sub-workflow relationships before refactoring or deleting a workflow.

Resource: Workflow, Operation: Dependency Graph. No other fields. Filter dependencyGraph.edges downstream by toWorkflowId.

Example 2: Scheduled check that warns when workflows call each other circularly.

Schedule Trigger → AutoVerse Workflow Controller (Workflow / Dependency Graph) → IF dependencyGraph.possibleLoops is not empty → send notification.

Links

Discussion