Send a weekly Plausible analytics digest to Telegram chat
Ready for 3.0What this workflow does
This workflow has 14 nodes and runs on a schedule (every week at 08:00) (plus 1 other trigger). Along the way it connects Telegram.
How it runs
Trigger: On a schedule (every week at 08:00) (plus 1 other trigger).
- Set Workflow Variables (Edit Fields (Set)): sets 3 fields: site_id, plausible_url, telegram_chat_id
- Post Top Pages Query (HTTP Request): calls an HTTP API (POST)
- Post This Week Referrers Query (HTTP Request): calls an HTTP API (POST)
- Post Current Page Traffic Query (HTTP Request): calls an HTTP API (POST)
- Prepare Top Pages Data (Edit Fields (Set)): sets 1 field: topPages
- Post Last Week Referrers Query (HTTP Request): calls an HTTP API (POST)
- Post Historical Traffic Query (HTTP Request): calls an HTTP API (POST)
- Combine All Insights (Merge): merges the data from its input branches
- Identify New Referrers (Code): runs custom JavaScript code
- Analyze Content Decay (Code): runs custom JavaScript code
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Manual Trigger
n8n-nodes-base.manualTrigger - Telegram
n8n-nodes-base.telegram
From the author
Quick Overview This workflow runs every Monday (or manually) to query Plausible Analytics for top pages, new referrers, and potential content decay, then formats a weekly digest and sends it to a Telegram chat. How it works 1. Runs every Monday at 8:00 AM or…