OpenRuna
Sign in
← Workflows

0445_Splitout_Code_Import_Scheduled

14 nodes · schedule, graphql, splitOut, googleSheets

Engine
n8n
Nodes
14
Trigger
scheduled/triggered
Source file
0445_Splitout_Code_Import_Scheduled.json

Workflow flow

IntegrationsScheduleGraphqlSplit OutGoogle SheetsIFSetCode
100%
TRIGGER

Every day at 06:00

Schedule

Get all your team's tickets

Graphql

Get end cursor

Set

Set custom fields

Set

Get next page

Graphql

Flatten object to have simple fields to filter by

Code

if has next page

IF

Split out the tickets

Split Out

Write tickets to Sheets

Google Sheets

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

Browse by integration

Browse all integrations →

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: 0445_Splitout_Code_Import_Scheduled. 14 nodes across schedule, graphql, splitOut, googleSheets, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "0445_Splitout_Code_Import_Scheduled", wires together schedule, graphql, splitOut, googleSheets in 14 nodes. 14 nodes · schedule, graphql, splitOut, googleSheets A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

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

Example output

Imported into n8n, "0445_Splitout_Code_Import_Scheduled" exposes 14 configured nodes. Trigger type: scheduled/triggered. Integrations: schedule, graphql, splitOut, googleSheets. 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

Ask Claude to turn the "0445_Splitout_Code_Import_Scheduled" JSON into a plain-English runbook, node by node. It can flag where schedule 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 schedule, graphql, splitOut, googleSheets. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0445_Splitout_Code_Import_Scheduled" — extract schedule IDs and secrets into environment variables without changing the 14-node structure.

Frequently asked questions

How do I import "0445_Splitout_Code_Import_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 "0445_Splitout_Code_Import_Scheduled" use?
It uses: schedule, graphql, splitOut, googleSheets. The flow diagram above shows how each service connects across the 14 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 graphql credentials in n8n after import.
What trigger type does "0445_Splitout_Code_Import_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 "0445_Splitout_Code_Import_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, graphql, splitOut, googleSheets.

Related resources