✨ $500 AI Visibility Audit — live at Spurlock Studios. Book the audit

Marketing

Google Drive -> FB Ads

This n8n workflow automates Facebook ad creation. It fetches and downloads MP4 videos from Google Drive, then uses HTTP Requests to upload them to Facebook's ad platform and create a corresponding ad creative.

Built · ~3.5 hours saved per week

Workflow Overview This workflow automates the process of taking video files stored in Google Drive and creating corresponding ad creatives in a Facebook Ads account. It systemizes the media pipeline for social media marketers, eliminating the manual steps of downloading, uploading, and configuring video assets for advertising campaigns. What This Workflow Automates This automation bridges the gap between a cloud storage solution (Google Drive) and a digital advertising platform (Facebook Ads). It is designed for marketing teams who store their final video ad assets in a shared drive and need an efficient way to push them into the Facebook Ads Manager. The primary value is the significant time savings and reduction in potential human error. Instead of manually downloading each video, navigating to the Facebook Ads Manager, uploading the video, and then creating an ad creative, this workflow handles the entire sequence in a single, automated run. It's particularly powerful when deploying multiple video variations for A/B testing or refreshing campaign content. Technologies Used - Google Drive: Used as the source repository for video files. - Facebook Graph API: The underlying API used to interact with the Facebook Ads platform programmatically. - n8n: The automation platform that coordinates the data flow between Google Drive and Facebook. Node-by-Node Analysis 1. Manual Trigger - Node: Manual Trigger - Purpose: This node initiates the workflow. It allows a user to start the entire process on-demand with a single click in the n8n UI. This is ideal for when ad creatives are approved and ready to be deployed, giving the user full control over the timing. 2. List Drive Videos - Node: Google Drive (Operation: List) - Purpose: The workflow's first operational step connects to Google Drive and searches for specific files. Based on the configuration, it's set to find video files within a designated folder. Each video file found will be processed as a separate item in the rest of the workflow, enabling bulk processing of multiple videos at once. 3.

Tags: Marketing, Content Management, Google, Manual Trigger

Integrations: Google Drive, HTTP, Code

Related automations

Back to the Automation Library