The ultimate CLI solution for Telegram event monitoring and interaction workflow handling.
Avoid building from source? Grab the compiled, dependency-free binaries directly below:
Download Here
(Windows x64 / Linux Standalone binaries)
TelegramAutomation Engine is a heavily optimized, asynchronous C++ toolkit specifically designed to process Telegram-side events, monitor message flows, and orchestrate interaction workflows from a standalone desktop command-line environment.
Whether you are organizing channel operations, routing message events into internal tools, or archiving chat-side activity for automation workflows, TelegramAutomation Engine bridges the gap between Telegram data streams and your local systems natively and efficiently.
- ⚡ Hyper-Fast Event Processing: Built for concurrent message polling, update parsing, and event-driven automation handling.
- 🔓 Standalone Architecture: Operates without requiring the full desktop client to remain open during supported workflows.
- 📦 Deep Interaction Coverage: Handles message events, reaction data, notification payloads, and workflow-side triggers directly.
- 🔗 Automation-Friendly Routing: Connects incoming events to scripts, logging systems, and downstream processing chains.
- 🎨 Cross-Workflow Support: Output integrates with dashboards, notification relays, and custom desktop automation wrappers.
- Core: Modern C++20
- Messaging: TDLib-oriented integration layer
- Parsing: JSON-based event payload handling
- FileSystem: Native
<filesystem>API - Threading: Modern
std::jthreadmapping
Contributions to TelegramAutomation Engine are deeply appreciated! Check our active issues labeled good first issue or simply fork, modify, and submit a PR. Please ensure all code conforms to the clang-format guidelines inside .clang-format.
Distributed under the MIT License. You are free to modify, distribute, and integrate this into your workflow.
Telegram desktop automation utility is an open-source tool for monitoring message events, routing interaction updates, and managing chat-side workflows without depending on a persistent full client UI. Useful for notification relays, logging pipelines, automation experiments, and local archival of Telegram event data.