OpenRuna
Sign in
← Workflows

1634_Automation

0 nodes

Engine
n8n
Nodes
0
Trigger
manual
Source file
1634_Automation.json
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

1634_Automation is a free n8n workflow on OpenRuna — 0 nodes connecting multiple apps and APIs. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

This n8n workflow, "1634_Automation", wires together multiple apps and APIs in 0 nodes. 0 nodes It starts from a manual 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 0-node flow from scratch.
  • Benchmark it against your current your stack integration to spot missing steps or redundant nodes.
  • Import "1634_Automation" into n8n, reconnect credentials for multiple apps and APIs, and run the same automation in your own workspace.
  • Use it as a starting template when wiring multiple apps and APIs — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "1634_Automation" exposes 0 configured nodes. Trigger type: manual. Integrations: multiple apps and APIs. Set your credentials on the your stack 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 "1634_Automation" JSON into a plain-English runbook, node by node. It can flag where your stack 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 multiple apps and APIs. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "1634_Automation" — extract your stack IDs and secrets into environment variables without changing the 0-node structure.

Frequently asked questions

How do I import "1634_Automation" 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 "1634_Automation" use?
It uses: multiple apps and APIs. The flow diagram above shows how each service connects across the 0 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 your stack and your stack credentials in n8n after import.
What trigger type does "1634_Automation" use?
Trigger type: manual. 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 "1634_Automation" 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 multiple apps and APIs.

Related resources