Block 1 - Get row(s) in sheet
- Type / Role
- n8n-nodes-base.googleSheets - googleSheets
- Config choices
- Version 4.7
Hi, I’m Amina I built this workflow to remove the daily pain of Meta Ads reporting. If you manage multiple ad accounts, you know how time consuming it is to open Ads Manager, export campaign data, ...
n8n-nodes-base.googlesheets, n8n-nodes-base.splitinbatches, n8n-nodes-base.stickynote, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.merge, n8n-nodes-base.telegram, n8n-nodes-base.scheduletrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Amina Doszhan.
Original n8n.io sourceI built this workflow to remove the daily pain of Meta Ads reporting. If you manage multiple ad accounts, you know how time-consuming it is to open Ads Manager, export campaign data, clean spreadsheets, and send updates to clients.
This automation pulls campaign performance directly from the Meta Ads API, writes structured data into Google Sheets (per client), generates a performance summary, and sends a Telegram alert when the report is updated.
It transforms manual reporting into a fully automated monitoring system.
Schedule Trigger starts the workflow on a defined schedule.
Google Sheets (Get rows) loads your client register (one row per client). Use this template structure for the client register: 👉 Client Register Template
The register should include:
ad_account_idaccess_tokenreport_sheet_urlLoop Over Items processes each client individually.
Code (ctx) prepares the current client context (account ID, token, report sheet URL).
HTTP Request calls the Meta Ads Insights endpoint and retrieves campaign-level metrics.
IF checks the response (skip if no data).
Merge combines client context + API response.
Code (Split campaigns) converts the campaigns array into individual items (one per campaign) and formats metrics for reporting.
Code (Extract spreadsheetId) extracts the spreadsheet ID from the report URL.
Google Sheets (Append row) writes each campaign row into the client’s report sheet. Example report structure: 👉 Campaign Report Template
Code (Summary & Status Logic) aggregates totals and applies campaign diagnostics.
Telegram sends a structured performance summary including:
After writing campaign rows to Google Sheets, the workflow generates a performance overview using a JavaScript node.
The workflow then:
This provides both structured spreadsheet reporting and a quick executive snapshot.
Each campaign is automatically evaluated based on CTR and CPC thresholds.
Weak Creative (❌)
If CTR < 1.5%
→ Indicates low engagement. The ad creative may need improvement.
Expensive Click (⚠)
If CPC > 0.5
→ Indicates high cost per click. Audience targeting or bidding strategy may need optimization.
Good Candidate to Scale (🔥)
If CTR ≥ 2% AND CPC ≤ 0.5
→ Strong performance. The campaign may be suitable for scaling.
OK (✅) If none of the above conditions are met → Campaign performance is within an acceptable range.
The status appears directly in the Telegram notification, allowing marketers to quickly identify which campaigns need attention without logging into Ads Manager.
Estimated setup time: 10–20 minutes.
ad_account_idaccess_tokenreport_sheet_urlThis 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 28 workflow blocks. Download the JSON for the full node graph.
| Workflow | Generate Meta Ads campaign reports in Google Sheets and send Telegram alerts |
|---|---|
| Complexity | advanced |
| Nodes | 28 |
| Categories | Market Research, AI Summarization |
| Author | Amina Doszhan |
| Published | 27 Feb 2026 |
Use the JSON export at /data/workflows/13745/13745.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.
Hi, I’m Amina I built this workflow to remove the daily pain of Meta Ads reporting. If you manage multiple ad accounts, you know how time consuming it is to open Ads Manager, export campaign data, ...
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 Market Research, AI Summarization use case.