This article provides a complete, practical walkthrough of the Manual Http Import Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Automating Video Upload and Renaming in Google Drive Using n8n and Google Apps Script
   
   Meta Description:  
   Learn how to automate the upload and renaming of video files in Google Drive using n8n workflow automation and a custom Google Apps Script. Streamline your content management process with this low-code solution.
   
   Keywords:  
   n8n, Google Drive API, Google Apps Script, video automation, workflow automation, upload video to Google Drive, rename file, HTTP request, no-code tools, low-code automation
   
   Third-Party APIs Used:
   
   - Google Drive API (via n8n Google Drive Node)
   - Google Apps Script Web App (custom endpoint triggered via HTTP request)
   
   Article:
   
   In today’s digital content landscape, managing and organizing video files can quickly become overwhelming—especially when you’re handling multiple uploads and need them to be consistently named and stored. Fortunately, with modern automation platforms like n8n and the power of Google Apps Script, you can streamline these tasks with minimal coding.
   
   This article covers a simple yet effective n8n workflow that takes a publicly hosted video URL, uploads the video to Google Drive via a Google Apps Script webhook, and then renames the file—all automatically. It's a great example of how to integrate services and reduce manual overhead in your video management workflow.
   
   📌 Why Use Automation for Video Uploads?
   
   Video content creators, educators, marketers, and businesses increasingly rely on cloud storage like Google Drive for video sharing and collaboration. But manually uploading and renaming files is time-consuming—and prone to error. Automation not only speeds up the workflow but also ensures file naming consistency and repeatability.
   
   Let’s explore how this n8n workflow works step-by-step.
   
   🛠️ Overview of the Workflow
   
   The n8n workflow involves a series of three connected nodes:
   
   1. Manual Trigger: Initiates the workflow with a click (ideal for testing).
   2. HTTP Request: Sends a video URL to a Google Apps Script that uploads it to Google Drive.
   3. Google Drive Node: Renames the newly uploaded video file in Google Drive.
   
   Step 1: Manual Trigger
   
   The workflow begins with a “Manual Trigger” node. This node is designed to start the workflow when the user manually initiates it—useful for development, testing, or workflows that don’t require automated scheduling.
   
   This node doesn't require any special configuration; it simply waits for user input to begin the chain of events.
   
   Step 2: Upload Video via Google Apps Script Web App
   
   The next node is an HTTP Request node titled “Send URL to GDrive Script and Upload.” Here’s where the real magic begins. This node sends a POST request to a Google Apps Script Web App URL. The request body contains:
   
   - videoUrl: A direct link to the .mp4 video file online.
   - secret: A shared secret token used to authenticate the request and prevent unauthorized access.
   
   Here is a simplified JSON object being sent:
   
   {
     "videoUrl": "https://example.com/path/to/your.mp4",
     "secret": "your-strong-secret-here"
   }
   
   On the backend, your Google Apps Script (already deployed as a Web App with correct scopes and permissions) handles the video download and uploads it to your Google Drive. The script can then optionally return a link or ID to the uploaded file.
   
   Step 3: Rename the Uploaded Video
   
   Once the video has been successfully uploaded, the third node titled "Rename Uploaded Video" comes into play. This node uses the Google Drive API via n8n’s Google Drive integration. It performs the following:
   
   - Takes the file ID or file URL (assuming it's returned from the previous HTTP node or pre-known).
   - Updates the name of the file to a standardized name—like "Music Video 1" in this example.
   
   This action ensures that all files uploaded via this workflow follow a consistent naming convention, which is crucial for organization and searchability.
   
   🌐 The Role of Google Apps Script
   
   To make this workflow effective, you’ll need to deploy a Google Apps Script as a Web App. This script receives the POST request, downloads the video from the provided URL, and uploads it directly to your designated Google Drive folder. Here’s a simplified version of what the Apps Script might look like:
   
   ```javascript
   function doPost(e) {
     const secret = "your-strong-secret-here";
     const payload = JSON.parse(e.postData.contents);
     
     if (payload.secret !== secret) return ContentService.createTextOutput("Unauthorized").setMimeType(ContentService.MimeType.TEXT);
   
     const response = UrlFetchApp.fetch(payload.videoUrl);
     const blob = response.getBlob().setName("uploaded_video.mp4");
   
     const file = DriveApp.createFile(blob);
     return ContentService.createTextOutput(file.getId()).setMimeType(ContentService.MimeType.TEXT);
   }
   ```
   
   🧩 Extending the Workflow
   
   Here are a few additional ideas to enhance this workflow:
   
   - Add automatic email notifications using Gmail node.
   - Allow dynamic video URLs via a webhook input instead of a static link.
   - Schedule the workflow to run at specific intervals.
   - Store metadata (upload date, URL, name) in a Google Sheet using n8n's Google Sheets integration.
   
   🎯 Final Thoughts
   
   This n8n workflow is a perfect example of how low-code tools can empower you to automate repetitive file management tasks. By combining the flexibility of Google Apps Script with n8n’s visual automation interface, you can easily create sophisticated workflows that save time and reduce manual intervention.
   
   Whether you're managing marketing videos, course content, or internal training materials, automating your Google Drive uploads and file renaming can dramatically improve efficiency and consistency.
   
   Ready to take your file management to the next level? Start building your own n8n workflow today!
   
   —  
   Need help setting this up for your business or creative workflow? Reach out to automation experts or explore more use-cases in the growing n8n community forums.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.