SMS2Webhook

org.golder.sms2webhook
by e3c6d9d5…

Forwards incoming SMS to a webhook endpoint you control, with retries, deduplication and optional API key authentication.

SMS2Webhook runs on your own phone and posts each incoming SMS to a webhook URL that you configure. It is a building block for self-hosted automation: point it at your own server to trigger workflows, archive messages, feed a CRM or ticketing system, or expose SMS to your own dashboards. ## What it sends Every forwarded message is posted as JSON to the single endpoint you set. The payload is your phone's own messaging row rather than a fixed shape, so the fields present vary by device and Android version: the sender `address`, the message `body` and the `date` timestamp are always there, and devices whose messaging app records a SIM subscription include it as `sub_id`. Treat anything beyond those as optional. If you configure an API key it is sent as an `Authorization: Bearer` header. ## What leaves the device Message content is transmitted **only** to the webhook URL you enter. There are no analytics, no advertising, no crash reporting and no third-party servers. The local database stores a SHA-256 hash of each message for deduplication, not the message text. Source code is public and auditable. Because this is a self-hosted tool, the destination is yours to choose. Review the URL you enter, and prefer HTTPS so message bodies are encrypted in transit. ## Permissions - `RECEIVE_SMS` and `READ_SMS` — required to observe incoming messages and, if you choose, to backfill your existing SMS history. - `INTERNET` — to reach your webhook. - `CAMERA` — optional, only for scanning the setup QR code. The telephony and camera hardware features are declared optional, so the app installs on devices without them. ## Reliability Uploads are queued in WorkManager with exponential backoff, so a webhook that is briefly unreachable does not lose messages. A SHA-256 cache prevents the same message being delivered twice. ## Requirements Android 9.0 (API 28) or later.

First release: Oct 4, 2026, 5 total releases.

Most recent release: Oct 6, 2026.

Website Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Oct 6, 2026 2.2.1
    Patch release after 2.2.0. No behaviour change to SMS handling or webhook format. ### 🐛 Fixes - **Activity log had insufficient height in landscape (and some portrait) views.** The RecyclerView did not expand to fill the viewport on short heights, cutting off entries. Now uses `0dp` height with `app:layout_constraintBottom_toBottomOf="parent"` so the log fills available space and scrolls. - **ZapStore protocol details were leaking into this repo's release checklist.** The thin checklist now only asserts what is owned here: the publish step must succeed (re-run if needed), and `CHANGELOG.md` must be current because `zapstore.yaml` points `release_notes` at it. Everything else belongs in `rossigee/zapstore-publish`. ### 📚 Documentation - The prerequisite action fixes (30 s publish timeout + one retry, `release_notes` fallback documented) are in zapstore-publish v1.0.3 with `@v1` updated to point at it. ---
  • Oct 6, 2026 2.2.0
    Minor: the main screen is redesigned, and the app now uploads only what you received. No longer sending your sent messages is a deliberate behaviour change. Also the release that repairs the ZapStore listing, whose **Install button was greyed out**. The relay had rejected the asset event carrying the APK because it requires a `version_code` tag that the publish action was not emitting, while the release event survived and pointed at an asset the relay did not have. The run still reported success, because the action awaited an array of promises rather than the promises themselves, so the rejection surfaced as noise rather than an error. Both are fixed in zapstore-publish v1.0.2, which `release.yml` picks up through `@v1`.
    More…
    ### 🎨 Main screen - **One status line instead of three counters.** The screen showed Inbox / Uploaded / Failed plus a progress bar, which answered "what has happened in my history" rather than "is there anything outstanding". On a phone holding 624 messages with an empty cache it read Uploaded 0, Failed 0 — indistinguishable from a fully synced device. - The status line now reports one of four states: all uploaded, N not uploaded yet, N refused, or syncing. The colour reflects urgency, so an ordinary unsynced phone is not alarmed at. - Sync progress moved onto the status line (`Syncing… 42%`) rather than a separate bar. - **Clear cache moved to the overflow menu.** It is destructive and rarely needed. ### 🐛 Fixes - **The sync queued from the menu cleared the cache without asking.** The confirmation dialog only existed on the button that has just been removed; the menu item has been present all along and went straight to the destructive action. - **The Clear cache dialog said the opposite of the truth** — "Sync SMS first to ensure all messages are uploaded". Clearing the cache *causes* a full re-upload. It now explains that, and that whether duplicates appear depends on the server recognising them. - **Repeated diagnostics filled the activity log with one line.** Four copies of "624 messages have no cache entry" were visible at rest on a real device, because diagnostics run on every activity launch, every Clear cache and every sync exit. A finding is now reported once and stays quiet while it remains true; a count that changes reports the new number. ### 🔒 Behaviour - **The sync is inbox-only.** The query was the whole `sms` table, so sent messages were uploaded as well. That is not what the app promises to do, it inflated every count derived from it, and it made inbox-minus-uploaded drift positive by roughly the size of your sent history. **Existing installs will show fewer messages immediately.** ### 📚 Documentation - **The ZapStore listing now carries the app icon.** `zapstore.yaml` gained an `icon:` field; without it the store showed a placeholder letter. This is the first release where it reaches a published event. - The webhook contract is documented for the first time: which status codes mean delivered, retried, or permanently discarded, and the setup QR payload format. ### 🧪 Tests - 146 unit tests, up from 129. Added `SyncStatusTest`, `CacheDiagnosticsTest`, and coverage for reporting an unreadable inbox rather than claiming zero outstanding. `StatisticsTest` was removed with the counters it tested. ---
  • Oct 6, 2026 2.1.2
    Documentation only. **No application code changed since 2.1.1**, so the APK is functionally identical; only `versionCode` and `versionName` differ. Published so that the ZapStore listing carries corrected text. The listing is a signed Nostr event with the description and screenshots baked in, and `zapstore.yaml` and this file are inputs to publishing rather than the source of truth — so the 2.1.1 listing kept its original wording until a new publish replaced the event. ### 📚 Documentation
    More…
    - **Corrected the ZapStore listing, which promised a SIM slot that may not be sent.** It said every payload includes "the SIM slot it arrived on". `SmsStoreWorker.encodeMessage` copies every column the cursor returns from `content://sms`, so `sub_id` is present only where the device's messaging provider exposes it. The listing now states the actual contract: the payload is the provider's own row, its shape varies by device, and only `address`, `body` and `date` are dependable. - **Added the missing 2.1.1 entry**, which this release had shipped without. - Added a release checklist to `AGENTS.md`, covering the version bump, the changelog entry, the on-device smoke test, PR review, tagging, and how to confirm the Zapstore publish actually happened. - `AGENTS.md` referenced a `debug_install.sh` script that does not exist in this repository; the guidance now points at `adb logcat`. - The `## Version 2.0.0 Updates (Current)` heading no longer claims to be current. ---
  • Oct 6, 2026 2.1.1
    # Changelog ## [2.0.1] - 2025-07-04 ### 🐛 Fixes - Fixed edge-to-edge display issues on Pixel 8 Pro and other modern devices - Corrected window inset handling for the system status bar - Removed a deprecated import in `SmsBroadcastReceiver` ### 📚 Documentation
    More…
    - Expanded the README with full webhook payload documentation - Added screenshots showing the main and settings screens ## [2.0.0] - 2024-01-03 ### 🎨 UI/UX Improvements - Complete Material Design 3 overhaul with modern components - New card-based layout with better visual hierarchy - Added dark mode support - Improved statistics display with color-coded metrics - RecyclerView-based activity log with timestamps and status icons - Pull-to-refresh functionality - Responsive design that adapts to all screen sizes ### 🏗️ Architecture - Implemented MVVM architecture with ViewModels and LiveData - Proper separation of concerns - Background operations moved off main thread - Added proper lifecycle management ### ✨ New Features - Test Connection button in settings to verify webhook configuration - Diagnostic system to detect cache inconsistencies - Real-time input validation for webhook URL - Swipe refresh for activity logs - Material Design buttons and progress indicators - Improved error messages and user feedback ### 🐛 Bug Fixes - **Fixed cache inconsistency issue** where duplicate entries caused incorrect counts - Database now uses message hash as primary key to prevent duplicates - Added database migration to clean up existing duplicates - Fixed potential memory leaks with proper lifecycle handling - Resolved threading issues with database operations ### 🔧 Technical Improvements - Upgraded to Room database version 2 with migration - Added AndroidX lifecycle components - Implemented proper dependency injection patterns - Updated all dependencies to latest stable versions - Added comprehensive GitHub Actions CI/CD ### 📝 Database Changes - **Migration Required**: Database schema updated from v1 to v2 - Primary key changed from auto-increment ID to message hash - Automatic cleanup of duplicate entries during migration - INSERT OR REPLACE strategy to prevent future duplicates ### 🚀 Performance - Optimized log display with RecyclerView - Limited log entries to prevent memory issues - Improved database query efficiency - Better resource management ### 📦 Dependencies Updated - Material Design Components - AndroidX Lifecycle - Room Database - RecyclerView - SwipeRefreshLayout --- ## [1.3.1] - Previous Release - Basic SMS to webhook functionality - Simple UI with basic statistics - Cache system for tracking sent messages
  • Oct 4, 2026 2.1.0
    # Changelog ## [2.0.1] - 2025-07-04 ### 🐛 Fixes - Fixed edge-to-edge display issues on Pixel 8 Pro and other modern devices - Corrected window inset handling for the system status bar - Removed a deprecated import in `SmsBroadcastReceiver` ### 📚 Documentation
    More…
    - Expanded the README with full webhook payload documentation - Added screenshots showing the main and settings screens ## [2.0.0] - 2024-01-03 ### 🎨 UI/UX Improvements - Complete Material Design 3 overhaul with modern components - New card-based layout with better visual hierarchy - Added dark mode support - Improved statistics display with color-coded metrics - RecyclerView-based activity log with timestamps and status icons - Pull-to-refresh functionality - Responsive design that adapts to all screen sizes ### 🏗️ Architecture - Implemented MVVM architecture with ViewModels and LiveData - Proper separation of concerns - Background operations moved off main thread - Added proper lifecycle management ### ✨ New Features - Test Connection button in settings to verify webhook configuration - Diagnostic system to detect cache inconsistencies - Real-time input validation for webhook URL - Swipe refresh for activity logs - Material Design buttons and progress indicators - Improved error messages and user feedback ### 🐛 Bug Fixes - **Fixed cache inconsistency issue** where duplicate entries caused incorrect counts - Database now uses message hash as primary key to prevent duplicates - Added database migration to clean up existing duplicates - Fixed potential memory leaks with proper lifecycle handling - Resolved threading issues with database operations ### 🔧 Technical Improvements - Upgraded to Room database version 2 with migration - Added AndroidX lifecycle components - Implemented proper dependency injection patterns - Updated all dependencies to latest stable versions - Added comprehensive GitHub Actions CI/CD ### 📝 Database Changes - **Migration Required**: Database schema updated from v1 to v2 - Primary key changed from auto-increment ID to message hash - Automatic cleanup of duplicate entries during migration - INSERT OR REPLACE strategy to prevent future duplicates ### 🚀 Performance - Optimized log display with RecyclerView - Limited log entries to prevent memory issues - Improved database query efficiency - Better resource management ### 📦 Dependencies Updated - Material Design Components - AndroidX Lifecycle - Room Database - RecyclerView - SwipeRefreshLayout --- ## [1.3.1] - Previous Release - Basic SMS to webhook functionality - Simple UI with basic statistics - Cache system for tracking sent messages