Telegram alerts for changes in the dispatchers’ working Google Sheet
The challenge
Dispatchers at a logistics company ran trips in a shared Google Sheet: someone added new data, someone changed statuses, and the manager found out only by opening the sheet. The full system was still being built, but changes had to be visible right away.
What was built
We wrote a Google Apps Script with an installable onEdit trigger. It watches the new-data and status columns and on every change sends a short Telegram message: sheet name (the week), row number, PRO # from the same row, the column name from the header and the new value. PRO numbers are issued sequentially through a counter in Script Properties so two dispatchers never take the same number. Bot tokens live in Script Properties, not in the code.
Edit trigger
installable onEdit; everyone in the Telegram group sees changes within a second.
Context in the message
sheet, row, PRO #, column name from the header and the new value.
Works on paste
the value is read from the range, so paste and bulk edits are caught too.
Sequential PRO #
a counter in Script Properties issues the next number without duplicates.
A single trigger
setup removes old triggers first, so messages are never duplicated.
No server
everything inside Google Workspace; tokens in Script Properties.
The result
The manager sees every status change in Telegram without opening the sheet, and PRO numbering stopped duplicating. The solution lived until the full TMS launched and became part of its requirements.
Tech stack
Have a similar challenge?
Discuss a projectNext case
Fleet ERP
ERP for an international carrier — trips, fuel, multi-currency →