OpenRuna
Sign in
← Workflows

Workflow Importer

58 nodes · extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut

Engine
n8n
Nodes
58
Trigger
scheduled/triggered
Source file
1169_Splitout_Code_Import_Webhook.json

Workflow flow

IntegrationsExtractFromFileExecuteCommandReadWriteFileHTTPFormSplit OutSortRenameKeysN8NFilterRemoveDuplicatesMerge+4 more

Integration path in execution order (sticky notes and duplicate steps omitted)

ExtractFromFileExecuteCommandReadWriteFileMergeSetCodeHTTPNoOpIFFormSplit OutSortRenameKeysN8NFilterRemoveDuplicates

37 steps · use Full diagram for every node

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

Free n8n workflow: Workflow Importer. 58 nodes across extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut, sort, renameKeys, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "Workflow Importer" chains 58 nodes to move data between extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut, sort, renameKeys. 58 nodes · extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 58-node flow from scratch.
  • Benchmark it against your current extractFromFile integration to spot missing steps or redundant nodes.
  • Study how data moves from extractFromFile to executeCommand before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the extractFromFile stack.

Example output

Imported into n8n, "Workflow Importer" exposes 58 configured nodes. Trigger type: scheduled/triggered. Integrations: extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut, sort, renameKeys. Open each node after import to map credentials to your own extractFromFile and executeCommand accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Workflow Importer" JSON into a plain-English runbook, node by node. It can flag where extractFromFile rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut, sort, renameKeys. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Workflow Importer" — extract extractFromFile IDs and secrets into environment variables without changing the 58-node structure.

Frequently asked questions

How do I import "Workflow Importer" 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 Importer" use?
It uses: extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut, sort, renameKeys. The flow diagram above shows how each service connects across the 58 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 extractFromFile and executeCommand credentials in n8n after import.
What trigger type does "Workflow Importer" 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 Importer" 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 extractFromFile, executeCommand, readWriteFile, httpRequest, form, splitOut, sort, renameKeys.

Related resources