OpenRuna
Sign in
← Workflows

Workflow stats

33 nodes · manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook

Engine
n8n
Nodes
33
Trigger
scheduled/triggered
Source file
1401_Code_Webhook_Automate_Webhook.json

Workflow flow

IntegrationsManualExecuteWorkflowXMLHtmlMoveBinaryDataRespondToWebhookSortAggregateN8NWebhookCodeSet+1 more
100%
TRIGGER

When clicking "Test workflow"

Manual

TRIGGER

Execute Workflow Trigger

ExecuteWorkflow

TRIGGER

Request HTML dashboard

Webhook

TRIGGER

Request xsl template

Webhook

Template elements

Set

n8n-get-workflows

N8N

Prepare JSON object

ExecuteWorkflow

Convert to XML

XML

Final template

Set

get-nodes-via-jmespath

Set

workflows-section

Set

Create HTML

Html

Respond to Webhook2

RespondToWebhook

nodes-section

Code

tags-section

Code

globals-section

Set

Move Binary Data

MoveBinaryData

Sort-workflows

Sort

webhook-section

Code

Respond to Webhook

RespondToWebhook

Sort-nodes

Sort

Sort-tags

Sort

Aggregate-workflows

Aggregate

Sort-whooks

Sort

Aggregate-nodes

Aggregate

Aggregate-tags

Aggregate

Aggregate-whooks

Aggregate

Final-json

Merge

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

Browse by integration

manualexecuteWorkflowxmlhtmlmoveBinaryDatarespondToWebhooksortaggregaten8nwebhook
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

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

Workflow stats (33-node n8n automation, manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

"Workflow stats" is an n8n automation built from 33 nodes spanning manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate. 33 nodes · manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook Execution begins at the scheduled/triggered trigger and flows through the 33 configured nodes. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". 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 manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate — adjust node parameters to your accounts and record IDs.
  • Import "Workflow stats" into n8n, reconnect credentials for manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate, and run the same automation in your own workspace.
  • Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.
  • Study how data moves from manual to executeWorkflow before building your own variant.

Example output

Imported into n8n, "Workflow stats" exposes 33 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate. Reconnect the manual credential first, then walk the remaining nodes top to bottom. 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 "Workflow stats" into Claude and ask it to explain each of the 33 nodes. Claude is good at suggesting credential mappings for manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Workflow stats" to your accounts — which manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate 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 33 nodes.

Frequently asked questions

How do I import "Workflow stats" 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 "Workflow stats" use?
It uses: manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate. The flow diagram above shows how each service connects across the 33 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 manual and executeWorkflow credentials in n8n after import.
What trigger type does "Workflow stats" 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 "Workflow stats" 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 manual, executeWorkflow, xml, html, moveBinaryData, respondToWebhook, sort, aggregate.

Related resources