OpenRuna
Sign in
← Workflows

0897_Limit_Code_Send_Scheduled

29 nodes · schedule, n8n, googleDrive, splitInBatches, limit, executionData

Engine
n8n
Nodes
29
Trigger
scheduled/triggered
Source file
0897_Limit_Code_Send_Scheduled.json

Workflow flow

IntegrationsScheduleN8NGoogle DriveSplitInBatchesLimitExecutionDataGmailExecuteWorkflowDiscordIFSetCode
100%
TRIGGER

Schedule Trigger

Schedule

TRIGGER

When Executed by Another Workflow

ExecuteWorkflow

Get all n8n Workflows

N8N

Workflow Data

ExecutionData

Parameters

Set

getDriveFileData

Google Drive

ifDriveEmpty

IF

firstWorkflowJson

Set

CodeJsonToFile1

Code

Backup to Google Drive2

Google Drive

JsonToFile

Code

Backup to Google Drive4

Google Drive

failureEmail

Gmail

Loop Over Items

SplitInBatches

successEmail

Gmail

Discord

Discord

Limit

Limit

Execute Workflow

ExecuteWorkflow

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

Browse by integration

schedulen8ngoogleDrivesplitInBatcheslimitexecutionDatagmailexecuteWorkflowdiscord
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: 0897_Limit_Code_Send_Scheduled. 29 nodes across schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"0897_Limit_Code_Send_Scheduled" is an n8n automation built from 29 nodes spanning schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow. 29 nodes · schedule, n8n, googleDrive, splitInBatches, limit, executionData It starts from a scheduled/triggered trigger and routes data through every node in order. 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

  • Benchmark it against your current schedule integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 29-node flow from scratch.
  • Use it as a starting template when wiring schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow — adjust node parameters to your accounts and record IDs.
  • Import "0897_Limit_Code_Send_Scheduled" into n8n, reconnect credentials for schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow, and run the same automation in your own workspace.

Example output

Imported into n8n, "0897_Limit_Code_Send_Scheduled" exposes 29 configured nodes. Trigger type: scheduled/triggered. Integrations: schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow. Reconnect the schedule credential first, then walk the remaining nodes top to bottom. 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 "0897_Limit_Code_Send_Scheduled" into Claude and ask it to explain each of the 29 nodes. Claude is good at suggesting credential mappings for schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0897_Limit_Code_Send_Scheduled" to your accounts — which schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow 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 29 nodes.

Frequently asked questions

How do I import "0897_Limit_Code_Send_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 "0897_Limit_Code_Send_Scheduled" use?
It uses: schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow. The flow diagram above shows how each service connects across the 29 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 schedule and n8n credentials in n8n after import.
What trigger type does "0897_Limit_Code_Send_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 "0897_Limit_Code_Send_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 schedule, n8n, googleDrive, splitInBatches, limit, executionData, gmail, executeWorkflow.

Related resources