Apify + Google Drive: clone Facebook ads faster

You find a competitor ad that’s clearly working, then the grind starts. Screenshot. Download. Rename files. Try to “recreate the vibe” in Canva or Figma. By the time you’ve made two decent variations, the momentum is gone (and honestly, so is your patience).

This ad cloning automation hits performance marketers first, but ecommerce founders and agency leads feel it too. You want more tests on proven angles without turning your week into a file-management job.

This workflow turns a Facebook Ad Library URL plus your product image into organized folders of competitor references and AI-generated “style-matched” clones in Google Drive. You’ll see what it automates, what results you should expect, and where people usually get stuck.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Apify + Google Drive: clone Facebook ads faster

Click to explore

flowchart LR

    subgraph sg0["form_ Flow"]
        direction LR
        n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/form.svg' width='40' height='40' /></div><br/>form_trigger"]
        n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "iterate_ads", pos: "b", h: 48 }
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>download_image"]
        n3@{ icon: "mdi:cog", form: "rounded", label: "convert_ad_image_to_base64", pos: "b", h: 48 }
        n4@{ icon: "mdi:cog", form: "rounded", label: "upload_ad_reference", pos: "b", h: 48 }
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>merge"]
        n6@{ icon: "mdi:cog", form: "rounded", label: "aggregate", pos: "b", h: 48 }
        n7@{ icon: "mdi:cog", form: "rounded", label: "get_image", pos: "b", h: 48 }
        n8@{ icon: "mdi:cog", form: "rounded", label: "upload_image", pos: "b", h: 48 }
        n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "set_result", pos: "b", h: 48 }
        n10@{ icon: "mdi:swap-horizontal", form: "rounded", label: "check_if_prohibited", pos: "b", h: 48 }
        n11@{ icon: "mdi:cog", form: "rounded", label: "convert_product_image_to_bas..", pos: "b", h: 48 }
        n12["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>generate_ad_image_prompt"]
        n13["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>generate_ad_image"]
        n14@{ icon: "mdi:swap-vertical", form: "rounded", label: "build_prompt", pos: "b", h: 48 }
        n15@{ icon: "mdi:swap-horizontal", form: "rounded", label: "scrape_ads", pos: "b", h: 48 }
        n5 --> n6
        n6 --> n14
        n7 --> n8
        n15 --> n1
        n9 --> n7
        n1 --> n2
        n14 --> n12
        n0 --> n11
        n8 --> n1
        n2 --> n4
        n2 --> n3
        n13 --> n10
        n10 --> n1
        n10 --> n9
        n4 --> n5
        n12 --> n13
        n3 --> n5
        n11 --> n15
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n10,n15 decision
    class n2,n12,n13 api
    classDef customIcon fill:none,stroke:none
    class n0,n2,n5,n12,n13 customIcon

The Problem: Cloning Winning Facebook Ads Is Slow and Messy

Ad research is easy. Turning research into testable creatives is the part that drags. You’re juggling the Facebook Ad Library, downloads that land in random folders, and a “rebuild it by eye” process that’s never quite the same as the original. Then you still need variations. Different colors, different product shots, slightly different layouts. It’s not hard work, it’s repetitive work, which means it steals focus from the stuff that actually moves the account.

It adds up fast. Here’s where it breaks down in real life.

Pulling 10–20 competitor ads means lots of manual downloading, renaming, and “where did I save that?” moments.
Recreating a layout from a screenshot takes long enough that you end up testing fewer concepts.
When your files aren’t organized, you can’t compare versions cleanly, so you second-guess decisions later.
Creative production becomes the bottleneck, even when media buying and budgeting are ready to scale.

The Solution: Scrape, Analyze, Clone, and File Everything Automatically

This workflow starts with a simple form submission: you paste a Facebook Ad Library URL and upload your product image. From there, Apify scrapes up to 20 ads from that URL, and the automation cycles through them one-by-one so you don’t have to babysit a long run. For each competitor ad, it downloads the image, saves a clean reference copy to Google Drive, and converts both images into a format the AI can understand. Then an AI analysis step looks at the competitor creative and your product image, writes detailed “clone instructions,” and generates a new ad visual that keeps the original style while swapping in your branding and packaging. Finally, successful clones are uploaded to Google Drive alongside the originals, already grouped for review.

The workflow kicks off from a form trigger, so it feels like a mini “creative request” portal. Apify handles extraction, AI handles the style-match and adaptation, and Google Drive becomes the single source of truth for reference ads and generated clones.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Scrapes up to 20 ads from a Facebook Ad Library URL using Apify.
Downloads each competitor image and stores it as a reference in Google Drive.
Generates AI-written cloning instructions from both images (style + product swap).
Creates new ad images and uploads the successful outputs to Google Drive.

A batch of up to 20 “ready-to-review” ad variations per competitor link.
Fewer creative stalls, because you’re not rebuilding layouts from scratch.
Cleaner A/B testing, since every clone starts from a proven style template.
One organized Drive structure for originals and clones, which makes handoff easy.
More concepts shipped per week without expanding your design queue.

Example: What This Looks Like

Say you want to test a competitor’s style across 20 ads. Manually, even a quick process is about 5 minutes to find, download, rename, and file each reference image, plus maybe 15 minutes to recreate each layout with your product. That’s roughly 6–7 hours of work for a full batch. With this workflow, you submit the form in about 2 minutes, then let it run; image generation is about 10–30 seconds per ad, so most batches finish in under an hour while you do other work.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Apify for scraping Facebook Ad Library creatives.
Google Drive to store originals and clones.
Google Gemini API key (get it from Google AI Studio / Gemini API console).

Skill level: Intermediate. You’ll connect accounts, paste API keys, and confirm a few folder and form settings in n8n.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Form submission trigger. You paste a Facebook Ad Library link and upload your product image. That single submission starts the run and keeps the input consistent across your team.

Competitor ads are scraped and queued. Apify pulls up to 20 ads from the URL, and n8n processes them in batches so it can loop safely without timeouts or memory issues.

Images are downloaded, converted, and analyzed. The workflow fetches each ad image, stores a reference copy in Google Drive, then encodes both the competitor image and your product image for the AI prompt-building step.

AI generates a style-matched clone and saves it. The system creates detailed clone instructions, generates the new ad visual, checks if content was blocked, then uploads the finished image back into Google Drive.

You can easily modify the number of ads processed to match your review capacity. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Form Trigger

Set up the form intake so the workflow can receive a Facebook Ad Library URL and a product image upload.

Add and configure Form Intake Trigger with Form Title set to Facebook Ad Thief Form.
In Form Fields, add a required text field labeled Facebook Ad Library Url with placeholder https://www.facebook.com/.
Add a required file field labeled Your Product Image and keep Multiple Files disabled.

Tip: Use the form description from Form Intake Trigger to guide users: Upload your product image and submit a facebook ad library url for the ads you want to clone/spin for your produc.t.

Step 2: Connect the Ad Scraping Pipeline

Convert the uploaded product image and scrape the ad library for matching ad assets.

In Encode Product Image, set Operation to binaryToPropery and Binary Property Name to Your_Product_Image.
In Scrape Ad Library, confirm Operation is Run actor and get dataset and Memory is 512.
Set Custom Body to the provided JSON and ensure the URL uses the expression {{ $('Form Intake Trigger').item.json['Facebook Ad Library Url'] }}.
Credential Required: Connect your apifyOAuth2Api credentials in Scrape Ad Library.

⚠️ Common Pitfall: The actorId in Scrape Ad Library contains [YOUR_ID]. Replace it with your Apify actor ID to avoid empty datasets.

Step 3: Batch, Fetch, and Parallelize Ad Assets

Cycle through scraped ads, download reference images, and process them in parallel for storage and encoding.

Leave Cycle Ad Batches as default to iterate through dataset items.
In Fetch Ad Image, set URL to {{ $node['Cycle Ad Batches'].json.snapshot.cards.first().original_image_url }}.
Fetch Ad Image outputs to both Store Ad Reference and Encode Ad Image in parallel.
In Store Ad Reference, set Name to {{ $node['Cycle Ad Batches'].json.snapshot.cards.first().title }} and choose your Drive and Folder.
Credential Required: Connect your googleDriveOAuth2Api credentials in Store Ad Reference.
In Encode Ad Image, set Operation to binaryToPropery.
Use Combine Inputs to merge Store Ad Reference and Encode Ad Image before Aggregate Results.

Tip: Ensure Cycle Ad Batches continues the loop by using the outputs from Save Generated Image and Validate Content Status back into the batch node.

Step 4: Set Up Prompt Composition and AI Requests

Aggregate data, craft the prompt, and call Gemini endpoints to generate the new ad creative.

In Aggregate Results, keep defaults to bundle combined inputs into a single item.
In Compose Prompt Text, confirm the prompt field contains the long instruction string used to guide image rewriting.
In Create Image Prompt, set URL to https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-pro:generateContent and Method to POST.
Set JSON Body to the provided template and keep the inline data expressions: {{ $node['Encode Product Image'].json.data }} and {{ $node['Encode Ad Image'].json.data }}.
Credential Required: Connect your httpHeaderAuth credentials in Create Image Prompt.
In Generate Ad Visual, set URL to https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-flash-image-preview:generateContent and keep the JSON body expression {{ JSON.stringify($json.candidates.first().content.parts.first().text) }}.
Credential Required: Connect your httpHeaderAuth credentials in Generate Ad Visual.

⚠️ Common Pitfall: If the Gemini API responds with rate limits or timeouts, increase the retry settings in Create Image Prompt and Generate Ad Visual (already configured with retries).

Step 5: Validate, Build, and Save Generated Images

Filter prohibited content, transform the generated image output into a file, and store it in Google Drive.

In Validate Content Status, confirm the condition checks {{ $json.candidates.first().finishReason }} equals PROHIBITED_CONTENT.
In Assign Image Output, set the image_result assignment to {{ $json.candidates[0].content.parts.filter(item => item.inlineData).first().inlineData.data }}.
In Build Image File, set Operation to toBinary and Source Property to image_result.
In Save Generated Image, set Name to Cloned Ad #{{ $runIndex + 1 }} and select the target Drive and Folder.
Credential Required: Connect your googleDriveOAuth2Api credentials in Save Generated Image.

⚠️ Common Pitfall: The Folder ID in Save Generated Image uses [CONFIGURE_YOUR_API_KEY]. Replace it with a valid Google Drive folder ID.

Step 6: Test and Activate Your Workflow

Validate the end-to-end flow to ensure images are scraped, generated, and stored correctly.

Click Execute Workflow and submit the Form Intake Trigger with a valid Facebook Ad Library URL and a PNG/JPG product image.
Confirm Scrape Ad Library returns dataset items and Cycle Ad Batches iterates through them.
Verify Fetch Ad Image runs and that both Store Ad Reference and Encode Ad Image receive data in parallel.
Check that Create Image Prompt and Generate Ad Visual respond successfully and that Save Generated Image writes files to Google Drive.
Once the test succeeds, switch the workflow Active toggle to enable production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Apify credentials can expire or need specific permissions. If things break, check your Apify token settings in your Apify account first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Frequently Asked Questions

How long does it take to set up this ad cloning automation automation?

About an hour if your Apify, Google Drive, and Gemini accounts are ready.

Do I need coding skills to automate ad cloning automation?

No. You’ll mainly connect accounts, paste API keys, and choose where files should be saved.

Is n8n free to use for this ad cloning automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Gemini API usage for image analysis and generation.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this ad cloning automation workflow for different folder naming and fewer than 20 ads?

Yes, and it’s one of the first tweaks worth making. You can change the limit in the Apify scrape step (the workflow is set to process up to 20 ads), and you can adjust the Google Drive upload steps to name folders by client, campaign, or product line. Most people also edit the prompt text step to push specific brand rules like “always use our headline style” or “keep backgrounds minimal.” If you want only the top few ads, add simple filtering before the batch loop.

Why is my Apify connection failing in this workflow?

Usually it’s an expired or incorrect Apify API token. Update the credential in n8n, then confirm the Apify task has access to the Facebook Ad Library scraper you’re calling. If it still fails, the source URL may not have accessible ads, or Apify may be rate limiting the run when you push too many requests quickly.

How many ads can this ad cloning automation handle?

This template is set to process up to 20 ads per Facebook Ad Library URL.

Is this ad cloning automation better than using Zapier or Make?

For this use case, yes, because you’re chaining scraping, file handling, image processing, and AI generation in one workflow. Zapier and Make can do parts of it, but multi-step looping with images gets awkward fast, and you often hit premium limits once you scale tests. n8n also gives you the self-host option, which matters when you run lots of batches. If you only need to save a single scraped link somewhere, other tools are fine. Talk to an automation expert if you want a recommendation based on your volume and team setup.

Once this is running, competitor research stops being a dead end. You get organized references and a stack of clones you can actually test, without turning your creative week into admin work.

Apify + Google Drive: clone Facebook ads faster

How This Automation Works

n8n Workflow Template: Apify + Google Drive: clone Facebook ads faster

The Problem: Cloning Winning Facebook Ads Is Slow and Messy