HumationHuman + Automation
Back to Catalog

Automate unified marketing reports with Google Analytics, Google Ads, Meta Ads & HubSpot

Avkash KakdiyaAvkash Kakdiya
732 views
2/3/2026
Lead GenerationHubSpotAutomationSalesforceCRM
Official Page

How it works

This workflow runs on scheduled weekly and monthly triggers to generate unified marketing performance reports. It processes multiple websites by collecting analytics data, paid ads performance, and CRM leads, then calculates KPIs and insights automatically. The workflow sends structured reports via email and stores historical data in Google Sheets. It ensures consistent reporting without manual effort.

Step-by-step

  • Step 1: Trigger & report type detection

    • Schedule Trigger2 – Triggers the workflow weekly at a predefined time.
    • Schedule Trigger3 – Triggers the workflow monthly at a predefined time.
    • check month and week1 – Identifies whether the run is weekly or monthly and sets flags.
    • Set Websites and Campaings1 – Defines websites, GA4 property IDs, and mapped ad campaigns.
    • Expand Websites1 – Expands the website array into individual website items.
    • Attach Run Flags1 – Attaches weekly or monthly flags to each website record.

  • Step 2: Website & ads data processing

    • Loop Websites1 – Iterates through each website independently.
    • Get a report – Fetches website traffic and engagement metrics from analytics.
    • Get many campaigns – Retrieves Google Ads campaign data.
    • Fetch Meta Ads – Fetches Meta Ads performance data via API.
    • Filter Google Ads By Website1 – Filters Google Ads campaigns by website.
    • Filter Meta Ads By Website1 – Filters Meta Ads campaigns by website.
    • Merge1 – Merges analytics, Google Ads, and Meta Ads datasets.
    • Build Website Dataset1 – Builds a unified dataset per website.
    • Calculate KPIs & Campaign Insights1 – Calculates spend, CTR, CPA, CPL, conversions, and performance insights.
    • Append or update row in sheet2 – Stores website-level marketing metrics in Google Sheets.

  • Step 2.1: Marketing report generation

    • Prepare Report Data2 – Combines all website datasets into a unified report object.
    • Switch – Routes execution based on weekly or monthly report type.
    • Send Weekly Marketing report2 – Sends the weekly marketing performance email.
    • Send Monthly Marketing Report2 – Sends the monthly marketing performance email.

  • Step 3: HubSpot lead analysis

    • Fetch1 – Fetches leads from HubSpot CRM.
    • Filter Hubspot Leads – Filters leads based on weekly or monthly time range.
    • Summarize Hubspot Leads – Aggregates lead status and lifecycle metrics.
    • Prepare Report Data3 – Prepares CRM summary data for reporting.

  • Step 3.1: CRM reporting & storage

    • Switch3 – Routes CRM reporting by report type.
    • Send Weekly Marketing report3 – Sends the weekly CRM summary email.
    • Send Monthly Marketing Report3 – Sends the monthly CRM summary email.
    • Code in JavaScript1 – Transforms CRM data for storage.
    • Append or update row in sheet3 – Stores CRM lead performance data in Google Sheets.
    • Switch3 – Routes CRM reporting by report type.
    • Send Weekly Marketing report3 – Sends the weekly CRM summary email.
    • Send Monthly Marketing Report3 – Sends the monthly CRM summary email.
    • Code in JavaScript1 – Transforms CRM data for storage.
    • Append or update row in sheet3 – Stores CRM lead performance data in Google Sheets.

Why use this?

  • Automates complex weekly and monthly marketing reporting.
  • Unifies website analytics, ad platforms, and CRM data in one flow.
  • Delivers consistent KPI calculations and insights every run.
  • Maintains historical performance logs in Google Sheets.
  • Scales easily across multiple websites and campaigns.

Automate Unified Marketing Reports with Google Analytics, Google Ads, Meta Ads & HubSpot

This n8n workflow simplifies and automates the process of generating unified marketing reports by pulling data from various sources and compiling them into a Google Sheet. It's designed to provide a consolidated view of your marketing performance across different platforms.

What it does

This workflow performs the following key steps:

  1. Schedules Execution: The workflow is triggered on a predefined schedule (e.g., daily, weekly, monthly) to ensure regular report generation.
  2. Fetches Google Analytics Data: It retrieves marketing performance data from Google Analytics.
  3. Fetches Google Ads Data: It pulls campaign performance metrics from Google Ads.
  4. Fetches Meta Ads Data: It collects advertising data from Meta Ads (Facebook/Instagram Ads).
  5. Fetches HubSpot Data: It extracts CRM and marketing data from HubSpot.
  6. Combines Data: All the collected data from various sources are merged into a single dataset.
  7. Transforms Data: The merged data is processed and formatted to ensure consistency and readiness for reporting.
  8. Writes to Google Sheets: The processed and unified marketing data is appended as new rows to a specified Google Sheet.
  9. Sends Email Notification (Optional): If any issues occur during the data fetching or processing, an email notification can be sent via Gmail.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Account: An active n8n instance (cloud or self-hosted).
  • Google Sheets Account: A Google account with access to Google Sheets.
  • Google Analytics Account: An active Google Analytics account with relevant data.
  • Google Ads Account: An active Google Ads account with relevant data.
  • Meta Ads Account: An active Meta Ads account (Facebook/Instagram Ads) with relevant data.
  • HubSpot Account: An active HubSpot account with relevant data.
  • Gmail Account (Optional): For sending email notifications.
  • Credentials: Configured n8n credentials for Google Sheets, Google Analytics, Google Ads, HubSpot, and Gmail.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up Google Sheets credentials (OAuth2 recommended).
    • Set up Google Analytics credentials (OAuth2 recommended).
    • Set up Google Ads credentials (OAuth2 recommended).
    • Set up HubSpot credentials.
    • Set up Gmail credentials (OAuth2 recommended) if you wish to enable email notifications.
  3. Configure Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency (e.g., daily, weekly).
    • Google Analytics: Configure the View ID, metrics, and dimensions to retrieve the specific data you need.
    • Google Ads: Configure the Customer ID, report type, and fields to fetch relevant Google Ads data.
    • HTTP Request (for Meta Ads): Update the URL, headers (including your access token), and body to query the Meta Ads API for your desired metrics and dimensions.
    • HubSpot: Configure the resource (e.g., Deals, Contacts, Engagements) and operations to retrieve your HubSpot marketing data.
    • Edit Fields (Set): Review and adjust any data transformation logic to match your reporting requirements.
    • Google Sheets: Specify the Spreadsheet ID and Sheet Name where the unified report will be written. Ensure the column headers in your Google Sheet match the output of the workflow.
    • Switch: This node likely contains logic to route data or handle errors. Review its conditions and outputs.
    • Gmail (Optional): If enabled, configure the recipient email address, subject, and body for error notifications.
  4. Activate the Workflow: Once all configurations are complete, activate the workflow. It will run automatically based on your defined 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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

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.

Le NguyenBy Le Nguyen
942