Match Spotify Tracks to YouTube Videos

This part finds the best YouTube video for a Spotify track using the YouTube Data API v3. It searches with the track title and artist, retrieves the top 5 videos, and selects the first one with a duration within ±10% of the Spotify track length. The matched video is added to a YouTube playlist, and its ID is saved in the database.

Operation:

• Uses Spotify data (title + artist) for search.

• Ensures duration accuracy (±10% tolerance).

• Automates playlist updates and database storage.

Spotify to YouTube Playlist Synchronization

A workflow that maintains a YouTube playlist in sync with a Spotify playlist, featuring smart video matching and persistent synchronization.

Key Features

• One-way Sync: Spotify playlist → YouTube playlist (additions and deletions
• Continuous Monitoring: Automatic synchronization (every hour by default, but you can put any time you want)
• Smart Video Matching: Considers video length and content relevance
• Auto-Recovery: Automatically handles deleted YouTube videos
• Database Backup: Persistent storage using Supabase

Prerequisites

1. Supabase project with the following table structure:

CREATE TABLE IF NOT EXISTS musics (
    id TEXT PRIMARY KEY,
    title TEXT NOT NULL,
    artist TEXT NOT NULL,
    duration INT8 NOT NULL,
    youtube_video_id TEXT,
    to_delete BOOLEAN DEFAULT FALSE
);

2. Empty YouTube playlist (recommended as duplicates are not handled)
3. Configured credentials for YouTube, Spotify, and Supabase APIs
4. Properly set variables in all "variables" nodes (variables, variables1, variables2, variables3, variables4 (all the same))
5. Activate the workflow !

Workflow Components

Workflow 1: Main Sync Process

1. Change Detection

   • Monitors Spotify playlist for changes
   • Compares database state with current playlist

2. Video Matching

   • Searches YouTube based on title, artist, and duration
   • Evaluates top 5 results for best match
   • Marks unmatched tracks with "NOTFOUND"
   • Notifies user of successful matches and failures

Workflow 2: YouTube Maintenance

• Monitors YouTube playlist for removed videos
• Flags removed videos for re-search
• Handles deletion of marked videos

Workflow 3: Recovery Process

• Clears "NOTFOUND" flags periodically to re-search previously unmatched tracks

Implementation Notes

• Workflows can be separated into different files for better monitoring
• Recovery process ensures long-term playlist maintenance

Spotify-Database Synchronization

Operation:

• Compares Spotify playlist tracks against database entries

• Adds missing tracks to database

• Marks database entries for deletion when removed from Spotify playlist

Daily Force Check

Forces daily comparison between Spotify playlist and database state, bypassing playlist modification checks. Essential for:

• Initial setup of large playlists (manages YouTube API limits)

• Processing pending tracks when playlist hasn't changed

• Continuing sync attempts for unmatched tracks

Workflow 1: Main Sync Process

1. Change Detection

• Monitors Spotify playlist for changes

• Compares database state with current playlist

2. Video Matching

• Searches YouTube based on title, artist, and duration

• Evaluates top 5 results for best match

• Marks unmatched tracks with "NOTFOUND"

• Notifies user of successful matches and failures

Workflow 2: YouTube Maintenance

• Monitors YouTube playlist for removed videos

• Flags removed videos for re-search

• Handles deletion of marked videos

Workflow 3: Recovery Process

• Clears "NOTFOUND" flags periodically to re-search previously unmatched tracks

Match Spotify Tracks to YouTube Videos

Purpose and structure

This folder contains the Match Spotify Tracks to YouTube Videos workflow. Its executable nodes use aggregate, compareDatasets, discord, if, noOp, removeDuplicates, scheduleTrigger, set, splitInBatches, spotify, supabase, wait, youTube. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Every day at noon, Every day at noon + 1mn, Every hour, Every day at midnight, Every month

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/0715_Wait_Schedule_Create_Scheduled.json MIT; preserve source notices.