Telegram + Google Trends, instant daily trend briefs
You open Google Trends, pick a country, click around, copy a few items, then repeat it again tomorrow. And again next week. It’s not hard work. It’s the kind of work that quietly steals your best planning time.
Marketing managers feel it when content calendars are due. A founder feels it when they’re trying to spot demand before competitors do. And if you run a small agency, you already know how messy it gets when every client wants “today’s trends” in a different region. This Telegram trends bot automation turns that routine into a single message.
You’ll see how this workflow pulls Google’s daily trending searches by country code, formats a clean brief, and sends it right back to Telegram (ready to forward, paste into a doc, or share with a team).
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram + Google Trends, instant daily trend briefs
flowchart LR
subgraph sg0["Telegram Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>HTTP Request"]
n1@{ icon: "mdi:cog", form: "rounded", label: "XML", pos: "b", h: 48 }
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code"]
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Send a text message"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram Trigger"]
n1 --> n2
n2 --> n3
n0 --> n1
n4 --> n0
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n4 trigger
class n0 api
class n2 code
classDef customIcon fill:none,stroke:none
class n0,n2,n3,n4 customIcon
The Problem: Trend Research Turns Into Tab-Hopping
Trend research sounds simple until it’s part of your daily rhythm. You check Google Trends (or an RSS page), pick a country, scan for what’s spiking, open a few news links, then try to summarize it in a way your team can actually use. Meanwhile, Slack pings keep coming, a meeting starts in 10 minutes, and your “quick check” turns into a half-hour detour. Worse, you can’t repeat it consistently, so insights get missed and planning becomes reactive instead of intentional.
The friction compounds. Here’s where it breaks down in real life.
- You end up doing the same manual lookup for every country or client, even though the data source is predictable.
- Trend notes get lost in chat threads or personal bookmarks, so nobody can reference them later.
- When you’re rushing, you copy the headline but forget the context, which means weak briefs and back-and-forth questions.
- It’s hard to build a habit around it, because the workflow lives in your browser tabs, not in your team’s workflow.
The Solution: Country-Code Trend Briefs in Telegram
This n8n workflow turns Telegram into a simple “ask-and-receive” trend brief tool. A user sends a two-letter country code (like US, EG, or SA) to your Telegram bot. n8n takes that exact code and requests Google’s official daily trends RSS feed for that region. The feed comes back as XML, which the workflow converts into structured data you can work with. Then a small script selects the top trends, attaches the approximate traffic volume, pulls in the top related news links, and formats everything as a readable Telegram message. Finally, the bot replies in the same chat with a clean, shareable brief.
It starts in Telegram with one short message. Then the HTTP request pulls the latest daily trends, the XML parser makes it usable, and the formatting step turns it into something you’d actually forward to a team. The last step posts it back to Telegram, so the insight lands where decisions happen.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you track trends for 5 markets each morning (US, UK, SA, EG, AE). Manually, you might spend about 10 minutes per country to find the feed, skim it, copy items, and grab a couple of news links. That’s roughly 50 minutes per day. With this workflow, you send five short Telegram messages (one per code) in about 2 minutes total, then wait for replies. Even if responses take a minute to arrive, you’re still getting close to an hour back every morning.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram to receive requests and deliver briefs.
- Google Trends RSS endpoint as the data source for daily trends.
- Telegram bot token (create it in Telegram via BotFather).
Skill level: Beginner. You’ll connect Telegram credentials and paste a small formatting script that’s already included in the workflow.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Telegram message triggers the workflow. You send a two-letter country code to your bot (US, EG, SA). That single message is the only “input” you need.
The workflow requests Google’s daily trends feed. n8n uses the country code as the geo parameter in an HTTP request to trends.google.com/trending/rss, so you always get the most recent daily list for that region.
The feed is parsed and turned into a brief. The XML node converts the RSS response into data fields, then the script grabs the top 5 trends and builds a readable Telegram message with traffic estimates and two related news links per trend.
The formatted report is sent back to Telegram. Your bot replies in the same chat, so you can forward it to a channel, paste it into a doc, or drop it into a client update.
You can easily modify the language and formatting to match your brand voice based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Telegram Trigger
Set up the workflow entry point so it listens for incoming Telegram messages and captures the user’s region input.
- Add and open Incoming Telegram Trigger.
- Set Updates to include
message. - In Additional Fields, set Chat IDs to
{{ $env.chat_id }}. - Credential Required: Connect your
telegramApicredentials.
Step 2: Connect External API Fetch
Fetch Google Trends RSS data based on the user’s input from Telegram.
- Add External API Fetch and connect it after Incoming Telegram Trigger.
- Set URL to
https://trends.google.com/trending/rss. - Enable Send Query.
- Add a query parameter with Name set to
geoand Value set to{{ $json.message.text }}.
Step 3: Set Up Processing Nodes
Parse the RSS XML and format a readable Telegram report with the top trends.
- Add XML to Data Parser and connect it after External API Fetch.
- Leave XML to Data Parser options at default.
- Add Transform Logic Script and connect it after XML to Data Parser.
- Paste the provided JS Code into Transform Logic Script to generate the final report text, including the header and top 5 trends.
$('Incoming Telegram Trigger').first().json.message.text. Ensure the trigger captures a valid region code.Step 4: Configure the Output Action
Send the formatted trend report back to the Telegram chat.
- Add Dispatch Telegram Notice and connect it after Transform Logic Script.
- Set Text to
{{ $json.text }}. - Set Chat ID to
{{ $('Incoming Telegram Trigger').item.json.message.chat.id }}. - In Additional Fields, set Parse Mode to
HTMLand Append Attribution tofalse. - Credential Required: Connect your
telegramApicredentials.
parse_mode: 'Markdown' while Dispatch Telegram Notice is set to HTML. Align these settings if formatting looks incorrect.Step 5: Test and Activate Your Workflow
Verify the workflow runs end-to-end and then activate it for production use.
- Click Execute Workflow and send a Telegram message (e.g.,
USorEG) to the bot. - Confirm that External API Fetch returns RSS data and XML to Data Parser outputs JSON.
- Check that Dispatch Telegram Notice sends a formatted trend report back to the same chat.
- Toggle the workflow to Active to enable production use.
Common Gotchas
- Telegram credentials can expire or you might be using the wrong bot token. If messages stop sending, check the Telegram Trigger and “send message” nodes first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 20 minutes if your Telegram bot is already created.
No. You’ll mostly connect Telegram and paste in the workflow. The formatting script is already included, so you’re editing text, not building logic from scratch.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Telegram costs (free) and any optional AI usage if you extend the workflow.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s the best part of this workflow. The language lives in the formatting code that builds the Telegram message, so you can translate headers, swap labels, or change the ordering in one place. You can also adjust “top 5” to “top 10” by changing the loop/limit in the Transform Logic Script node. Common tweaks include adding your brand intro line, changing the countries you allow, and posting the same brief into a Telegram channel instead of replying in a DM.
Usually it’s a bot token issue or the credential is saved under the wrong Telegram account in n8n. Regenerate the token via BotFather if you suspect it leaked, then update both the Telegram Trigger and the send message node. Also check that your bot has actually started a chat with you (Telegram won’t always deliver messages until that happens). If only some requests fail, you might be hitting rate limits from rapid-fire testing.
On n8n Cloud Starter, you’re typically fine for a small team running daily lookups, and bigger plans handle higher volume. If you self-host, there’s no execution limit (it depends on your server). Practically, this workflow is lightweight because it’s one HTTP request, one XML parse, one format step, then a Telegram reply.
Often, yes, because RSS + XML parsing + custom formatting is where no-code tools start to feel cramped. n8n makes it easier to transform the feed and control the final message without paying extra for every “formatter” step, and self-hosting is a real advantage if you expect lots of requests. Zapier or Make can still work if you keep it simple, but you may end up fighting the formatting. Talk to an automation expert if you want help choosing.
Once this is running, “what’s trending in SA today?” becomes a message, not a task. Honestly, that small shift is what makes daily research sustainable.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
