OpenRuna
Sign in
← Workflows

0034_Code_Filter_Create_Scheduled

30 nodes · spotify, nocoDb, filter, splitInBatches, schedule

Engine
n8n
Nodes
30
Trigger
scheduled/triggered
Source file
0034_Code_Filter_Create_Scheduled.json

Workflow flow

IntegrationsSpotifyNocoDbFilterSplitInBatchesScheduleCodeIFMergeNoOp
100%
TRIGGER

Schedule Trigger

Schedule

Get current date

Code

Get last 10 liked tracks

Spotify

Get all user playlist

Spotify

Get monthly playlist

Filter

Monthly playlist exist in Spotify ?

IF

Get playlist in DB

NocoDb

Create playlist in Spotify

Spotify

Playlist exist in DB ?

IF

Create playlist in DB1

NocoDb

Create playlist in DB

NocoDb

Clean op

NoOp

Song is not present in the playlist ?

IF

Add song to the playlist

Spotify

For each tracks in liked song

SplitInBatches

Check if track is saved

NocoDb

Merge

Merge

Clean op1

NoOp

Is not saved

IF

Get this month playlist in DB

NocoDb

For each monthly tracks in DB

SplitInBatches

Create song entry

NocoDb

Clean op2

NoOp

Get this month tracks in DB

NocoDb

Get this month tracks in Spotify

Spotify

Filter1

Filter

End

NoOp

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

Browse by integration

spotifynocoDbfiltersplitInBatchesschedule
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

0034_Code_Filter_Create_Scheduled (30-node n8n automation, spotify, nocoDb, filter, splitInBatches, schedule) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

"0034_Code_Filter_Create_Scheduled" is an n8n automation built from 30 nodes spanning spotify, nocoDb, filter, splitInBatches, schedule. 30 nodes · spotify, nocoDb, filter, splitInBatches, schedule Execution begins at the scheduled/triggered trigger and flows through the 30 configured nodes. 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

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

Example output

Imported into n8n, "0034_Code_Filter_Create_Scheduled" exposes 30 configured nodes. Trigger type: scheduled/triggered. Integrations: spotify, nocoDb, filter, splitInBatches, 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

Paste the exported JSON for "0034_Code_Filter_Create_Scheduled" into Claude and ask it to explain each of the 30 nodes. Claude is good at suggesting credential mappings for spotify, nocoDb, filter, splitInBatches, schedule, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0034_Code_Filter_Create_Scheduled" to your accounts — which spotify, nocoDb, filter, splitInBatches, 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 30 nodes.

Frequently asked questions

How do I import "0034_Code_Filter_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 "0034_Code_Filter_Create_Scheduled" use?
It uses: spotify, nocoDb, filter, splitInBatches, schedule. The flow diagram above shows how each service connects across the 30 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 nocoDb credentials in n8n after import.
What trigger type does "0034_Code_Filter_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 "0034_Code_Filter_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, nocoDb, filter, splitInBatches, schedule.

Related resources