OpenRuna
Sign in
← Workflows

0667_Code_GitHub_Create_Scheduled

23 nodes · manual, n8n, httpRequest, switch, github, splitInBatches

Engine
n8n
Nodes
23
Trigger
scheduled/triggered
Source file
0667_Code_GitHub_Create_Scheduled.json

Workflow flow

IntegrationsManualN8NHTTPSwitchGitHubSplitInBatchesScheduleExecuteWorkflowSetIFMergeCode+1 more
100%
samedifferentnew
TRIGGER

On clicking 'execute'

Manual

TRIGGER

Schedule Trigger

Schedule

TRIGGER

Execute Workflow Trigger

ExecuteWorkflow

n8n

N8N

Globals

Set

Get file data

GitHub

If file too large

IF

Get File

HTTP

Merge Items

Merge

isDiffOrNew

Code

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

Execute Workflow

ExecuteWorkflow

Loop Over Items

SplitInBatches

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

Browse by integration

manualn8nhttpRequestswitchgithubsplitInBatchesscheduleexecuteWorkflow
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

Free n8n workflow: 0667_Code_GitHub_Create_Scheduled. 23 nodes across manual, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "0667_Code_GitHub_Create_Scheduled", wires together manual, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow in 23 nodes. 23 nodes · manual, n8n, httpRequest, switch, github, splitInBatches Execution begins at the scheduled/triggered trigger and flows through the 23 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

  • Import "0667_Code_GitHub_Create_Scheduled" into n8n, reconnect credentials for manual, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow, and run the same automation in your own workspace.
  • Use it as a starting template when wiring manual, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow — adjust node parameters to your accounts and record IDs.
  • Study how data moves from manual to n8n before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.

Example output

Imported into n8n, "0667_Code_GitHub_Create_Scheduled" exposes 23 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow. Open each node after import to map credentials to your own manual and n8n 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 "0667_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, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow. Handy for onboarding teammates new to n8n.

Cursor

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

Frequently asked questions

How do I import "0667_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 "0667_Code_GitHub_Create_Scheduled" use?
It uses: manual, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow. The flow diagram above shows how each service connects across the 23 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 n8n credentials in n8n after import.
What trigger type does "0667_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 "0667_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, n8n, httpRequest, switch, github, splitInBatches, schedule, executeWorkflow.

Related resources