The flow
Starts it 1Logic 3Service 5
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2Get my tracks inside my playlistYou TubeService
- 3Get tracks inside the Spotify PlaylistSpotifyService
- 4Loop Over ItemsSplit In BatchesLogic
- 5Extract the spotify track IDSetLogic
- 6Extract the Spotify Track IDSetLogic
- 7Find the returned tracks on SpotifySpotifyService
- 8Compare the two DatasetsCompare DatasetsService
- 9Add tracks not already in playlistSpotifyService
How it's built
- Starts on
- An event in a connected app
- Steps
- 9, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- YouTube
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own YouTube account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 9 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.