/tool fetch url=$url http-method=post http-data=$postData keep-result=no /system logging add action=script script="notify-user-removed" topics=ppp,info add action=script script="notify-user-removed" topics=hotspot,info Alternatively, use a scheduler to check for removed users every minute:
/tool fetch url=$url http-method=post http-data=$data keep-result=no
/system script run set-telegram-vars /system script add name="notify-user-removed" source= :global tgToken :global tgChatId :local logMsg "$[/system clock get date] $[/system clock get time] - User removed: $[/log get $1 message]" :local message "🚫 User removed from Mikrotik\n$logMsg" This script can be manually tested or called
To trigger manually:
# Copy-paste sequence (adjust token & chatId) /system script add name=telegram-removed source=":local token \"YOUR_TOKEN\"; :local chatId \"YOUR_CHATID\"; :local name \"\$1\"; :local text \"User \$name removed\"; /tool fetch url=\"https://api.telegram.org/bot\$token/sendMessage?chat_id=\$chatId&text=\$[:escape \$text]\" keep-result=no" /log add topics=ppp,info action=script script=telegram-removed This completes the technical documentation for the . [/system clock get time] :local text "⚠️ <b>User
Note: The scheduler approach assumes removal = deletion. Adjust logic as needed. This script can be manually tested or called from a log trigger.
Run once:
:local url "https://api.telegram.org/bot$token/sendMessage" :local data "chat_id=$chatId&text=$[:escape $text]&parse_mode=HTML"
:local now [/system clock get date] . " " . [/system clock get time] :local text "⚠️ <b>User Removed</b>\n👤 Name: $userName\n⏰ Time: $now\n🏷️ Router: [/system identity get name]" :local chatId \"YOUR_CHATID\"