MCP Client with Brave and Telegram
Configured with Mcp Client, Telegram, Telegram Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Integration
- Code
- Messaging
- Trigger
- Routing
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| List Brave Tools | Integration | Mcp Client | See node parameters |
| Exec Brave tool | Integration | Mcp Client | executeTool |
| Clean query | Code | Code | See node parameters |
| Send message | Messaging | Telegram | See node parameters |
| Get Message | Trigger | Telegram Trigger | See node parameters |
| Search with Brave? | Routing | If | See node parameters |
| Get Text | Transform | Edit Fields | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
mcpClientApitelegramApi
Workflow notes
PRELIMINARY STEPS
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
SET MCP BRAVE TOOL
SET MCP BRAVE TOOL
In "List Brave Tools" create new credential as shown in this image
In Environment field set this value: BRAVE_API_KEY=your-api-key
Sticky Note2
the search only occurs when the command "/brave" is present in the message
Sticky Note3
I clean the message by removing the "/brave" command
Sticky Note4
Get all available Brave search tools
Sticky Note5
I get the search results
MCP-based Brave Search Engine on Telegram
MCP-based Brave Search Engine on Telegram
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.
This n8n 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.
MCP Client with Brave and Telegram
MCP Client with Brave and Telegram
Purpose and structure
This folder contains the MCP Client with Brave and Telegram workflow. Its executable nodes use code, if, mcpClient, set, telegram, telegramTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Get Message
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/1001_Telegram_Stickynote_Automation_Triggered.json MIT; preserve source notices.