The private implementation uses a self-hosted n8n workflow as the coordinator. Provider adapters supply measurements, deterministic logic validates and summarises them, Google Sheets receives the latest source table, and Data Studio presents it through a separate connection.
| Layer | Responsibility |
|---|---|
| Schedulers | Start daily and Monday-only executions at 09:00 Europe/Zurich. |
| Report context | Establish the owner profile, daily/weekly mode, generation timestamp, date range, and report timezone. |
| Configuration checks | Require enabled sources, approved credentials, account identifiers, and valid configuration before collection. |
| Provider adapters | Issue bounded read requests and preserve source-specific meaning. |
| Validation | Check response shape, numeric metrics, currencies, timezones, and known incompleteness signals. |
| Report assembly | Produce source statuses, notes, deterministic totals, ratios, and the flat dashboard table. |
| Sheet export | Overwrite Daily for daily mode or Latest for weekly mode, and verify the returned range and dimensions. |
| Dashboard | Read the private Sheet and display available measurements and source context. |
- A daily or weekly clock trigger starts a separate execution of the same published workflow.
- Reporting logic selects yesterday for daily mode or seven complete days for weekly mode, excluding the current day.
- Each source passes through a setup check. Disabled or unconfigured sources produce an explicit status without a provider request.
- Enabled Meta and HubSpot adapters request the permitted measurements.
- Responses are normalised and validated. Failures remain attached to their source instead of becoming fabricated metrics.
- The report is assembled. The accepted path bypasses the optional AI summary because AI is off.
- Google Sheets receives a header and five source rows in
Daily!A1:M6orLatest!A1:M6, according to the execution's mode. - The workflow checks that the update response names the expected range, six rows, and 13 columns. Data Studio reads the feeds independently through native Sheets connections on separate pages.
This sequence describes logical responsibilities; it is not a public workflow definition or a deployment recipe.
The existing manual entry remains weekly, and a separate daily manual entry supports maintenance checks. Each execution creates its own profile context; changing the daily period does not mutate the weekly period. Only the two fixed feed ranges are accepted for export. On Monday, both schedules can run at the same clock time without writing over one another's report.
Both triggers use Europe/Zurich so the owner can expect a consistent Swiss wall-clock time. Source reporting uses the verified Meta account timezone recorded as EET, so date boundaries align with that account's daily results.
The period has an inclusive start date and end date for presentation. Timestamp filtering uses the start boundary through the next midnight after the last included day, with an exclusive upper bound. It is a calendar-day window, rather than an assumption that every day is exactly 24 hours long.
Meta, HubSpot, and the Google report writer use encrypted credentials managed by n8n. Account configuration and credential selection are separate: a saved account identifier does not grant permission to read it.
The report writer's Google OAuth application uses a separate Cloud project and is in production. Its drive.file scope is limited to app-authorised files rather than blanket access to the owner's Drive. Data Studio uses its own separately authorised native Sheets connector; the writer's access does not grant the dashboard's access.
No provider credentials, live account identifiers, private destination URLs, internal service addresses, or deployment configuration are included in this repository.
There are distinct checks for provider collection, Sheet export, and dashboard display. A successful provider response does not by itself establish a successful export. A saved dashboard URL produces the workflow status configured_link_only; it is not evidence of dashboard availability.
Each export checks the Sheets API update response, including the target range and table dimensions. Maintenance acceptance also read back both feeds and reviewed formulas and both dashboard pages. Those stronger acceptance checks are not claimed to run continuously on every schedule.
Real GA4, Google Ads, or Tag Manager assets can be connected individually after owner approval. Each source needs its own credential/access check, valid account configuration, response validation, and live execution evidence. The same report structure can then describe it without presenting a configured adapter as an accepted connection.
Historical storage, full advertising pagination, or notification delivery would change the accepted behavior and require separate implementation and verification. None is supplied by this documentation repository.
The private provenance record identifies two public n8n template foundations:
| Template reference | Recorded adaptation |
|---|---|
| n8n workflow 8463 | GA4 HTTP reporting node and period/reporting structure. |
| n8n workflow 12124 | Weekly trigger and source aggregation/report-table structure. |
The personal workflow adds fixed read-only provider requests, deterministic metric validation, explicit setup statuses, and the accepted private export configuration. Template provenance is not evidence that a deferred provider is connected. No template export or third-party source is redistributed through this showcase; the original projects retain their own terms.