OpenRuna
Sign in
← Workflows

0182_Code_GitHub_Create_Scheduled

26 nodes · manual, executeWorkflow, n8n, httpRequest, switch, github

Engine
n8n
Nodes
26
Trigger
scheduled/triggered
Source file
0182_Code_GitHub_Create_Scheduled.json

Workflow flow

IntegrationsManualExecuteWorkflowN8NHTTPSwitchGitHubSplitInBatchesScheduleSlackSetIFMerge+2 more
100%
samedifferentnew
TRIGGER

On clicking 'execute'

Manual

TRIGGER

Execute Workflow Trigger

ExecuteWorkflow

TRIGGER

Schedule Trigger

Schedule

Starting Message

Slack

Config

Set

n8n

N8N

Get file data

GitHub

If file too large

IF

Get File

HTTP

Merge Items

Merge

isDiffOrNew

Code

Create sub path

Set

Check Status

Switch

Same file - Do nothing

NoOp

File is different

NoOp

File is new

NoOp

Create new file

GitHub

Edit existing file

GitHub

Return

Set

Failed Flows

Slack

Loop Over Items

SplitInBatches

Execute Workflow

ExecuteWorkflow

Completed Notification

Slack

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

Browse by integration

manualexecuteWorkflown8nhttpRequestswitchgithubsplitInBatchesscheduleslack
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

0182_Code_GitHub_Create_Scheduled is a free n8n workflow on OpenRuna — 26 nodes connecting manual, executeWorkflow, n8n, httpRequest, switch, github, splitInBatches, schedule. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

This n8n workflow, "0182_Code_GitHub_Create_Scheduled", wires together manual, executeWorkflow, n8n, httpRequest, switch, github, splitInBatches, schedule in 26 nodes. 26 nodes · manual, executeWorkflow, n8n, httpRequest, switch, github Execution begins at the scheduled/triggered trigger and flows through the 26 configured nodes. 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 26-node flow from scratch.
  • Benchmark it against your current manual integration to spot missing steps or redundant nodes.
  • Import "0182_Code_GitHub_Create_Scheduled" into n8n, reconnect credentials for manual, executeWorkflow, n8n, httpRequest, switch, github, splitInBatches, schedule, and run the same automation in your own workspace.
  • Use it as a starting template when wiring manual, executeWorkflow, n8n, httpRequest, switch, github, splitInBatches, schedule — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "0182_Code_GitHub_Create_Scheduled" exposes 26 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, executeWorkflow, n8n, httpRequest, switch, github, splitInBatches, schedule. 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 "0182_Code_GitHub_Create_Scheduled" 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, executeWorkflow, n8n, httpRequest, switch, github, splitInBatches, schedule. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0182_Code_GitHub_Create_Scheduled" — extract manual IDs and secrets into environment variables without changing the 26-node structure.

Frequently asked questions

How do I import "0182_Code_GitHub_Create_Scheduled" 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 "0182_Code_GitHub_Create_Scheduled" use?
It uses: manual, executeWorkflow, n8n, httpRequest, switch, github, splitInBatches, schedule. The flow diagram above shows how each service connects across the 26 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 "0182_Code_GitHub_Create_Scheduled" 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 "0182_Code_GitHub_Create_Scheduled" 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, n8n, httpRequest, switch, github, splitInBatches, schedule.

Related resources