Block 1 - Rename Image Binary Top Image1
- Type / Role
- n8n-nodes-base.code - code
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
Who's it for Marketing teams, agencies, and businesses who regularly create tens or hundreds of Facebook ads and store their creative assets in Google Drive. Perfect for teams who want to stop doin...
n8n-nodes-base.code, n8n-nodes-base.facebookgraphapi, n8n-nodes-base.splitinbatches, n8n-nodes-base.wait, n8n-nodes-base.errortrigger, n8n-nodes-base.stopanderror, n8n-nodes-base.slack, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Chris Rudy.
Original n8n.io sourceMarketing teams, agencies, and businesses who regularly create tens or hundreds of Facebook ads and store their creative assets in Google Drive.
Perfect for teams who want to stop doing manual work of uploading and setting up ads.
This workflow automates the entire Facebook ad creation process from a simple form submission.
Users provide a Google Drive link to their media file, ad copy, and target URL through a form.
The workflow then automatically fetches the media from Google Drive, creates a new Facebook ad with proper naming conventions (matching the Drive file name), applies tracking parameters, and publishes it to the specified ad set.
It sends Slack notifications upon successful ad creation or if errors occur.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 40 workflow blocks. Download the JSON for the full node graph.
| Workflow | Meta ads bulk launcher with Google Drive integration and Slack notifications |
|---|---|
| Complexity | advanced |
| Nodes | 40 |
| Categories | Social Media |
| Author | Chris Rudy |
| Published | 05 Sept 2025 |
Use the JSON export at /data/workflows/8276/8276.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Who's it for Marketing teams, agencies, and businesses who regularly create tens or hundreds of Facebook ads and store their creative assets in Google Drive. Perfect for teams who want to stop doin...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Social Media use case.