Monitor brand mentions and draft crisis responses with OpenAI and Telegram
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 24 nodes and runs on a schedule (every day) (plus 2 other triggers). Along the way it connects Google Sheets, OpenAI, Telegram and Slack.
How it runs
Trigger: On a schedule (every day) (plus 2 other triggers).
- Get New Mentions (Google Sheets): uses Google Sheets
- Parse Approval Message (Code): runs custom JavaScript code
- Slack: uses Slack
- Loop Mentions (Loop Over Items (Split in Batches)): loops over the items in batches
- Find Pending Crisis (Google Sheets): uses Google Sheets
- Classify Severity (OpenAI): uses OpenAI
- Merge Approval Data (Code): runs custom JavaScript code
- Parse Classification (Code): runs custom JavaScript code
- Approved? (If): checks a condition and branches into true / false
- Is Crisis? (If): checks a condition and branches into true / false
…plus 10 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 (11)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Sheets
n8n-nodes-base.googleSheets - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - No Operation, do nothing
n8n-nodes-base.noOp - OpenAI
@n8n/n8n-nodes-langchain.openAi - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - Telegram Trigger
n8n-nodes-base.telegramTrigger - Error Trigger
n8n-nodes-base.errorTrigger - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow monitors brand mentions stored in Google Sheets on a 15-minute schedule, uses OpenAI to classify crisis severity and draft PR responses, logs incidents to a crisis sheet, and routes approval decisions through Telegram, with Slack…