OpenRuna
Sign in
← Workflows

Get all the tasks in Flow

2 nodes · manual, flow

Engine
n8n
Nodes
2
Trigger
scheduled/triggered
Source file
0122_Manual_Flow_Import_Triggered.json

Workflow flow

IntegrationsManualFlow
100%
TRIGGER

On clicking 'execute'

Manual

Flow

Flow

2 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

Get all the tasks in Flow is a free n8n workflow on OpenRuna — 2 nodes connecting manual, flow. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

This n8n workflow, "Get all the tasks in Flow", wires together manual, flow in 2 nodes. 2 nodes · manual, flow Execution begins at the scheduled/triggered trigger and flows through the 2 configured nodes. 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

  • Fork it to add error handling, retries, or a notification step without designing the 2-node flow from scratch.
  • Benchmark it against your current manual integration to spot missing steps or redundant nodes.
  • Import "Get all the tasks in Flow" into n8n, reconnect credentials for manual, flow, and run the same automation in your own workspace.
  • Use it as a starting template when wiring manual, flow — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "Get all the tasks in Flow" exposes 2 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, flow. Set your credentials on the manual node, then verify each downstream node picks them up. 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 "Get all the tasks in Flow" JSON into a plain-English runbook, node by node. It can flag where manual 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 manual, flow. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Get all the tasks in Flow" — extract manual IDs and secrets into environment variables without changing the 2-node structure.

Frequently asked questions

How do I import "Get all the tasks in Flow" 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 "Get all the tasks in Flow" use?
It uses: manual, flow. The flow diagram above shows how each service connects across the 2 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 flow credentials in n8n after import.
What trigger type does "Get all the tasks in Flow" 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 "Get all the tasks in Flow" 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, flow.

Related resources