OpenRuna
Sign in
← Workflows

n8n Subworkflow Dependency Graph & Auto-Tagging

40 nodes · httpRequest, n8n, filter, schedule, splitInBatches, splitOut

Engine
n8n
Nodes
40
Trigger
scheduled/triggered
Source file
1591_Splitout_Code_Automate_Webhook.json

Workflow flow

IntegrationsHTTPN8NFilterScheduleSplitInBatchesSplit OutAggregateQuickChartWebhookRespondToWebhookCodeSet+2 more
100%
TRIGGER

And every Sunday

Schedule

TRIGGER

When this workflow is activated

N8N

TRIGGER

When viewed in a browser

Webhook

GET all workflows

N8N

List callers of subworkflows

Code

Exclude uncalled workflows

Filter

GET workflow(s)

N8N

Exclude missing workflows

Filter

Count callers and identify new callers

Set

Update workflow tags

HTTP

Return dependency graph data

Set

Loop through workflows

SplitInBatches

Combine dependency graph values into labels

Aggregate

SET instance_url

Set

Format workflow relationship data for rendering

Code

GET all tags

HTTP

Visualize subworkflow dependency graph

QuickChart

Visualize dependency graph with MermaidJS

RespondToWebhook

Remove existing tags from new_callers list

Set

Create new tags

HTTP

GET all tags again

HTTP

If any new callers

IF

Return original pass through values

Code

Create tag id:name dictionary

Set

Split out new callers as new tags

Split Out

Merge

Merge

Retrieve tag ids and names from dictionary

Set

27 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

n8n Subworkflow Dependency Graph & Auto-Tagging is a free n8n workflow on OpenRuna — 40 nodes connecting httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"n8n Subworkflow Dependency Graph & Auto-Tagging" is an n8n automation built from 40 nodes spanning httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart. 40 nodes · httpRequest, n8n, filter, schedule, splitInBatches, splitOut A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Use it as a starting template when wiring httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart — adjust node parameters to your accounts and record IDs.
  • Import "n8n Subworkflow Dependency Graph & Auto-Tagging" into n8n, reconnect credentials for httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart, and run the same automation in your own workspace.
  • Share it with your team as a documented reference for scheduled/triggered automations in the httpRequest stack.
  • Study how data moves from httpRequest to n8n before building your own variant.

Example output

Imported into n8n, "n8n Subworkflow Dependency Graph & Auto-Tagging" exposes 40 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart. Open each node after import to map credentials to your own httpRequest and n8n accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "n8n Subworkflow Dependency Graph & Auto-Tagging" into Claude and ask it to explain each of the 40 nodes. Claude is good at suggesting credential mappings for httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "n8n Subworkflow Dependency Graph & Auto-Tagging" to your accounts — which httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 40 nodes.

Frequently asked questions

How do I import "n8n Subworkflow Dependency Graph & Auto-Tagging" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "n8n Subworkflow Dependency Graph & Auto-Tagging" use?
It uses: httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart. The flow diagram above shows how each service connects across the 40 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own httpRequest and n8n credentials in n8n after import.
What trigger type does "n8n Subworkflow Dependency Graph & Auto-Tagging" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "n8n Subworkflow Dependency Graph & Auto-Tagging" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for httpRequest, n8n, filter, schedule, splitInBatches, splitOut, aggregate, quickChart.

Related resources