OpenRuna
Sign in
← Workflows

0093_HTTP_GitHub_Create_Scheduled

11 nodes · github, httpRequest, cron

Engine
n8n
Nodes
11
Trigger
scheduled/triggered
Source file
0093_HTTP_GitHub_Create_Scheduled.json

Workflow flow

IntegrationsGitHubHTTPCronFunctionMerge
100%

Get Files

GitHub

Daily at 23:59

Cron

Transform

Function

Get workflows

HTTP

Download Raw Content

HTTP

transform

Function

Get workflow data

HTTP

Merge

Merge

Merge1

Merge

GitHub Edit

GitHub

Create file

GitHub

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

Browse by integration

githubhttpRequestcron
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

0093_HTTP_GitHub_Create_Scheduled is a free n8n workflow on OpenRuna — 11 nodes connecting github, httpRequest, cron. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

Built in n8n, "0093_HTTP_GitHub_Create_Scheduled" chains 11 nodes to move data between github, httpRequest, cron. 11 nodes · github, httpRequest, cron It starts from a scheduled/triggered trigger and routes data through every node in order. 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

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

Example output

Imported into n8n, "0093_HTTP_GitHub_Create_Scheduled" exposes 11 configured nodes. Trigger type: scheduled/triggered. Integrations: github, httpRequest, cron. Open each node after import to map credentials to your own github and httpRequest 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 "0093_HTTP_GitHub_Create_Scheduled" JSON into a plain-English runbook, node by node. It can flag where github 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 github, httpRequest, cron. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0093_HTTP_GitHub_Create_Scheduled" — extract github IDs and secrets into environment variables without changing the 11-node structure.

Frequently asked questions

How do I import "0093_HTTP_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 "0093_HTTP_GitHub_Create_Scheduled" use?
It uses: github, httpRequest, cron. The flow diagram above shows how each service connects across the 11 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 github and httpRequest credentials in n8n after import.
What trigger type does "0093_HTTP_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 "0093_HTTP_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 github, httpRequest, cron.

Related resources