Route SMS conflict case commands via webhook using Google Sheets and Telegram

by Alassane ✓ · 0 views · created 2026-08-21 · Project Management

What this workflow does

This workflow has 64 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Google Sheets and Telegram.

How it runs

Trigger: When an HTTP POST request hits its webhook URL.

1. Normalize mediator request (Edit Fields (Set)): sets 5 fields: phone, smsText, providerMessageId…
2. Check required request fields (If): checks a condition and branches into true / false
3. Find approved mediator (Google Sheets): uses Google Sheets
4. Reply: invalid request (Respond to Webhook): sends the response back to the webhook caller
5. Mediator is active (If): checks a condition and branches into true / false
6. Reply: register unavailable (Respond to Webhook): sends the response back to the webhook caller
7. Find completed provider message (Google Sheets): uses Google Sheets
8. Reply: sender not approved (Respond to Webhook): sends the response back to the webhook caller
9. Provider message already processed (If): checks a condition and branches into true / false
10. Reply: message log unavailable (Respond to Webhook): sends the response back to the webhook caller

…plus 53 more steps. See the full node list below.

Services it uses

Google SheetsTelegram

Before you upgrade to n8n 3.0

Nodes used (7)

• Webhookn8n-nodes-base.webhook
• Edit Fields (Set)n8n-nodes-base.set
• Ifn8n-nodes-base.if
• Google Sheetsn8n-nodes-base.googleSheets
• Respond to Webhookn8n-nodes-base.respondToWebhook
• Switchn8n-nodes-base.switch
• Telegramn8n-nodes-base.telegram

From the author

Quick overview This workflow helps approved community mediators record and retrieve conflict-case information through SMS-style commands. It stores cases and updates in Google Sheets, sends private Telegram alerts to a record keeper, and keeps conflict…

View the original on n8n.io → Check your own copy