Skip to content
ExpertEnterpriseChatbots & Conversational AIWebhook trigger31 nodes

Power an AI agent task: Google Sheets & Telegram for support bots

Fires the moment a webhook arrives across Google Sheets, Telegram and Slack, looks the answer up in a vector store, then hands the decision to an AI agent. Built for support bots, around a "Normalize Conversation Payload" step, in 31 documented nodes.

Power an AI agent task with Telegram and log the results for Support Bots. An original, ready-to-import n8n workflow built around the 'AI Agent' pattern for customer support. It fires on a webhook and orchestrates 31 nodes across Google Sheets, Telegram, Slack. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. Nothing slips through the cracks.

Key benefits

  • Keeps Google Sheets and Telegram in step for support bots, without anyone re-typing a row
  • Safe to re-run: records already in Google Sheets or Telegram are skipped, across all 31 nodes of this support-bots build
  • A failed Google Sheets or Telegram call is retried rather than dropped, at any of the 31 nodes in this support-bots build
  • Every support-bots run leaves an audit row behind, alongside Google Sheets
  • The support-bots AI step is isolated from Google Sheets, so models swap without touching the other 31 nodes

Use cases

  • Teams keeping Google Sheets and Telegram aligned by hand for support bots
  • Answering support-bots questions from your own indexed documents, then replying in Google Sheets
  • Support bots work that needs a judgement call per item before it reaches Google Sheets
  • Pushing support-bots events into Google Sheets and Telegram the moment they land, not on the next poll

Integrations

Google SheetsTelegramSlackNotionHTTP / REST APIPostgreSQLGroq

Workflow preview (31 nodes)

The template's actual node layout and connections. Node parameters and credential slots unlock with the download.

On Telegram EventTelegram TriggerNormalize Conversation …CodeAnswer from Knowledge B…AgentGroq Chat ModelLm Chat GroqKnowledge Base RetrieverVector Store PGVectorQuery EmbeddingsEmbeddings Open AiGrounded Answer Found?IfDeliver Answer via SlackSlackLog Knowledge GapGoogle SheetsFlag Gap to KB OwnersTelegramEnrich with Reference D…Http RequestFold In Enrichment Fiel…SetLoad Previous SnapshotNotionCompute Drift vs Snapsh…CodeStamp Completion TimeDate TimePersist Run MetadataExecution DataSerialize Run Output (C…Convert To FileArchive Row SnapshotGoogle SheetsOffload to Post-Process…Execute WorkflowRecord Sub-workflow Res…Execution DataFingerprint for Idempot…CodeDrop Already-Processed …Remove DuplicatesGuard Non-Empty messageFilterAlign Field NamesRename KeysCap Batch VolumeLimitSummarize Run StatsSetAppend Audit Row (Notio…NotionSend Summary to SlackSlackCapture Failure ContextSetEscalate Failure to Tel…TelegramPark in Dead-Letter Que…Google Sheets

What's inside (31 nodes)

A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.

AgentCodeConvert To FileDate TimeEmbeddings Open AiExecute WorkflowExecution DataFilterGoogle SheetsHttp RequestIfLimitLm Chat GroqNotionRemove DuplicatesRename KeysSetSlackTelegramTelegram TriggerVector Store PGVector

Agent tools included (1)

An AI Agent is only as capable as the tools wired into it. These are read from the template's own graph — every one is a real node in the file you download.

  • Knowledge Base Retriever · Vector Store PGVector

This agent runs without conversation memory - each run starts from the incoming request.

From download to running in 3 steps

  1. 1
    Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
  2. 2
    Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
  3. 3
    Activate. Run it once to test, then toggle Active. The automation is live.

What you'll learn

Architect level

The deepest tier - sub-workflow delegation, state snapshots, and full observability.

  • Moving data between Telegram, Slack and Google Sheets in a single run
  • Normalising timestamps before anything downstream compares them
  • Adding retries and an explicit error path to external calls

Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.

Common questions

What exactly do I get?

The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.

How do I import it into n8n?

In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.

Do I need anything else for it to work?

You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Google Sheets, Telegram, Slack, Notion, …). No coding is required.

What if it doesn't work for me?

If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.

Can I modify or resell it?

You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.

Original n8n workflow template created and owned by WorkflowCrate. After purchase you receive the ready-to-import JSON file and a license to use and adapt it in your own projects.