OpenRuna
Sign in
← Workflows

0605_Code_Itemlists_Create_Scheduled

33 nodes · moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n

Engine
n8n
Nodes
33
Trigger
scheduled/triggered
Source file
0605_Code_Itemlists_Create_Scheduled.json

Workflow flow

IntegrationsMoveBinaryDataFilterGoogle DriveItemListsSplitInBatchesN8NScheduleCodeIFMerge
100%

LIST OLD BACKUPS

Google Drive

DELETE OLD BACKUP

Google Drive

Item Lists old

ItemLists

Split In Batches old

SplitInBatches

TRIGGER

Schedule Trigger

Schedule

TRIGGER

Schedule Trigger1

Schedule

If n8n_old

IF

If1 n8n_backups

IF

GET CURRENT BACKUPS1

Google Drive

n8n

N8N

Move Binary Data

MoveBinaryData

Create n8n_backups

Google Drive

Create n8n_old

Google Drive

Merge mensage

Merge

Item Lists

ItemLists

GET CURRENT FOLDER

Google Drive

GET CURRENT FOLDER CREATES

Google Drive

Split In Batches2

SplitInBatches

Split In Batches

SplitInBatches

IGNORE FILES

Filter

Code

Code

MOVE INTO OLD FOLDER

Google Drive

UPLOAD WORKFLOWS

Google Drive

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

Browse by integration

moveBinaryDatafiltergoogleDriveitemListssplitInBatchesn8nschedule
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: 0605_Code_Itemlists_Create_Scheduled. 33 nodes across moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n, schedule, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"0605_Code_Itemlists_Create_Scheduled" automates a moveBinaryData-to-filter flow in n8n across 33 nodes. 33 nodes · moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n Execution begins at the scheduled/triggered trigger and flows through the 33 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

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

Example output

Imported into n8n, "0605_Code_Itemlists_Create_Scheduled" exposes 33 configured nodes. Trigger type: scheduled/triggered. Integrations: moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n, schedule. Set your credentials on the moveBinaryData 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

Paste the exported JSON for "0605_Code_Itemlists_Create_Scheduled" into Claude and ask it to explain each of the 33 nodes. Claude is good at suggesting credential mappings for moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n, schedule, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0605_Code_Itemlists_Create_Scheduled" to your accounts — which moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n, schedule credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 33 nodes.

Frequently asked questions

How do I import "0605_Code_Itemlists_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 "0605_Code_Itemlists_Create_Scheduled" use?
It uses: moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n, schedule. The flow diagram above shows how each service connects across the 33 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 moveBinaryData and filter credentials in n8n after import.
What trigger type does "0605_Code_Itemlists_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 "0605_Code_Itemlists_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 moveBinaryData, filter, googleDrive, itemLists, splitInBatches, n8n, schedule.

Related resources