Weekly Google Analytics report by AI to email and Telegram

Weekly Google Analytics report by AI to email and Telegram

An n8n workflow that sends a weekly Google Analytics report. Every Monday at 7:00 it reads the last 7 days of a GA4 property and
the same days a year earlier. It totals each set, and an OpenAI model writes a short summary and a table of the changes. The report
goes out as an HTML email, and a plain text copy goes to Telegram.

What is inside

• workflow.json: the workflow as n8n exports it, thirteen working nodes and one sticky note. It holds no credential.
• README.md: these notes.

What we changed from the original copy

• The column names were German (Aufrufe, Nutzer, Sitzungen and so on). They are English now (Views, Users, Sessions,
  Sessions per user, Session duration, Purchases, Revenue per purchase, Revenue), in both Assign data nodes, both
  Summarize Data nodes and the email prompt. The first Google Analytics node was renamed to Google Analytics: Last 7 days.
• The second metric and the dimension of both Google Analytics nodes were left blank and filled in by n8n's defaults. They now say
  totalUsers and date outright.
• The email prompt read each summary with .item. Mindket's copy uses .first(), since each summary is one item built from many
  rows. The prompt's table divider had three columns for four headings, and its number examples contradicted its rules, so both
  were fixed.
• The models changed. Processing for email went from gpt-4o to gpt-5.6-terra, and Processing for Telegram from
  gpt-4o-mini to gpt-6-luna. See Good to know.
• The Google Analytics property, the two email addresses and the Telegram chat ID were the author's own. They are now an empty
  property picker and <YOUR_FROM_EMAIL>, <YOUR_TO_EMAIL> and <YOUR_TELEGRAM_CHAT_ID>.
• The sticky note was rewritten without the author's contact line.

Before you start

• An n8n instance, on n8n Cloud or your own server.
• A Google Analytics 4 property and a Google account that can read it.
• An OpenAI API key.
• The SMTP details of a mailbox that can send, and the address the report goes to.
• Optional: a Telegram bot token and the chat ID the text copy goes to.

Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick workflow.json.
2. Open Google Analytics: Last 7 days, add a Google Analytics OAuth2 credential and choose your GA4 property. Do the same in
   Google Analytics: Past 7 days of the previous year.
3. Open Processing for email and Processing for Telegram and add an OpenAI credential with your key.
4. Open Send Email, add an SMTP credential, and replace <YOUR_FROM_EMAIL> and <YOUR_TO_EMAIL> with real addresses.
5. Open Telegram, add a Telegram credential and replace <YOUR_TELEGRAM_CHAT_ID> with your chat ID. Delete this node and
   Processing for Telegram if you only want email.
6. Press Execute workflow once and check the email. Then press Publish so the Monday schedule runs.

How a run goes

1. Schedule Trigger fires on Monday at hour 7.
2. Google Analytics: Last 7 days reads eight metrics by date: page views, total users, sessions, sessions per user, average
   session duration, ecommerce purchases, average purchase revenue and purchase revenue.
3. Assign data gives the columns their report names, and Summarize Data sums the totals and averages the rest.
4. Calculation same period previous year works out the start and end dates one year back.
5. Google Analytics: Past 7 days of the previous year, Assign data1 and Summarize Data1 repeat steps 2 and 3 for those dates.
6. Processing for email (OpenAI, with a Calculator tool) gets both summaries in its prompt and writes the summary and the table
   as HTML.
7. Send Email sends that HTML. Processing for Telegram turns it into plain lines, and Telegram sends them.

Change the look

• The day and the hour: Trigger at Day and Trigger at Hour in Schedule Trigger.
• The numbers reported: the metrics in both Google Analytics nodes, then the names in both Assign data and both
  Summarize Data nodes.
• The wording and layout of the email, the number format and the currency: the prompt in Processing for email.
• The model: Model in Processing for email and Processing for Telegram.

Good to know

• OpenAI's deprecations page, read on 12 November 2026, lists gpt-4o and gpt-4o-mini as shutting down on 14 January 2027,
  with gpt-6-luna as the replacement. That model's page says Chat Completions supports function calling for it only with
  reasoning effort off, and the OpenAI node has no setting for that. So the email node, which has a Calculator tool, uses
  gpt-5.6-terra.
• Sessions per user, session duration and revenue per purchase are averages of the daily values. Google would calculate a
  weekly value differently.
• This week's range includes today so far, while last year's range is complete.
• Purchases and revenue read zero when the property records no ecommerce events.
• The euro sign and the German number format in the prompt come from the original. Change them for your market.
• The report goes out without anyone reading it first, and your traffic figures go to OpenAI.