Route Telegram customer complaints with OpenAI and Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 31 nodes and runs on Telegram events (message) (plus 2 other triggers). Along the way it connects Telegram, Google Sheets, OpenAI and Slack.
How it runs
Trigger: On Telegram events (message) (plus 2 other triggers).
- Normalize Complaint Input (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Slack: uses Slack
- Lookup Order Details (Google Sheets): uses Google Sheets
- Extract Order ID From Callback (Code): runs custom JavaScript code
- Notify Support Lead - Rejected Logged (Telegram): uses Telegram
- Get Customer Complaint History (Google Sheets): uses Google Sheets
- Update Row - Mark Approved (Google Sheets): update
- Determine Issue Type and Repeat Offender (Code): runs custom JavaScript code
- Notify Customer - Escalated Resolution Approved (Telegram): uses Telegram
…plus 18 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - Telegram
n8n-nodes-base.telegram - Switch
n8n-nodes-base.switch - Wait
n8n-nodes-base.wait - OpenAI
@n8n/n8n-nodes-langchain.openAi - Error Trigger
n8n-nodes-base.errorTrigger - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow handles customer order complaints submitted via Telegram by looking up order details in Google Sheets, using OpenAI to classify message sentiment, and routing each case to auto-approval, support lead review, warehouse…