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

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 decisions with human mediators.

How it works A webhook receives a phone number and an SMS-style command.

The workflow rejects missing fields and checks the sender against the active mediators listed in Google Sheets. NEW creates a case, prepares a record-keeper checklist, and sends the record keeper a private Telegram alert. UPDATE checks that the case exists, appends the update to its history, and alerts the record keeper. SUMMARY and STATUS read the protected case register and return only a short, masked reply. For an urgent NEW report, the workflow reads the locally configured contacts and tells the mediator to contact the local authority and peace-committee leader. It does not contact authorities automatically. Approved inbound messages and prepared outbound replies are logged in Google Sheets. The demo returns the reply through the webhook; a live adaptation can connect an SMS provider.

Setup Import the workflow into n8n. Create one protected Google Sheet with these tabs: Mediators, Cases, Case Updates, Messages, Local Contacts, and Case Review Checklists. Copy the exact column headers from the included setup notes or project documentation. Add your Google Sheets credential and select the same spreadsheet in every Google Sheets node. Add your Telegram credential, replace YOUR_RECORD_KEEPER_TELEGRAM_ID, and test with a private record-keeper chat. Open Webhook: mediator request, click Test workflow, copy its Test URL, and send fictional test data only. Connect an SMS provider only after adapting the access, safeguarding, urgent-contact, language, and message-delivery rules for your organisation.

Customization Replace the fictional mediator records and example cases with organisation-approved test data before any controlled pilot. Adapt conflict categories, command wording, languages, status values, urgent criteria, and locally agreed contacts. Keep SMS summaries short and masked. Do not include names, detailed allegations, or confidential case notes. Replace the webhook response with the chosen SMS provider's send-message action and verify delivery reports before claiming that a message reached a phone.

Additional info This template supports human mediators but does not replace their judgment. It does not decide who is guilty or responsible, how serious a risk is, or how a conflict should be resolved. Use only fictional information during setup and testing. Before using real conflict data, the organisation should review access, safeguarding, security, data retention, consent, urgent-case procedures, and wording in local languages.