Skip to main content

Search the web with MCP-based Brave Search Engine on Telegram

Workflow preview

Workflow preview
100%
Search the web with MCP-based Brave Search Engine on Telegram preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This workflow enables users to perform web searches directly from Telegram using the Brave search engine. By simply sending the command /brave followed by a query, the workflow retrieves search res...

Best for

  • Personal Productivity automation workflows
  • AI RAG automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-mcp.mcpclient, n8n-nodes-base.code, n8n-nodes-base.telegram, n8n-nodes-base.telegramtrigger, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.set

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Davide.

Original n8n.io source

1.1 Workflow description

Title
Search the web with MCP-based Brave Search Engine on Telegram
Workflow name
Search the web with MCP-based Brave Search Engine on Telegram

This workflow enables users to perform web searches directly from Telegram using the Brave search engine. By simply sending the command /brave followed by a query, the workflow retrieves search results from Brave and returns them as a Telegram message.

This workflow is ideal for users who want a quick and private way to search the web without switching between apps. 🚀

This workflow is a powerful tool for automating interactions with Brave tools through Telegram, providing users with quick and easy access to information directly in their chat.

Below is a breakdown of the workflow:


1. How It Works

The workflow is designed to process user queries from Telegram, execute a Brave tool via the MCP Client, and send the results back to the user. Here's how it works:

  1. Telegram Trigger:

    • The workflow starts with the Telegram Trigger node, which listens for new messages in a Telegram chat.
    • When a message is received, the workflow checks if it starts with the command /brave.
  2. Filter Messages:

    • The If node filters messages that start with /brave. If the message doesn't start with /brave, the workflow stops.
  3. Edit Fields:

    • The Edit Fields node extracts the text of the message for further processing.
  4. Clean Query:

    • The Clean Query node removes the /brave command from the message, leaving only the user's query.
  5. List Brave Tools:

    • The List Brave Tools node retrieves the list of available tools from the MCP Client.
  6. Execute Brave Tool:

    • The Exec Brave Tool node executes the first tool in the list using the cleaned query as input.
  7. Send Message:

    • The Send Message node sends the result of the Brave tool execution back to the user in the Telegram chat.

2. Preliminary Steps
  • Access to an n8n self-hosted instance and install the Community node "n8n-nodes-mcp". Please see this easy guide
  • Get your Brave Search API Key: https://brave.com/search/api/
  • Telegram Bot Access Token

In "List Brave Tools" create new credential as shown in this image

In Environment field set this value: BRAVE_API_KEY=your-api-key


3. Set Up Steps

To set up and use this workflow in n8n, follow these steps:

  1. Telegram Configuration:

    • Set up Telegram credentials in n8n for the Telegram Trigger and Send Message nodes.
    • Ensure the Telegram bot is authorized to read messages and send responses in the chat.
  2. MCP Client Configuration:

    • Set up MCP Client credentials in n8n for the List Brave Tools and Exec Brave Tool nodes.
    • Ensure the MCP Client is configured to interact with Brave tools.
  3. Test the Workflow:

    • Send a message starting with /brave followed by a query (e.g., /brave search for AI tools) to the Telegram chat.
    • The workflow will:
      • Process the query.
      • Execute the Brave tool via the MCP Client.
      • Send the result back to the Telegram chat.
  4. Optional Customization:

    • Modify the workflow to include additional features, such as:
      • Adding more commands or tools.
      • Integrating with other APIs or services for advanced use cases.
      • Sending notifications via other channels (e.g., email, Slack)

Need help customizing?

Contact me for consulting and support or add me on Linkedin.

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 - List Brave Tools

Type / Role
n8n-nodes-mcp.mcpClient - mcpClient
Config choices
Version 1

Block 2 - Exec Brave tool

Type / Role
n8n-nodes-mcp.mcpClient - mcpClient
Config choices
Version 1

Block 3 - Clean query

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 4 - Send message

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

Block 5 - Get Message

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

Block 6 - Search with Brave?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 7 - Sticky Note

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

Block 8 - Sticky Note1

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

Block 9 - Sticky Note2

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

Block 10 - Sticky Note3

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

Block 11 - Sticky Note4

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

Block 12 - Sticky Note5

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

Block 13 - Sticky Note6

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

Block 14 - Get Text

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

3. Summary Table

Workflow Search the web with MCP-based Brave Search Engine on Telegram
Complexity intermediate
Nodes 14
Categories Personal Productivity, AI RAG
Author Davide
Published 20 Mar 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3231/3231.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 Search the web with MCP-based Brave Search Engine on Telegram do?

This workflow enables users to perform web searches directly from Telegram using the Brave search engine. By simply sending the command /brave followed by a query, the workflow retrieves search res...

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 Personal Productivity, AI RAG use case.