🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home n8n Workflow
January 22, 2026

BrowserAct + Telegram: only the best job matches

Lisa Granqvist Partner Workflow Automation Expert

You find a “great” job post, click through, and it’s already gone. Or worse, it was never relevant in the first place. After a week of that, job hunting starts to feel like a second job you didn’t apply for.

This Telegram job matches automation hits job seekers first, honestly, but recruiters and solo market analysts feel the same overload. Instead of endless tabs, you get a short list that actually matches your resume, delivered right where you already check messages.

Below, you’ll see how the workflow pulls fresh listings with BrowserAct, uses AI to filter them, then sends only the best matches to Telegram in a clean format you can act on fast.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: BrowserAct + Telegram: only the best job matches

The Problem: Job boards create noise, not clarity

Most job feeds are built to keep you scrolling, not to help you decide. So you bounce between tabs, copy titles into notes, and try to remember which role required “5+ years” versus which one was actually realistic. Duplicates show up across boards, reposts look new, and a promising listing turns into 20 minutes of reading before you even know if it fits. The mental load is the sneaky part. After a while, you stop applying because you’re tired, not because there aren’t opportunities.

It adds up fast. Here’s where it breaks down in real life.

  • You spend about 1–2 hours a day reading listings that were never a match.
  • Duplicates and reposts clog your “saved jobs,” so you lose track of what you already reviewed.
  • Matching your resume to the role happens too late, after you’ve already invested attention.
  • Good opportunities expire while you’re still sorting through the junk.

The Solution: BrowserAct scrape + AI resume matching + Telegram delivery

This workflow flips the order of operations. Instead of you reading everything and then deciding what fits, BrowserAct collects the newest listings first, then an AI Agent compares them to your resume before anything ever reaches your inbox. You start the run manually (or schedule it later), n8n kicks off a BrowserAct “Job Market Intelligence” scrape through an HTTP request, and then it checks status until the scrape is complete. Once the data is ready, the AI Agent (powered by Google Gemini models) filters and ranks listings based on your resume criteria. A small code step formats the results into a human-readable shortlist, and Telegram delivers the final set as a message you can immediately act on.

The workflow starts with a BrowserAct API request to gather fresh job offers. Then it waits and re-checks until the scrape returns complete data. Finally, AI filters for fit and Telegram sends the curated matches, so you’re not triaging noise.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you review job boards 5 days a week, and you normally scan about 40 listings a day. If you spend even 2 minutes per listing, that’s roughly 80 minutes daily, plus another 20 minutes saving and de-duping. With this workflow, you click Execute, wait for the scrape and AI pass (often around 20–30 minutes in the background), then you spend about 5–10 minutes reading a Telegram shortlist. That’s about an hour back per day, without applying to fewer roles.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • BrowserAct for scraping fresh job listings
  • Telegram to receive your curated shortlist
  • BrowserAct API token + Workflow ID (get it from your BrowserAct dashboard)

Skill level: Beginner. You’ll paste credentials, edit one prompt (your resume), and test a run.

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

How It Works

You trigger a run. By default it’s manual (click “Execute workflow”), which is nice while you’re testing. Once it’s dialed in, you can switch to a schedule so it runs every morning.

BrowserAct starts scraping. n8n sends an HTTP request to the BrowserAct API using your token and the BrowserAct workflow ID for the “Job Market Intelligence” template. That scrape collects the newest job offers from your configured sources.

n8n waits until the data is truly ready. A set of checks (If nodes) and Wait loops poll scrape status. If the task is incomplete, it pauses and tries again. If the response looks wrong, it loops back and re-requests so you don’t process half-baked data.

AI filters and Telegram delivers. The AI Agent uses Gemini chat models to compare the scraped listings to your resume content, then a code step formats the shortlist into readable bullets. Finally, Telegram sends the message to your channel or direct chat.

You can easily modify the resume criteria to target different roles based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Manual Trigger

This workflow starts manually so you can test the scrape, matching, and notification pipeline end-to-end.

  1. Add the Manual Launch Trigger node as your trigger.
  2. Leave all fields at their defaults since the trigger is manual.
  3. Connect Manual Launch Trigger to Start Scrape Request.

Step 2: Connect the Scrape Request & Task Status Checks

These nodes start the BrowserAct workflow task and poll for completion.

  1. Open Start Scrape Request and set URL to https://api.browseract.com/v2/workflow/run-task.
  2. Set Method to POST, enable Send Body, and set Authentication to genericCredentialType with Generic Auth Type httpBearerAuth.
  3. Under Body Parameters, set workflow_id to [YOUR_ID].
  4. Credential Required: Connect your httpBearerAuth credentials in Start Scrape Request.
  5. Open Check Scrape Status and set URL to https://api.browseract.com/v2/workflow/get-task with Send Query enabled.
  6. Set the query parameter task_id value to {{ $json.id }}.
  7. Credential Required: Connect your httpBearerAuth credentials in Check Scrape Status.
Tip: The Start Scrape Request node is set to continue on error. Keep this behavior if your scraping service returns temporary errors.

Step 3: Configure Polling Logic and Retry Delays

These nodes validate the task response and loop until the scrape is complete.

  1. In Validate Task Response, verify the conditions use {{ $json.error }} (not exists) and {{ $json.id }} (not equals null).
  2. Confirm the flow: Validate Task ResponseCheck Scrape Status on success, and Validate Task ResponseShort Delay Loop on failure.
  3. Set Short Delay Loop to wait 1 minute and route back to Start Scrape Request.
  4. In Check Task Complete, ensure conditions use {{ $json.error }} (not exists) and {{ $json.status }} equals finished.
  5. Set Pause Before Retry to wait 2 minutes and route back to Check Scrape Status.
⚠️ Common Pitfall: If Check Scrape Status receives a missing or null {{ $json.id }}, the loop can stall. Always ensure Start Scrape Request returns a valid task ID.

Step 4: Set Up the AI Matching Agent

The AI agent compares your resume against scraped job data and outputs structured results.

  1. Open Resume Match Agent and confirm the prompt includes {{ $json.output.string }} and outputs the required format_final_json_response structure.
  2. Ensure Resume Match Agent has Needs Fallback enabled and Has Output Parser enabled.
  3. Connect Gemini Primary Model to Resume Match Agent as the main language model.
  4. Credential Required: Connect your googlePalmApi credentials in Gemini Primary Model.
  5. Connect Gemini Fallback Model as the fallback language model and set Model Name to models/gemini-2.0-flash.
  6. Credential Required: Connect your googlePalmApi credentials in Gemini Fallback Model.
  7. Attach Parse Structured Output as the output parser and keep the JSON Schema Example exactly as defined.
Tip: Parse Structured Output is an AI sub-node. Add credentials on Gemini Primary Model and Gemini Fallback Model, not on the parser itself.

Step 5: Format Results and Send Telegram Alerts

Format the AI output into individual items and send a Telegram message for each match.

  1. In Format Result List, keep the JavaScript code that maps $input.first().json.output.Request into individual text objects.
  2. Confirm the flow: Resume Match AgentFormat Result ListDispatch Telegram Alert.
  3. Open Dispatch Telegram Alert and set Text to Title: {{ $json.text.Title }} Summary :{{ $json.text.Summary }} Needs: {{ $json.text.Needs }} Educarion: {{ $json.text.Education }} {{ $json.text.Link }}.
  4. Set Chat ID to [YOUR_ID].
  5. Credential Required: Connect your telegramApi credentials in Dispatch Telegram Alert.
⚠️ Common Pitfall: If [YOUR_ID] is left unchanged, Dispatch Telegram Alert will fail silently. Replace it with your Telegram chat ID.

Step 6: Test and Activate Your Workflow

Run a manual test to confirm the scrape, AI matching, formatting, and Telegram notification outputs.

  1. Click Execute Workflow on Manual Launch Trigger to run the full flow.
  2. Verify Start Scrape Request returns a task ID and Check Scrape Status eventually shows finished.
  3. Confirm Resume Match Agent outputs the structured Request array and Format Result List splits items correctly.
  4. Check Telegram for messages sent by Dispatch Telegram Alert with title, summary, needs, education, and link.
  5. When satisfied, set the workflow to Active for production use.
🔒

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 token in the BrowserAct dashboard first.
  • If you’re using Wait nodes or external scraping, 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 job matches automation?

About 20–40 minutes if you already have your BrowserAct and Telegram credentials.

Do I need coding skills to automate Telegram job matches?

No. You’ll connect accounts, paste tokens, and tweak the resume prompt. The only “code” piece is already included to format the output.

Is n8n free to use for this Telegram job matches 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 Gemini usage costs (often just a few dollars a month at typical job-search volume).

Where can I host n8n to run this 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 job matches automation for multiple resumes and role types?

Yes, but you’ll want to duplicate the AI Agent prompt and store a few resume variants (for example: “Product Marketing,” “Growth,” and “Content”). You can route listings through different prompts using a Switch node, then send separate Telegram messages per role type. Common customizations include stricter location rules, salary thresholds, and excluding agencies or contract roles.

Why is my BrowserAct connection failing in this workflow?

Usually it’s an invalid or expired BrowserAct API token. Generate a new token in BrowserAct, update it in the HTTP Request node, and re-run the workflow. If it still fails, check that the BrowserAct workflow_id you’re calling is correct and that the “Job Market Intelligence” template is active in your account.

How many job listings can this Telegram job matches automation handle?

A lot. On n8n Cloud Starter, most people can run this daily without thinking about limits, and higher plans handle more volume. If you self-host, there’s no execution cap, so it mainly depends on your server and how heavy your scrape is. Practically, teams commonly process hundreds of listings per run and still end up with a shortlist of 5–20 matches.

Is this Telegram job matches automation better than using Zapier or Make?

For this use case, n8n is usually the better fit because it handles loops, waits, and conditional checks without getting awkward or expensive. You also get tighter control over how the scrape is polled, which matters with BrowserAct-style tasks that take time to finish. Zapier and Make can work, but the minute you need retries, structured AI output parsing, or branching logic, it gets fiddly. If you want, you can also self-host n8n and run as often as you like. Talk to an automation expert if you’re deciding between platforms.

When the workflow does the filtering, you stop wasting attention on listings that were never meant for you. Set it up once, tune the resume prompt as you grow, and let Telegram deliver the shortlist.

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.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Launch login modal Launch register modal