Block 1 - Watch New Song in Drive
- Type / Role
- n8n-nodes-base.googleDriveTrigger - googleDriveTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
The Problem That it Solves Uploading music manually to YouTube is a chore. Renaming files, filling metadata, picking the right playlist, adding keywords, and scheduling the release can eat up your ...
n8n-nodes-base.googledrivetrigger, @n8n/n8n-nodes-langchain.openai, n8n-nodes-base.googledrive, n8n-nodes-base.httprequest, n8n-nodes-base.youtube, n8n-nodes-base.googlesheets, n8n-nodes-base.datetime, n8n-nodes-base.if
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by danejw.
Original n8n.io sourceThe Problem That it Solves
Uploading music manually to YouTube is a chore. Renaming files, filling metadata, picking the right playlist, adding keywords, and scheduling the release can eat up your creative time. This workflow removes the busy work so you can focus on making tracks instead of managing uploads.
How it works Drop an MP3 into your shared Google Drive “Audio” folder and walk away. The workflow detects the new file, grabs the genre from the filename based on a set of keywords, uses the genre to map to cover art styles, and YouTube playlists, generates the description and tags for YouTube metadata, and schedules and posts to YouTube channel, while sending messages to discord for updates.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 73 workflow blocks. Download the JSON for the full node graph.
| Workflow | Automated music video creation & YouTube publishing with AI-generated metadata from Google Drive |
|---|---|
| Complexity | advanced |
| Nodes | 73 |
| Categories | Content Creation, Multimodal AI |
| Author | danejw |
| Published | 10 Jun 2025 |
Use the JSON export at /data/workflows/4848/4848.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
The Problem That it Solves Uploading music manually to YouTube is a chore. Renaming files, filling metadata, picking the right playlist, adding keywords, and scheduling the release can eat up your ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, Multimodal AI use case.