Bank codes, server alerts, delivery updates and team OTP messages still arrive on one physical Android phone.
If that phone sits in an office drawer, a courier bag or another country, the whole team waits.
This guide compares five practical ways to forward Android SMS to Telegram, from free APKs to Tasker, n8n and a cloud SMS forwarder.
TL;DR: best options
| Method | Best for | Setup time | Main trade-off |
|---|---|---|---|
| Cloud SMS forwarder | Teams, multiple devices, business workflows | 2-5 min | SMS passes through a third-party service |
| Open-source APK | Personal use, strict privacy, one phone | 15-30 min | Manual setup and maintenance |
| Tasker / MacroDroid | Power users already using Android automation | 30-60 min | Fragile rules and battery optimization issues |
| n8n webhook | Teams with existing automation infrastructure | 1-2 hours | You maintain the workflow and endpoint |
| Custom app | Regulated environments or internal tooling | Days/weeks | Highest maintenance cost |
What SMS-to-Telegram forwarding requires
Every implementation has the same basic pipeline:
- An Android app receives incoming SMS using the SMS permissions.
- The app formats the message and decides whether it should be forwarded.
- A Telegram bot sends the message to a chat, group or channel.
The difference is where the routing logic lives. It can live on the phone, in Tasker, in an n8n workflow, in your own backend or in a SaaS dashboard.
1. Cloud SMS forwarder
A cloud SMS forwarder pairs your Android phone with a web dashboard. Incoming SMS are sent securely to the service, matched against routing rules, then delivered to Telegram, Email, Slack, Discord, X2Chat or a webhook.
Pros: quick QR pairing, multi-device management, routing by sender or keyword, delivery history, team access, webhooks and less manual Telegram bot configuration.
Cons: SMS passes through a cloud service. If your use case requires zero third-party processing, a self-hosted or open-source option is a better fit.
SMS Sender 24 is in this category. It works well when one team needs to share OTP codes, server alerts or business SMS from several Android phones without maintaining Android automation on every device.
2. Open-source Android apps
Projects such as Spirit532 SMS Forwarder and similar APKs can read SMS locally and send them directly to Telegram Bot API or a webhook.
This is the cleanest option if you want to inspect the code and avoid a cloud account.
Pros: free, auditable, no SaaS dependency, good for one phone and one or two destinations.
Cons: you maintain every phone manually. Rules, bot tokens, chat IDs and battery settings are configured per device. Some projects go years without updates, which matters on newer Android versions.
Example Telegram Bot API call:
POST https://api.telegram.org/bot<TOKEN>/sendMessage
Content-Type: application/json
{
"chat_id": "-1001234567890",
"text": "SMS from +15551234567: Your verification code is 482913"
}
3. Tasker or MacroDroid
Tasker and MacroDroid can listen for SMS events and call Telegram Bot API through an HTTP action. This is powerful if you already understand Android automation.
Pros: very flexible, cheap, local-first, can combine SMS with other Android triggers.
Cons: hard to support as a team workflow. A missed battery permission, Android update or broken profile can silently stop forwarding. Debugging is usually on the person holding the phone.
This method is great for personal automation. It is less great when three people depend on that phone to receive production alerts or bank OTP codes.
4. n8n webhook workflow
If your team already runs n8n, Make or another automation platform, the Android app can send SMS to a webhook. The workflow can then filter messages and forward them to Telegram.
Example payload:
curl -X POST https://n8n.example.com/webhook/sms \
-H "Content-Type: application/json" \
-d '{
"sender": "AWS",
"body": "Your alarm is in ALARM state",
"sim": "work",
"received_at": "2026-05-23T09:15:00Z"
}'
Pros: great for teams that already automate alerts and business workflows. You can branch to Telegram, Slack, email or CRM.
Cons: you still need a reliable Android collector app, a public HTTPS endpoint, secrets management, monitoring and retries.
5. Custom Android app
Building your own Android app is reasonable for regulated environments, internal device fleets or very specific routing requirements. It gives you full control over data handling and backend architecture.
Pros: maximum control, private backend, custom security model.
Cons: Android SMS permissions, background execution, foreground services, device reboot handling and battery optimization are easy to underestimate.
The first version is the simple part. Keeping it reliable is the real work.
Android 14/15 pitfalls
SMS forwarding is not just an HTTP problem. Modern Android aggressively limits background work, especially for apps installed outside Google Play.
Watch for these issues:
- Battery optimization: the app may stop receiving or forwarding after several hours unless excluded from battery restrictions.
- Foreground service rules: long-running background services need a visible notification and correct service type.
- Boot handling: forwarding should resume after the phone restarts.
- Connectivity gaps: the phone needs Wi-Fi or mobile data. Good apps queue messages and retry.
- Dual SIM: personal and work SIMs often need different routing rules.
Which method should you choose?
| Scenario | Recommended method | Why |
|---|---|---|
| One personal phone, one Telegram chat | Open-source APK | Free and simple enough |
| Team OTP codes | Cloud SMS forwarder | Rules, history and team destinations matter |
| Server SMS alerts | Cloud forwarder or n8n | Reliability and routing are more important than novelty |
| Strict privacy / no third party | Open-source or custom app | Keep data under your control |
| Existing automation stack | n8n webhook | Easy to plug into current workflows |
Honest note
SMS Sender 24 is an independent cloud tool built to solve a real SMS forwarding problem.
It is convenient for teams, but it is not the right choice if your policy requires zero third-party processing. In that case, use an open-source app or self-host the whole pipeline.
FAQ
Can I forward only specific SMS?
Yes. Use sender names, phone numbers, keywords or SIM slots as routing conditions.
For example, bank OTP messages can go to one Telegram chat while courier updates go to another.
Does the Android phone need internet?
Yes. The phone needs Wi-Fi or mobile data to forward messages.
If connectivity drops, a reliable app should queue messages and retry when the connection returns.
Is this different from SMS gateways like Twilio?
Yes. Twilio and similar services provide virtual numbers or outbound messaging APIs.
SMS forwarding starts from a real Android phone and forwards incoming messages from its SIM card.
Can it work with two SIM cards?
Yes, if the collector app records the SIM slot and the service supports SIM-based rules.
This is useful when one phone has both personal and work SIM cards.
Is Telegram the only destination?
No. Telegram is the most common destination, but many teams also forward to Email, Slack, Discord, X2Chat or a webhook.
Originally published at https://smssender24.com/en/blog/forward-android-sms-to-telegram.html
Top comments (0)