Skip to main content

Verify service providers via Telegram using BrowserAct and Google Gemini

Workflow preview

Workflow preview
100%
Verify service providers via Telegram using BrowserAct and Google Gemini preview
Open on n8n.io

1. Workflow Overview

Verify service providers using Telegram and BrowserAct This workflow transforms your Telegram bot into an intelligent vendor vetting tool. Send the name and location of a service provider (e.g., "M...

Best for

  • Market Research automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatgooglegemini, n8n-nodes-base.switch, n8n-nodes-base.telegram, n8n-nodes-base.telegramtrigger, n8n-nodes-browseract.browseract, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Madame AI Team | Kai.

Original n8n.io source

1.1 Workflow description

Title
Verify service providers via Telegram using BrowserAct and Google Gemini
Workflow name
Verify service providers via Telegram using BrowserAct and Google Gemini

Verify service providers using Telegram and BrowserAct

This workflow transforms your Telegram bot into an intelligent vendor vetting tool. Send the name and location of a service provider (e.g., "Mr. Rooter in Detroit"), and it will automatically scrape Google Maps for reviews, cross-reference the business with OpenCorporates to verify its legal status, and deliver a detailed legitimacy report back to your chat.

Target Audience

Procurement managers, homeowners hiring contractors, and anyone needing to verify the legitimacy of a business quickly.

How it works

  1. Analyze Intent: The workflow receives a message via Telegram. An AI Agent classifies it: is it a casual chat or a verification request?
  2. Extract Details: If a request is detected, the AI extracts the Provider Name and Location from your message.
  3. Scrape Data: BrowserAct executes a background task to scrape Google Maps for reviews/ratings and search OpenCorporates for legal entity filings.
  4. Human Verification (CAPTCHA): If the scraper encounters a CAPTCHA, the workflow pauses and sends a Telegram alert with a link. Once you solve it, the workflow resumes automatically.
  5. Verify & Report: A second AI Agent analyzes the gathered data. It compares the Google listing with the corporate registry to determine if the business is "Verified" (matched), "Unverified" (local only), or "Not Found."
  6. Deliver: The bot sends a formatted HTML report with the verdict, ratings, and active locations to your Telegram chat.

How to set up

  1. Configure Credentials: Connect your Telegram, BrowserAct, and Google Gemini accounts in n8n.
  2. Prepare BrowserAct: Ensure the Vendor Vetting and verification bot template is saved in your BrowserAct account.
  3. Configure Telegram: Ensure your bot is created via BotFather and the API token is added to the Telegram credentials.
  4. Activate: Turn on the workflow.
  5. Test: Send a message like "Is Acme Plumbing in Chicago legit?" to your bot to start the verification process.

Requirements

  • BrowserAct account with the Vendor Vetting and verification bot template.
  • Telegram account (Bot Token).
  • Google Gemini account.

How to customize the workflow

  1. Add More registries: Update the BrowserAct template to search other databases like BBB (Better Business Bureau) or Yelp for broader verification.
  2. Change Output Format: Modify the system prompt in the Verify the provide agent to output a simple "Pass/Fail" score instead of a detailed report.
  3. Save Reports: Add a Google Sheets or Notion node at the end to log every verification request and its result for future reference.

Need Help?


Workflow Guidance and Showcase Video

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 2 - Validate user inputs

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3

Block 3 - Validation bot

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

Block 4 - Human verification Switch

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.4

Block 5 - Verify Data

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

Block 6 - Ask For human verification

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 7 - User Sends Message to Bot

Type / Role
n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices
Version 1.2

Block 8 - Get Vendor Data & Stats

Type / Role
n8n-nodes-browseract.browserAct - browserAct
Config choices
Version 1

Block 9 - Process Initialization Alert

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 10 - Give Time to Complete Verification

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 11 - Analyze Data & Verify Providers

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3

Block 12 - Get Data From BrowserAct

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 13 - Send Failure Alert

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 14 - Result Post Delivery

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 15 - Answer the User

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 16 - Chat bot Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3

Block 17 - Chat bot

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

Block 18 - Validation Type Switch

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.4

Block 19 - Workflow Overview

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Step 1 Explanation

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Step 2 Explanation

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Step 3 Explanation

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Step 4 Explanation

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Verify service providers via Telegram using BrowserAct and Google Gemini
Complexity advanced
Nodes 24
Categories Market Research, AI RAG
Author Madame AI Team | Kai
Published 03 Jan 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/12432/12432.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Verify service providers via Telegram using BrowserAct and Google Gemini do?

Verify service providers using Telegram and BrowserAct This workflow transforms your Telegram bot into an intelligent vendor vetting tool. Send the name and location of a service provider (e.g., "M...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Market Research, AI RAG use case.