Analyze Meta ads creatives with Google Vision & Video Intelligence APIs
This workflow transforms your Meta Ads creatives into a rich dataset of actionable insights. It's designed for data-driven marketers, performance agencies, and analysts who want to move beyond basic metrics and understand the specific visual and textual elements that drive ad performance. By automatically analyzing every video and image with Google's powerful AI (Video Intelligence and Vision APIs), it systematically deconstructs your creatives into labeled data, ready for correlation with campaign results.
Use Case
You know some ads perform better than others, but do you know why? Is it the presence of a person, a specific object, the on-screen text, or the spoken words in a video? Answering these questions manually is nearly impossible at scale. This workflow automates the deep analysis process, allowing you to:
- Automate Creative Analysis: Stop guessing and start making data-backed decisions about your creative strategy.
- Uncover Hidden Performance Drivers: Identify which objects, themes, text, or spoken phrases correlate with higher engagement and conversions.
- Build a Structured Creative Database: Create a detailed, searchable log of every element within your ads for long-term analysis and trend-spotting.
- Save Countless Hours: Eliminate the tedious manual process of watching, tagging, and logging creative assets.
How it Works
The workflow is triggered on a schedule and follows a clear, structured path:
1. Configuration & Ad Ingestion:
- The workflow begins on a schedule (e.g., weekly on Monday at 10 AM).
- It starts by fetching all active ads from a specific Meta Ads Campaign, which you define in the
Set Campaign IDnode.
2. Intelligent Branching (Video vs. Image):
- An IF node inspects each creative to determine its type.
- Video creatives are routed to the Google Video Intelligence API pipeline.
- Image creatives are routed to the Google Vision API pipeline.
3. The Video Analysis Pipeline:
- For each video, the workflow gets a direct source URL, downloads the file, and converts it to a Base64 string.
- It then initiates an asynchronous analysis job in the Google Video Intelligence API, requesting
LABEL_DETECTION,SPEECH_TRANSCRIPTION, andTEXT_DETECTION. - A loop with a wait timer periodically checks the job status until the analysis is complete.
- Finally, a Code node parses the complex JSON response, structuring the annotations (like detected objects with timestamps or full speech transcripts) into clean rows.
4. The Image Analysis Pipeline:
- For each image, the file is downloaded, converted to Base64, and sent to the Google Vision API.
- It requests a wide range of features, including label, text, logo, and object detection.
- A Code node parses the response and formats the annotations into a standardized structure.
5. Data Logging & Robust Error Handling:
- All successfully analyzed data from both pipelines is appended to a primary Google Sheet.
- The workflow is built to be resilient. If an error occurs (e.g., a video fails to be processed by the API, or an image URL is missing), a detailed error report is logged to a separate
errorssheet in your Google Sheet, ensuring no data is lost and problems are easy to track.
Setup Instructions
To use this template, you need to configure a few key nodes.
1. Credentials:
- Connect your Meta Ads account.
- Connect your Google account. This account needs access to Google Sheets and must have the Google Cloud Vision API and Google Cloud Video Intelligence API enabled in your GCP project.
2. The Set Campaign ID Node:
- This is the primary configuration step. Open this
Setnode and replace the placeholder value with the ID of the Meta Ads campaign you want to analyze.
3. Google Sheets Nodes: You need to configure two Google Sheets nodes:
Add Segments data:- Select your spreadsheet and the specific sheet where you want to save the successful analysis results.
- Ensure your sheet has the following headers:
campaign_id,ad_id,creative_id,video_id,file_name,image_url,source,annotation_type,label_or_text,category,full_transcript,confidence,start_time_s,end_time_s,language_code,processed_at_utc.
Add errors:- Select your spreadsheet and the sheet you want to use for logging errors (e.g., a sheet named "errors").
- Ensure this sheet has headers like:
error_type,error_message,campaign_id,ad_id,creative_id,file_name,processed_at_utc.
4. Activate the Workflow:
- Set your desired frequency in the
Run Weekly on Monday at 10 AM(Schedule Trigger) node. - Save and activate the workflow.
Further Ideas & Customization
This workflow provides the "what" inside your creatives. The next step is to connect it to performance.
- Build a Performance Analysis Workflow: Create a second workflow that reads this Google Sheet, fetches performance data (spend, clicks, conversions) for each
ad_idfrom the Meta Ads API, and merges the two datasets. This will allow you to see which labels correlate with the best performance. - Create Dashboards: Use the structured data in your Google Sheet as a source for a Looker Studio or Tableau dashboard to visualize creative trends.
- Incorporate Generative AI: Add a final step that sends the combined performance and annotation data to an LLM (like in the example you provided) to automatically generate qualitative summaries and recommendations for each creative.
- Add Notifications: Use the Slack or Email nodes to send a summary after each run, reporting how many creatives were analyzed and if any errors occurred.
Analyze Meta Ads Creatives with Google Vision & Video Intelligence APIs
This n8n workflow automates the process of analyzing Meta (Facebook) ad creatives using Google Cloud's Vision AI and Video Intelligence APIs. It's designed to extract insights from ad images and videos, store the results in Google Sheets, and manage the API request rate to avoid hitting limits.
What it does
This workflow performs the following key steps:
- Schedules Execution: Triggers daily to initiate the analysis process.
- Fetches Ad Creatives: Retrieves a list of ad creatives from the Facebook Graph API.
- Filters for New Creatives: Compares fetched creatives against a Google Sheet to identify those not yet processed.
- Extracts Media URLs: Parses the creative data to get image or video URLs.
- Analyzes Images (Google Vision AI): For image creatives, it sends the image URL to Google Vision AI for object detection, label detection, and web detection.
- Analyzes Videos (Google Video Intelligence API): For video creatives, it sends the video URL to Google Video Intelligence API for label detection (requires a Google Cloud Storage bucket for temporary storage).
- Stores Results: Appends the analysis results (creative ID, media type, analysis output) to a Google Sheet.
- Manages API Rate Limits: Includes a "Wait" node to introduce a delay between API calls, preventing rate limit issues.
- Handles Batches: Processes creatives in batches to optimize API calls.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Facebook Graph API Access: A Facebook Developer account with access to the Facebook Graph API and necessary permissions to read ad creatives.
- Google Sheets Account: A Google account with access to Google Sheets to store the analysis results.
- Google Cloud Account:
- Google Vision AI API Enabled: For image analysis.
- Google Video Intelligence API Enabled: For video analysis.
- Google Cloud Storage Bucket: Required for the Google Video Intelligence API to temporarily store video files for analysis.
- Credentials:
- Facebook Graph API OAuth2 credentials configured in n8n.
- Google Sheets OAuth2 credentials configured in n8n.
- Google Cloud Service Account credentials (or similar) with permissions for Vision AI, Video Intelligence API, and Cloud Storage.
Setup/Usage
- Import the Workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- Update the "Facebook Graph API" node with your Facebook Graph API OAuth2 credentials.
- Update the "Google Sheets" node with your Google Sheets OAuth2 credentials.
- Configure the "HTTP Request" nodes (for Google Vision and Video Intelligence) with your Google Cloud API key or service account authentication. Ensure the Google Cloud Storage bucket name is correctly configured for video analysis.
- Specify Google Sheet: In the "Google Sheets" node, specify the spreadsheet name and sheet name where you want to store the results. Ensure the sheet has appropriate columns for "Creative ID", "Media Type", and the various analysis outputs (e.g., "Vision Labels", "Vision Objects", "Vision Web Entities", "Video Labels").
- Customize Logic (Optional):
- Adjust the "Schedule Trigger" node to change the frequency of execution.
- Modify the "If" nodes to change filtering logic or add more conditions.
- Update the "Code" nodes if you need to transform data differently or add more complex logic.
- Adjust the "Wait" node duration to fine-tune API rate limiting.
- Activate the Workflow: Once configured, activate the workflow in n8n. It will run automatically based on the schedule.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.