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 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 ); Empty YouTube playlist (recommended as duplicates are not handled) Configured credentials for YouTube, Spotify, and Supabase APIs Properly set variables in all "variables" nodes (variables, variables1, variables2, variables3, variables4 (all the same)) Activate the workflow !
Tags
Discord
Spotify
Supabase
YouTubeRelated workflows
See all Discord→
Automated Workflow Backup System with Google Drive, Gmail and Discord Alerts'
How it works This workflow automates the backup of all your n8n workflows to a specified Google Drive folder. It operates in two main phases: Orchestration (Scheduled Task): The workflow is initiated by a Schedule Trigger (e.g., daily at 1:30 AM by default). It then uses an n8n API Node to fetch a list of all existing workflows in your n8n instance. A Loop Over Items node processes each fetched workflow individually. For every workflow in the list, an Execute Workflow node calls the "worker" part of this same workflow, passing the individual workflow's data. Individual Workflow Backup (Worker Task): This part is triggered by the When Executed by Another Workflow node (called by the orchestrator part). It first retrieves the passed workflow data. A Parameters node defines the target Google Drive directory. The Get Google Drive File Data node searches the specified Google Drive folder to see if a backup file for the current workflow (named as WorkflowName_WorkflowID.json) already exists. An IF Node (ifDriveEmpty) checks the result: If a backup file exists, the workflow data is converted to a binary JSON file using a Code Node, and then the existing file on Google Drive is updated (Ba
Send a message with a Discord Bot
Explore this workflow on its official n8n template page.
WSet alert on the website changes
I used this to check for a page that had Out Of Stock not found when an item came back in stock. Set the URL for the HTTP Request node and your Webhook URL and Messages for the discord nodes.