OpenRuna
Sign in
← Workflows

0706_Code_Schedule_Create_Scheduled

27 nodes · httpRequest, splitInBatches, notion, switch, schedule

Engine
n8n
Nodes
27
Trigger
scheduled/triggered
Source file
0706_Code_Schedule_Create_Scheduled.json

Workflow flow

IntegrationsHTTPSplitInBatchesNotionSwitchScheduleFunctionNoOpCodeMerge
100%

Run This First to Get Long Live Access Token

HTTP

TRIGGER

Get Posts Schedule

Schedule

Refresh Token

HTTP

Get Post

HTTP

Get Post ID

Function

Threads ID

Notion

Extract IDs

Function

Compare IDs

Function

If Post Exist

Switch

Create Page

Notion

Upload Medias

HTTP

Replace Me

NoOp

Loop Over Items

SplitInBatches

Threads / Comments

HTTP

Threads / Root

HTTP

Merge

Merge

Comment's Filter

Code

Root's Filter

Code

Threads Post

Code

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

Browse by integration

httpRequestsplitInBatchesnotionswitchschedule
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: 0706_Code_Schedule_Create_Scheduled. 27 nodes across httpRequest, splitInBatches, notion, switch, schedule, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "0706_Code_Schedule_Create_Scheduled", wires together httpRequest, splitInBatches, notion, switch, schedule in 27 nodes. 27 nodes · httpRequest, splitInBatches, notion, switch, schedule A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. 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 27-node flow from scratch.
  • Benchmark it against your current httpRequest integration to spot missing steps or redundant nodes.
  • Import "0706_Code_Schedule_Create_Scheduled" into n8n, reconnect credentials for httpRequest, splitInBatches, notion, switch, schedule, and run the same automation in your own workspace.
  • Use it as a starting template when wiring httpRequest, splitInBatches, notion, switch, schedule — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "0706_Code_Schedule_Create_Scheduled" exposes 27 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, splitInBatches, notion, switch, schedule. Set your credentials on the httpRequest 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 "0706_Code_Schedule_Create_Scheduled" JSON into a plain-English runbook, node by node. It can flag where httpRequest 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 httpRequest, splitInBatches, notion, switch, schedule. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0706_Code_Schedule_Create_Scheduled" — extract httpRequest IDs and secrets into environment variables without changing the 27-node structure.

Frequently asked questions

How do I import "0706_Code_Schedule_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 "0706_Code_Schedule_Create_Scheduled" use?
It uses: httpRequest, splitInBatches, notion, switch, schedule. The flow diagram above shows how each service connects across the 27 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 httpRequest and splitInBatches credentials in n8n after import.
What trigger type does "0706_Code_Schedule_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 "0706_Code_Schedule_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 httpRequest, splitInBatches, notion, switch, schedule.

Related resources