Upload & rename videos to Google Drive via Apps Script from URL
📄 Google Script Workflow: Upload File from URL to Google Drive (via n8n)
🔧 Purpose:
This lightweight Google Apps Script acts as a server endpoint that receives a file URL (from n8n), downloads the file, uploads it to your specified Google Drive folder, and responds with the file’s metadata (like Drive file ID and URL). This is useful for large video/audio files that n8n cannot handle directly via HTTP Download nodes.
🚀 Setup Steps:
1. Create a New Script Project
- Go to https://script.google.com
- Click “New Project”
- Rename the project to something like:
DriveUploader
2. Paste the Script Code
Replace the default Code.gs content with the following (your custom script):
function doPost(e) {
const SECRET_KEY = 'your-strong-secret-here'; // Set your secret key here
try {
const data = JSON.parse(e.postData.contents);
// 🔒 Check for correct secret key
if (!data.secret || data.secret !== SECRET_KEY) {
return ContentService.createTextOutput("Unauthorized")
.setMimeType(ContentService.MimeType.TEXT);
}
const videoUrl = data.videoUrl;
const folderId = 'YOUR_FOLDER_ID_HERE'; // Replace with your target folder ID
const folder = DriveApp.getFolderById(folderId);
const response = UrlFetchApp.fetch(videoUrl);
const blob = response.getBlob();
const file = folder.createFile(blob);
file.setName('uploaded_video.mp4'); // You can customize the name
return ContentService.createTextOutput(file.getUrl())
.setMimeType(ContentService.MimeType.TEXT);
} catch (err) {
return ContentService.createTextOutput("Error: " + err.message)
.setMimeType(ContentService.MimeType.TEXT);
}
}
3. Generate & Set Up Secret Key
To allow authorized post requests to your script only, we need to generate a secret key from aany reliable key generator.
- You can head over to acte, click generate and copy the "Encryption key 256".
- Paste it in the 'your-strong-secret-here' placeholder in your script then click save
const SECRET_KEY = 'your-strong-secret-here'; // Set your secret key here;
4. Replace Folder ID in Code
- Open the target Drive folder in your browser
- The folder ID is the part of the URL after
/folders/
Example:https://drive.google.com/drive/u/0/folders/1Xabc12345678defGHIJklmn - Paste that ID in the script:
var folderId = "1Xabc12345678defGHIJklmn";
5. Set Up Deployment as Web App
- Click “Deploy” > “Manage Deployments” > “New Deployment”
- Under Select type, choose Web app
- Description:
Upload from URL to Drive - Execute as: Me
- Who has access: Anyone
- Click Deploy
- Authorize the script when prompted
- Copy the Web App URL
📤 How to Use in n8n
1. HTTP Request Node
- Method:
POST - URL: (your web app URL)
- Secret Key: (Secret Key set in script)
- Body Content Type:
JSON - Paste code:
{
"videoUrl": "https://example.com/path/to/your.mp4",
"secret": "your-strong-secret-here"
}
videoUrl: The file download URLsecret: The generated and set up secret key
2. Rename Node
- A simple drive update node to rename the file using the file drive url returned from the script.
n8n Workflow: Upload and Rename Videos to Google Drive via Apps Script from URL
This n8n workflow provides a streamlined way to upload videos from a given URL to Google Drive and rename them using a Google Apps Script. It acts as a bridge, allowing you to trigger the Google Apps Script with specific video data.
What it does
This workflow automates the following steps:
- Manual Trigger: The workflow starts when manually executed.
- HTTP Request to Google Apps Script: It makes an HTTP POST request to a Google Apps Script endpoint. This request is intended to send data (presumably video URL and desired filename) to the Apps Script, which then handles the actual upload and renaming process in Google Drive.
- Google Drive (Placeholder): A Google Drive node is present in the workflow, though not actively connected in the provided JSON. This suggests a potential future expansion or an alternative path where n8n could directly interact with Google Drive.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n instance: A running n8n instance to import and execute the workflow.
- Google Account: A Google account with access to Google Drive and Google Apps Script.
- Google Apps Script: A pre-configured Google Apps Script deployed as a web app, designed to:
- Receive POST requests with video URL and filename data.
- Download the video from the provided URL.
- Upload the video to a specified Google Drive folder.
- Rename the uploaded video according to the provided filename.
- Crucially, the URL for this deployed Apps Script needs to be configured in the "HTTP Request" node.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Google Apps Script:
- Ensure you have a Google Apps Script deployed as a web app that can handle POST requests.
- The Apps Script should be set up to accept parameters (e.g.,
videoUrl,fileName) from the incoming request. - It should then use these parameters to fetch the video, upload it to Google Drive, and rename it.
- Configure HTTP Request Node:
- Open the "HTTP Request" node in the workflow.
- Update the "URL" field to point to your deployed Google Apps Script web app URL.
- Ensure the "Method" is set to "POST".
- Configure the "Body Parameters" to send the necessary data (e.g.,
videoUrl,fileName) that your Apps Script expects. You can use expressions to dynamically pass data if this workflow were to be triggered by another source (e.g., a webhook). For manual testing, you can hardcode values.
- Credentials (if applicable): While the Google Drive node is not connected, if you were to use it directly, you would need to configure Google Drive OAuth2 credentials in n8n. The HTTP Request node to the Apps Script typically doesn't require n8n's Google Drive credentials directly, as the Apps Script handles its own authentication to Google Drive.
- Execute the workflow: Click the "Execute Workflow" button to run the workflow and trigger your Google Apps Script.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte