BrowserAct + Telegram: curated social digests

You check X/Twitter “for five minutes,” then resurface an hour later with 30 tabs open and nothing you can actually share with your team. The worst part is the second round of work: rewriting posts into something usable.

This Telegram digest automation hits digital marketers hardest, but brand managers and analysts feel it too. You end up with the same mess: lots of noise, not enough signal, and a constant fear you missed the one update that mattered.

This workflow pulls fresh social updates with BrowserAct, cleans them up with AI, then publishes a curated digest straight into your Telegram channel. You will see how it works, what you need, and where people usually get stuck.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: BrowserAct + Telegram: curated social digests

Click to explore

flowchart LR

    subgraph sg0["Timed Automation Kickoff Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Timed Automation Kickoff", pos: "b", h: 48 }
        n1["<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/>Launch Scrape Request"]
        n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Validate Task Start", pos: "b", h: 48 }
        n3@{ icon: "mdi:cog", form: "rounded", label: "Delay Before Retry", pos: "b", h: 48 }
        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/httprequest.dark.svg' width='40' height='40' /></div><br/>Fetch Task Status"]
        n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Task Completion", pos: "b", h: 48 }
        n6@{ icon: "mdi:cog", form: "rounded", label: "Pause for Status", pos: "b", h: 48 }
        n7@{ icon: "mdi:robot", form: "rounded", label: "AI Refinement Agent", pos: "b", h: 48 }
        n8@{ icon: "mdi:brain", form: "rounded", label: "Gemini Chat Engine", pos: "b", h: 48 }
        n9@{ icon: "mdi:robot", form: "rounded", label: "Structured Parse Output", pos: "b", h: 48 }
        n10["<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/>Transform Items Script"]
        n11@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Image Presence Check", pos: "b", h: 48 }
        n12["<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 Telegram Text"]
        n13["<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 Telegram Photo"]
        n2 --> n4
        n2 --> n3
        n5 --> n7
        n5 --> n6
        n11 --> n12
        n11 --> n13
        n6 --> n4
        n3 --> n1
        n7 --> n10
        n1 --> n2
        n4 --> n5
        n0 --> n1
        n10 --> n11
        n8 -.-> n7
        n9 -.-> n7
    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 n0 trigger
    class n7,n9 ai
    class n8 aiModel
    class n2,n5,n11 decision
    class n1,n4 api
    class n10 code
    classDef customIcon fill:none,stroke:none
    class n1,n4,n10,n12,n13 customIcon

The Problem: Social “Monitoring” Turns Into Endless Scrolling

Keeping up with trends and competitor moves sounds simple until you do it every day. You skim feeds, save a few posts, copy links into notes, then try to explain why they matter in a Slack thread or a meeting. Multiply that by a few topics (your brand, competitors, industry keywords) and you have a recurring time leak that never shows up on a calendar. And because it’s manual, the quality changes depending on your mood, your focus, and how busy the day is. Honestly, it is easy to miss the one post you should have acted on.

The friction compounds. Here’s where it breaks down in real life.

You spend about 30–60 minutes collecting “interesting” posts, then another chunk of time rewriting them into a digest someone will actually read.
Duplicates creep in fast when the same story gets reposted, quote-tweeted, and summarized by five different accounts.
It’s hard to share consistently because the process depends on one person remembering to do it (and having the patience).
Manual summaries introduce errors, missed context, or vague takeaways that don’t lead to action.

The Solution: BrowserAct + AI Curation Sent to Telegram

This workflow turns social monitoring into a repeatable system. On a schedule you choose, n8n tells BrowserAct to run a social aggregation job (the workflow is designed around BrowserAct’s “Twitter/X Content Aggregation” template). Because scraping and aggregation take time, the workflow checks job status, waits, then checks again until the data is ready. Once results come back, an AI Agent (powered by Google Gemini in this template) summarizes what matters, removes duplicates, and produces clean, structured output. A small transformation step reshapes the items into “ready to publish” messages, then the workflow decides whether each post should be sent as a text message or as a photo message. Finally, Telegram receives a neat digest your team can skim and forward.

The workflow starts with a timed trigger, then runs and polls a BrowserAct job via HTTP requests. AI refines the raw feed into curated updates, and Telegram gets the final posts in the right format (text or image) without you doing the cleanup.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

A scheduled pull of fresh X/Twitter-style updates via BrowserAct, without manual searching.
Status polling with Wait and If checks, so you are not babysitting a scraping job.
AI summarization and deduplication using an Agent with a Gemini chat model.
Telegram publishing that automatically chooses text-only or photo messages based on the content.

Most teams get about 5 hours back each week by cutting scrolling and rewriting.
A consistent digest that appears even when you are busy, traveling, or in meetings all day.
Cleaner internal sharing, because the updates arrive in one channel in a readable format.
Fewer repeats and “we already saw this” moments, since duplicates are removed upstream.
Faster reaction time on trends and competitor moves, which means better content and campaign timing.

Example: What This Looks Like

Say you want a weekday digest for two competitor accounts and three industry topics. Manually, that’s usually about 10 minutes per source to find posts, plus another 20 minutes to rewrite and dedupe, so roughly 60–90 minutes a day. With this workflow, you spend about 5 minutes setting the schedule and prompt once, then the run is automatic: BrowserAct collects, AI summarizes, Telegram receives the digest. You skim in 5 minutes, forward what matters, and move on.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
BrowserAct to aggregate social home page updates
Telegram to publish digests into a channel
BrowserAct API key + Workflow ID (from your BrowserAct dashboard/workflow settings)

Skill level: Intermediate. You’ll paste API keys, update one workflow_id value, and test a run end-to-end.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A scheduled trigger kicks things off. n8n runs on a timer you control (weekday mornings, every hour, twice a day). No manual “go run it” step.

BrowserAct gets the raw updates. An HTTP request launches your BrowserAct aggregation workflow, then n8n checks that the job actually started. If it’s still processing, n8n waits and retries until the status says the output is ready.

AI turns the feed into a digest. The AI Agent takes the collected posts and produces a cleaner, deduplicated set of updates. In plain terms, it reduces noise and rewrites the content so it reads like a briefing, not a stream of links.

Telegram receives the final posts. A quick content check decides whether there’s an image. If yes, a Telegram photo message is sent; if not, it posts as text. The result looks polished in-channel, so people actually read it.

You can easily modify the schedule or the AI prompt to match your brand voice and what you consider “important.” See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set the timing for when the social content digest runs automatically.

Add and open Timed Automation Kickoff.
Set the schedule rule interval to hours and Hours Interval to 12.
Confirm Timed Automation Kickoff is connected to Launch Scrape Request.

Step 2: Connect BrowserAct Task Launch and Status Checks

Configure the HTTP requests that start the scrape and retrieve task progress.

Open Launch Scrape Request and set URL to https://api.browseract.com/v2/workflow/run-task.
Set Method to POST and enable Send Body.
In Body Parameters, set workflow_id to [YOUR_ID].
Credential Required: Connect your httpBearerAuth credentials for Launch Scrape Request.
Open Fetch Task Status and set URL to https://api.browseract.com/v2/workflow/get-task.
Enable Send Query and set task_id to {{ $json.id }}.
Credential Required: Connect your httpBearerAuth credentials for Fetch Task Status.

Tip: Keep Launch Scrape Request set to continue regular output on error so the retry logic can handle temporary failures.

Step 3: Configure Task Validation and Polling Logic

Ensure the workflow retries and polls until the task completes.

In Validate Task Start, verify the conditions check {{ $json.error }} does not exist and {{ $json.id }} is not null.
Confirm the false branch from Validate Task Start goes to Delay Before Retry.
Set Delay Before Retry Amount to 20 (seconds).
In Check Task Completion, verify the status condition checks {{ $json.status }} equals finished.
Set Pause for Status to Unit minutes and Amount 1.

⚠️ Common Pitfall: If the task status never reaches finished, the workflow will keep polling. Make sure the BrowserAct workflow ID is correct in Launch Scrape Request.

Step 4: Set Up AI Refinement and Structured Parsing

Refine and structure the scraped content with the AI agent and parser.

Open AI Refinement Agent and set Prompt to the provided text, including the expression {{ $json.output.string }}.
Ensure AI Refinement Agent uses the connected Gemini Chat Engine as its language model.
Credential Required: Connect your googlePalmApi credentials in Gemini Chat Engine (the language model for AI Refinement Agent).
Open Structured Parse Output and set JSON Schema Example to the provided structure with refined_output fields.
Keep Structured Parse Output linked as the output parser on AI Refinement Agent (credentials are applied to the parent node, not this parser).
Open Transform Items Script and keep the provided JavaScript to split items into individual outputs.

Step 5: Configure Telegram Output Routing

Send messages with or without images based on the presence of Pic.

In Image Presence Check, confirm the condition compares {{ $json.Pic }} to no picture.
Open Send Telegram Text and set Text to {{ $json.Title }} {{ $json.Summary }} BY: {{ $json.PublishedBy }} {{ $json.Url }}.
Set Chat ID in Send Telegram Text to [YOUR_ID].
Credential Required: Connect your telegramApi credentials for Send Telegram Text.
Open Send Telegram Photo, set Operation to sendPhoto, and set File to {{ $json.Pic }}.
Set Chat ID in Send Telegram Photo to [YOUR_ID], and keep the caption using {{ $json.Title }}, {{ $json.Summary }}, {{ $json.PublishedBy }}, and {{ $json.Url }}.
Credential Required: Connect your telegramApi credentials for Send Telegram Photo.

⚠️ Common Pitfall: If [YOUR_ID] isn’t replaced, Telegram will reject the request. Use the numeric chat ID for your target channel or user.

Step 6: Test and Activate Your Workflow

Run a full test to confirm the scrape, AI refinement, and Telegram delivery paths.

Click Execute Workflow and monitor the run from Timed Automation Kickoff to Send Telegram Text or Send Telegram Photo.
Verify that Fetch Task Status returns a finished status and that AI Refinement Agent outputs structured items.
Confirm Telegram messages arrive with correct formatting and images when {{ $json.Pic }} is valid.
When satisfied, toggle the workflow to Active to run every 12 hours automatically.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

BrowserAct credentials can expire or need specific permissions. If things break, check your BrowserAct API key and the selected template access in BrowserAct 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

How long does it take to set up this Telegram digest automation?

About 30 minutes if you already have BrowserAct and Telegram credentials.

Do I need coding skills to automate Telegram digests?

No. You’ll mostly paste credentials and change the workflow_id in the HTTP request. The included Code node is already written for you.

Is n8n free to use for this Telegram digest automation workflow?

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 BrowserAct and Gemini usage costs on their side.

Where can I host n8n to run this Telegram digest automation?

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.

Can I customize this Telegram digest automation workflow for Slack instead of Telegram?

Yes, but you’ll swap the destination nodes. Replace “Send Telegram Text” and “Send Telegram Photo” with Slack message nodes, then adjust formatting in the “Transform Items Script” node so the output fits how your team reads updates. Many people also customize the AI Agent prompt to include a short “why this matters” line for each item.

Why is my BrowserAct connection failing in this workflow?

Most of the time it’s an API key issue or the wrong BrowserAct workflow_id inside the “Launch Scrape Request” HTTP Request node. Check that the BrowserAct template is set up (“Twitter/X Content Aggregation”), then confirm the Run node points to the correct ID. If the job starts but never completes, your polling loop may be too aggressive; increase the Wait duration so the next status check happens a little later. Also watch for rate limits if you run this very frequently.

How many posts can this Telegram digest automation handle?

A typical run can handle dozens of items comfortably; if you push hundreds at once, you’ll want batching and stricter deduping in the AI prompt.

Is this Telegram digest automation better than using Zapier or Make?

For a polling + AI curation workflow like this, n8n is usually the easier fit because you can loop, wait, branch, and transform data without paying extra for every tiny step. Self-hosting is also a big deal if you run frequent digests. Zapier or Make can still work if you keep it simple, but long-running jobs (start, wait, check, wait, check) are where they can feel awkward. If you’re unsure, Talk to an automation expert and describe your volume and timing needs.

Set this up once and your Telegram channel becomes the place where “what’s happening” shows up automatically. Less scrolling. Better decisions.

BrowserAct + Telegram: curated social digests

How This Automation Works

n8n Workflow Template: BrowserAct + Telegram: curated social digests

The Problem: Social “Monitoring” Turns Into Endless Scrolling