Ads Report Generator, Darwani Works

Ads Report Generator

A reporting engine for an agency running 50+ clients from a single managed account. Google Ads and GA4 data syncs into Supabase every day; once a month n8n builds a polished Google Slides report per client, files it in a fresh dated Drive folder, and Claude can spin up an on-demand report any time in between.

Google Ads APIGA4Supabasen8nGoogle SlidesAI

50+ clients, a report month that never ended.

An agency managing Google Ads for 50+ clients from a single account hit the same wall every cycle: log into each account, export Google Ads and GA4, and hand-build a report per client. At that scale reporting isn't a task, it's a week lost, error-prone, and never quite consistent. The data was all there; the assembly was the bottleneck.

Daily sync, monthly report.

Daily sync

Every day, n8n pulls fresh Google Ads + GA4 data for all 50+ clients into Supabase, deduped, so nothing is ever doubled.

Auto-onboard

New clients are detected and their real GA4 property validated by Claude automatically, so they join the daily sync without anyone lifting a finger.

Monthly build

Once a month, n8n builds a polished Google Slides report deck for each client through the Slides API.

Filed away

A fresh dated Drive folder is created for the month and every client's deck is filed neatly inside.

On demand

Any time in between, Claude pulls an on-demand report straight from Supabase.

The moving parts.

50+ clients from one accountA single managed Google account fans out to 50+ client Google Ads and GA4 properties, everything pulled from one place, no per-client logins.

New clients register themselvesWhen a client comes on board, a dedicated flow detects their freshly-registered GA4 property, and because a signup often spawns several properties, a Claude request inspects them and picks the real one (the property that actually has conversions), then writes it to Supabase. No manual setup, and the monthly sync never misses a new client.

Every metric lands in SupabaseGoogle Ads spend/clicks/conversions and GA4 behaviour flow into a Supabase data layer, one clean source of truth the whole pipeline reads from.

Google Slides reports, auto-builtEach month n8n assembles a polished Slides deck per client through the Slides API, the report that used to be built by hand, now generated in minutes.

Dated Drive folders, made on the flyn8n creates a fresh Google Drive folder for each new month and files every client's report inside, the archive organizes itself.

No API on the main account, by designThe owner didn't want direct API access opened on the main Google Ads account, so the system doesn't force it. It leans on Google Ads' own native scheduled reports instead: 8 export to Drive as Sheets daily, and n8n syncs those into Supabase (deduped, so nothing doubles). The data still lands in one place, without crossing a line the client wasn't comfortable with.

Claude on tap for on-demand reportsSupabase is wired to Claude, so beyond the monthly run anyone can pull an on-demand report, ask, and get the numbers with a written read, without waiting for month-end.

How it's built.

Google Ads → Sheets

Not pulled by direct API, the owner didn't want the main account's API opened. Instead 8 native Google Ads scheduled reports export to Google Drive as Sheets every day, and n8n syncs those 8 tables into Supabase. A no-API workaround that still lands the data.

GA4 · Google Cloud

GA4 is the exception: its Data API (a Google Cloud project + OAuth) pulls each client's on-site behaviour and conversions straight into Supabase.

Supabase · PostgreSQL

The data layer, every client's metrics land here as the single source of truth the report builder and Claude both read.

n8n

The engine, a daily sync (pull + dedupe + onboard new clients into Supabase) plus a monthly job that builds each Slides deck via HTTP and files it in the right dated Drive folder. No spreadsheet touched.

Google Slides + Drive

The Slides API renders each report; Drive auto-creates a dated folder per month and stores every client's deck.

AI (Claude)

Two jobs: it disambiguates a new client's GA4 properties, picking the real one that has conversions, so onboarding is automatic, and it serves on-demand reports straight from Supabase, a written read of the live numbers any time.

How the pieces connect.

One account, 50+ clients, a report per client every month, plus on-demand. Here's the shape of how the pieces talk. No sensitive details, just the wiring.

Google Ads8 daily reports → Drive Sheets

GA4Data API · Google Cloud

Google Ads publishes 8 native daily reports into Drive as Sheets (no direct API on the owner's main account) while GA4 comes through the Data API, n8n syncs both into one Supabase

Supabase · PostgreSQLone door · source of truth

on top of that single source of truth, n8n runs the monthly build

n8ndaily sync · monthly report

it renders a Google Slides deck per client into a fresh dated Drive folder; Claude, wired to the same Supabase over MCP, serves on-demand reports and validates new-client properties

Google Slides + Drivereport deck · dated folders

Anthropic Claudeproperty sync + on-demand (MCP)

Who it's for.

◆

Marketing agenciesAgencies running Google Ads for dozens of clients who lose days to monthly reporting.

▲

Multi-brand teamsIn-house teams reporting on several brands or accounts who want one consistent, automatic deck each.

●

Google Ads + GA4 usersAnyone who wants their spend-vs-outcome story built for them, on schedule, in Slides.