All templates
FeaturedAutomation#Telegram#Google Analytics#MCP#Agent#Cron

Daily Telegram Google Analytics MCP Report

Send a daily Telegram summary by letting an Agent query Google Analytics through an MCP server.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Telegram#Google Analytics#MCP#Agent#Cron

Click a node to select it — same as the Heym editor; the panel shows its settings.

6 nodes · Free & source-available

Daily Telegram Google Analytics MCP Report

Send a daily GA4 digest to Telegram without building a custom reporting backend. A Cron node runs once per day, an Agent calls your Google Analytics MCP tools, and a Telegram node sends the formatted result to a chat or group.

What this workflow does

  1. DailySchedule runs once per day
  2. AnalyticsReporter (Agent) uses Google Analytics MCP tools to fetch yesterday's core metrics
  3. The Agent formats a short executive summary with sessions, users, conversions, and notable changes
  4. SendTelegramReport posts the digest to Telegram
  5. ReportStatus returns the Telegram send status for debugging

Use cases

  • Daily growth report for founders or marketing teams
  • Website traffic snapshots in a private Telegram group
  • Automated GA4 summaries without exporting CSV files

MCP and Agent setup

Configure the Agent node with your Google Analytics MCP server. The placeholder uses stdio-style settings; swap in the package, command, or HTTP endpoint used by your MCP deployment. If your MCP server returns GA Data API not configured, pass GA_SERVICE_ACCOUNT_JSON and GA_PROPERTY_ID through the Agent's MCP args field as the JSON config argument. Do not put service account JSON in the system prompt; the MCP server needs those values before the Agent can call its tools.

Setup

Create a Telegram credential, choose the target chat ID, and set the Cron expression for your timezone. For a daily 09:00 run, keep the default 0 9 * * * and adjust the scheduler timezone in your Heym deployment if needed.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+V— nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym