OpenRuna
Sign in
← Workflows

0503_Splitout_Code_Create_Scheduled

23 nodes · spotify, splitInBatches, aggregate, splitOut, filter, schedule

Engine
n8n
Nodes
23
Trigger
scheduled/triggered
Source file
0503_Splitout_Code_Create_Scheduled.json

Workflow flow

IntegrationsSpotifySplitInBatchesAggregateSplit OutFilterScheduleIFCodeSet
100%
TRIGGER

Schedule Trigger

Schedule

Globals

Set

Get Downloads Playlist

Spotify

Remove oldest tracks from Downloads

Spotify

Get all Playlists

Spotify

If no Downloads Playlist found

IF

If no playlist

IF

Get Liked Tracks

Spotify

Split Out

Split Out

Add tracks to Downloads

Spotify

Get Updated Downloads Playlist

Spotify

Create Downloads Playlist

Spotify

Loop Over Items

SplitInBatches

Aggregate

Aggregate

Filter out new tracks

Code

Get tracks to remove

Code

Filter out Downloads Playlist

Filter

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

Browse by integration

spotifysplitInBatchesaggregatesplitOutfilterschedule
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

0503_Splitout_Code_Create_Scheduled (23-node n8n automation, spotify, splitInBatches, aggregate, splitOut, filter, schedule) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "0503_Splitout_Code_Create_Scheduled" chains 23 nodes to move data between spotify, splitInBatches, aggregate, splitOut, filter, schedule. 23 nodes · spotify, splitInBatches, aggregate, splitOut, filter, schedule 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

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

Example output

Imported into n8n, "0503_Splitout_Code_Create_Scheduled" exposes 23 configured nodes. Trigger type: scheduled/triggered. Integrations: spotify, splitInBatches, aggregate, splitOut, filter, schedule. Reconnect the spotify 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 "0503_Splitout_Code_Create_Scheduled" JSON into a plain-English runbook, node by node. It can flag where spotify 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 spotify, splitInBatches, aggregate, splitOut, filter, schedule. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0503_Splitout_Code_Create_Scheduled" — extract spotify IDs and secrets into environment variables without changing the 23-node structure.

Frequently asked questions

How do I import "0503_Splitout_Code_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 "0503_Splitout_Code_Create_Scheduled" use?
It uses: spotify, splitInBatches, aggregate, splitOut, filter, schedule. The flow diagram above shows how each service connects across the 23 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 spotify and splitInBatches credentials in n8n after import.
What trigger type does "0503_Splitout_Code_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 "0503_Splitout_Code_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 spotify, splitInBatches, aggregate, splitOut, filter, schedule.

Related resources