OpenRuna
Sign in
← Workflows

0882_Telegram_Googletaskstool_Create_Triggered

21 nodes · telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow

Engine
n8n
Nodes
21
Trigger
scheduled/triggered
Source file
0882_Telegram_Googletaskstool_Create_Triggered.json

Workflow flow

IntegrationsTelegramMCPAgentMcpClientToolLmChatOpenAiMemoryBufferWindowGoogleTasksToolSwitchOpenAI@n8n/n8n-nodes-langchain.mcp@n8n/n8n-nodes-langchain.agent@n8n/n8n-nodes-langchain.mcpClientTool+4 more
100%
TRIGGER

Incoming Message

Telegram

TRIGGER

MCP Server Trigger

@n8n/n8n-nodes-langchain.mcp

MCP Client

@n8n/n8n-nodes-langchain.mcpClientTool

OpenAI Chat Model

@n8n/n8n-nodes-langchain.lmChatOpenAi

Simple Memory

@n8n/n8n-nodes-langchain.memoryBufferWindow

create_todays_task

GoogleTasksTool

create_upcoming_task

GoogleTasksTool

complete_task

GoogleTasksTool

get_todays_tasks

GoogleTasksTool

get_upcoming_tasks

GoogleTasksTool

Switch

Switch

chatInput

Set

audio_id

Set

download_audio

Telegram

transcribeAudio

@n8n/n8n-nodes-langchain.openAi

audioInput

Set

AI Agent

@n8n/n8n-nodes-langchain.agent

chatOutput

Set

sendMessage

Telegram

19 steps · flows top to bottom, branches left to right

Browse by integration

telegrammcpagentmcpClientToollmChatOpenAimemoryBufferWindowgoogleTasksToolswitchopenAi
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: 0882_Telegram_Googletaskstool_Create_Triggered. 21 nodes across telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow, googleTasksTool, switch, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"0882_Telegram_Googletaskstool_Create_Triggered" automates a telegram-to-mcp flow in n8n across 21 nodes. 21 nodes · telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Benchmark it against your current telegram integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 21-node flow from scratch.
  • Share it with your team as a documented reference for scheduled/triggered automations in the telegram stack.
  • Study how data moves from telegram to mcp before building your own variant.

Example output

Imported into n8n, "0882_Telegram_Googletaskstool_Create_Triggered" exposes 21 configured nodes. Trigger type: scheduled/triggered. Integrations: telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow, googleTasksTool, switch. Open each node after import to map credentials to your own telegram and mcp accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "0882_Telegram_Googletaskstool_Create_Triggered" into Claude and ask it to explain each of the 21 nodes. Claude is good at suggesting credential mappings for telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow, googleTasksTool, switch, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0882_Telegram_Googletaskstool_Create_Triggered" to your accounts — which telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow, googleTasksTool, switch credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 21 nodes.

Frequently asked questions

How do I import "0882_Telegram_Googletaskstool_Create_Triggered" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "0882_Telegram_Googletaskstool_Create_Triggered" use?
It uses: telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow, googleTasksTool, switch. The flow diagram above shows how each service connects across the 21 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own telegram and mcp credentials in n8n after import.
What trigger type does "0882_Telegram_Googletaskstool_Create_Triggered" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "0882_Telegram_Googletaskstool_Create_Triggered" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for telegram, mcp, agent, mcpClientTool, lmChatOpenAi, memoryBufferWindow, googleTasksTool, switch.

Related resources