A production-ready system that delivers location-based weather updates and severe event alerts directly to Telegram. It automates monitoring across multiple regions and accounts, reducing manual checks and ensuring teams or communities are notified in time to act. The result: reliable, real-time weather intelligence in your chats, powered by robust Android automation workflows.
Created by Appilot, built to showcase our approach to Automation!
If you are looking for custom Telegram Weather Alert Bot, you've just found your team — Let’s Chat.👆👆
What it does
Continuously fetches weather data, evaluates risk thresholds (rain, storms, heat, AQI, wind), and sends formatted alerts, summaries, and daily briefings to Telegram users, groups, or channels.
What it automates
Monitoring APIs, parsing alerts, deduplicating messages, scheduling dispatch, and handling multi-account delivery with human-like interaction patterns on Android devices or emulators.
Benefit
Instant signal with minimal noise: fewer misses, faster decisions, and scalable distribution across teams, regions, and brands.
- Policy-aware alerting: configurable thresholds, quiet hours, and escalation chains.
- Multi-region coverage with proxy & device pooling for throughput and reliability.
- Clean, actionable messages (maps, icons, severity labels, ETAs) tailored to recipients.
- Enterprise-ready telemetry: logs, metrics, retries, and audit trails.
- Works with both real Android devices and emulators, orchestrated from Appilot.
- Real Devices and Emulators: Run on physical Android phones or emulators (Bluestacks/Nox) with identical workflows for consistent behavior.
- No-ADB Wireless Automation: ADB-less control layer to reduce detection and simplify fleet setup over Wi-Fi/local networks.
- Mimicking Human Behavior: Randomized delays, typing simulation, scrolling, and back/forward navigation to appear natural.
- Multiple Accounts Support: Manage many Telegram bots/users with isolated sessions, tokens, and per-account policies.
- Multi-Device Integration: Parallel workers across device farms, each with its own queue and backoff strategies.
- Exponential Growth for Your Account: Scale outreach via channels and groups, schedule digest posts, and increase touch points responsibly.
- Premium Support: Priority debugging, integration help, and SLA-backed incident response.
- Granular Alert Rules: Per-city/geo fences, per-condition thresholds (rain mm/h, wind km/h, AQI bands).
- Rich Message Templates: Markdown/HTML, emoji severity tags, inline buttons, deep links, and media attachments.
- Analytics & Reporting: Daily/weekly summaries, delivery stats, failure breakdowns, and latency histograms.
Additional Features
| Feature | Description |
|---|---|
| Geo-Targeted Subscriptions | Users subscribe to cities/coords; bot maps chats to regions and filters alerts accordingly. |
| Quiet Hours & Escalation | Suppress routine pings at night; only critical alerts break through with elevated formatting. |
| Source Redundancy | Fallback to secondary weather providers when primaries rate-limit or fail. |
| De-duplication & Throttling | Collapse duplicate events; enforce per-chat rate limits to avoid spam. |
| Webhook & API Hooks | Expose webhooks for external systems and accept triggers from CRON/CI/CD/schedulers. |
| Role-Based Access | Admin-only commands for policy edits; viewer roles for read-only dashboards. |
- Input or Trigger — From the Appilot dashboard, select regions, thresholds, schedules, and recipient chats; optionally import a CSV of locations or drop pins on a map UI.
- Core Logic — Workers poll weather APIs, normalize data, and evaluate alert rules. Appilot orchestrates Android devices/emulators via UI Automator/ADB-less control to deliver Telegram messages and manage sessions.
- Output or Action — The bot posts alerts, daily briefings, and on-demand forecasts to Telegram users/groups/channels with buttons for snooze, expand, or subscribe/unsubscribe.
- Other functionalities — Automatic retries, exponential backoff, circuit breakers, structured logging, tracing, and parallel execution settings are managed in the Appilot dashboard.
- Language: Kotlin, Java, JavaScript, Python
- Frameworks: Appium, UI Automator, Espresso, Robot Framework, Cucumber
- Tools: Appilot, Android Debug Bridge (ADB), Appium Inspector, Bluestacks, Nox Player, Scrcpy, Firebase Test Lab, MonkeyRunner, Accessibility, Telegram Bot API
- Infrastructure: Dockerized device farms, Cloud-based emulators, Proxy networks, Parallel Device Execution, Task Queues, Real device farm
telegram-weather-alert-bot/
│
├── src/
│ ├── main.py
│ ├── bot/
│ │ ├── telegram_client.py
│ │ ├── commands.py
│ │ ├── message_templates.py
│ │ └── rate_limiter.py
│ ├── weather/
│ │ ├── providers/
│ │ │ ├── openweather.py
│ │ │ └── meteomatics.py
│ │ ├── normalizer.py
│ │ └── rules_engine.py
│ ├── automation/
│ │ ├── device_pool.py
│ │ ├── ui_automator_controller.py
│ │ ├── adb_less_controller.py
│ │ └── humanizer.py
│ ├── scheduler/
│ │ ├── cronjobs.py
│ │ └── queue_worker.py
│ └── utils/
│ ├── logger.py
│ ├── storage.py
│ ├── config_loader.py
│ └── geo.py
│
├── config/
│ ├── settings.yaml
│ ├── regions.csv
│ └── credentials.env
│
├── dashboards/
│ └── grafana.json
│
├── media/
│ └── telegram-weather-alert-bot-banner.png
│
├── logs/
│ └── runtime.log
│
├── output/
│ ├── alerts.json
│ └── reports/
│ └── weekly_report.csv
│
├── tests/
│ ├── test_rules_engine.py
│ └── test_templates.py
│
├── docker/
│ ├── Dockerfile
│ └── compose.yaml
│
├── requirements.txt
└── README.md
- Emergency coordinators use it to push severe weather alerts to field teams, so they can respond faster and safer.
- Logistics managers use it to reroute fleets around storms, so they reduce delays and damage.
- Community admins use it to inform residents about daily forecasts and warnings, so they improve preparedness.
- Retail operations use it to adjust staffing and inventory for weather-driven demand, so they optimize costs.
How do I configure this for multiple accounts?
Provide multiple Telegram tokens and map each to a device/emulator in config/settings.yaml. The device pool assigns chats to accounts and enforces per-account rate limits automatically.
Does it support proxy rotation or anti-detection?
Yes. Configure proxies per device and enable the humanizer module for randomized actions. The ADB-less controller reduces platform fingerprints further.
Can I schedule daily summaries and critical alerts separately?
Absolutely. Use the scheduler to create a morning briefing job while leaving critical alerts in real time with independent throttles and quiet hours.
What happens if a weather provider fails or rate-limits?
Source redundancy switches to fallback providers; circuit breakers pause failing sources, and retries use exponential backoff with jitter.
- Execution Speed: Processes and evaluates >1,500 locations/minute per worker on typical API SLAs; Telegram dispatch within 1–3 seconds/device under normal load.
- Success Rate: 95% end-to-end delivery across mixed device farms under steady network conditions.
- Scalability: Horizontally scales to 300–1000 Android devices/emulators with sharded queues and per-region workers.
- Resource Efficiency: Lightweight workers (~150–250MB RAM each) with pooled HTTP connections and gzip/HTTP2 where available.
- Error Handling: Structured logs, correlation IDs, dead-letter queues, automatic retries, and on-call alerts via webhook integrations.
