Skip to content
FlowHubFluxonLab
Google Drive
Google Drivefree

Remove Video Background & Compose on Custom Video Background with Google Drive

by Paul Rousseladapted from n8n official workflow galleryUpdated Aug 2026
RequiresGoogle DriveGoogle DriveHTTP RequestHTTP Request
Share Post Share
WeWebhook TriggerMaManual TriggerSeExtract Webhook DataExtract Webhook…SeSample Video URLs (Edit Here)Sample Video UR…MeMerge TriggersHR1. Create Job (Upload Foreground)1. Create Job (…HR2. Start Composition2. Start Compos…HR3. Check Job Status3. Check Job St…IfIs Complete?HR4. Download Video4. Download Vid…5. Upload to Google Drive5. Upload to Go…SeBuild Success ResponseBuild Success R…IfHas Failed?WaWait 20sSeBuild Error ResponseBuild Error Res…IfFrom Webhook?RTRespond to WebhookRespond to Webh…SeManual Test CompleteManual Test Com…12345678910111213141516171819
1/5
STEPS · 19
Starts on an incoming request

How it works • Upload foreground video (AI actors, product demos, webcam footage) • Provide custom background video URL • API removes video background with videobgremover.com • Composites foreground onto background • Downloads and uploads to Google Drive • Returns shareable link Set up steps • Get API key at https://videobgremover.com/n8n (2 min) • Import workflow (1 min) • Add API key to n8n variables as VIDEOBGREMOVER_KEY (1 min) • Connect Google Drive (2 min) • Test with manual trigger (1 min) • Total: 7 minutes What you'll need • VideoBGRemover API key ($0.50-$2.00 per minute) • Google Drive account • Publicly accessible video URLs • n8n instance Perfect for • AI UGC ad creators using HeyGen, Synthesia, Arcads • Marketing agencies creating ad variations • E-commerce product demos on custom backgrounds • Social media content with branded scenes • Video editors removing backgrounds at scale Key features • Video composition with custom templates • Audio mixing with adjustable volumes • 20-second polling for status • Google Drive integration • Webhook automation support • 3-5 minute processing time per minutes of input video

Tags

n8nreference-onlygoogle-drive
Connects
googledriveGoogle DriveWHTTP Request
CategoryGoogle Drive
Triggermanual
Complexityadvanced
Nodes18
AddedOct 10, 2025

Related workflows

See all Google Drive
googledriveW
free

Backup n8n workflows to Google Drive

Temporary solution using the undocumented REST API for backups using Google drive. Please note that there are issues with this workflow. It does not support versioning, so please know that it will create multiple copies of the workflows so if you run this daily it will make the folder grow quickly. Once I figure out how to version in Gdrive I'll update it here.

by Angel Menendez
googledriveW
free

Translate PDF documents from Google drive folder with DeepL

This workflow will translate all your PDF documents from specified Google Drive folder to the desired language. Translated files will be automatically uploaded to the original folder. Required accounts 1️⃣ Google Drive account 2️⃣ DeepL developer account and API key How to setup? 1️⃣ Setup your google drive folder url, target and source language in the configuration node 2️⃣ Connect your Google Drive account with all Google Drive nodes 3️⃣ Setup HTTP header credentials that should be used for HTTP nodes in the template (replace yourAuthKey with your DeepL API key) 4️⃣ Set your DeepL header credentials in all HTTP nodes

by Milorad Filipovic
googledriveW
free

Automatically optimise images added to a Google drive folder

How it works This workflow watches a selected Google Drive folder for any images added to it. It then takes that image, sends it the the tinypng.com service which optimises and reduces its size (where possible) Tinypng then returns the updated image which is then automatically saved in your chose Google Drive folder Setting things up It's pretty simple to configure and should only take around 5-10mins. You only need to set up credentials for Google Drive and Tinypng.com For Tinypng.com you can sign up for their free tier API access which gives you 500 optimisations per month Once you have those two things, you just need choose your 'input' folder to watch for images and your 'output' folder for where these images should be stored There are a few more optional things you can do such as the naming of your final image and also lots more you could do with the Tinypng API for more advanced image optimisation

by Jonathan