Choose a destination
Choose an HTTPS webhook with optional Basic Auth or headers, a dedicated Google Sheet, or an international SMS number. Carrier charges may apply to SMS forwarding.
YOUR MESSAGES. YOUR RULES.
Give your SMS a useful next stop.
Keep your usual Android messaging app. Relay matching SMS or opted-in app notifications to HTTPS endpoints, Google Sheets or another SMS number.
Development build. Device testing and Google Play review are still pending.
ILLUSTRATION · SYNTHETIC DATA
Incoming message · SMS or opted-in notificationSender: ExampleService
Your appointment is confirmed.
Your ruleIf text contains “appointment”
Your HTTPS endpoint
Your Google Sheet
SMS forwardingAnother SMS number
ANDROID DEVELOPMENT BUILD
Three decisions, made on your phone.
Write a rule
Match senders with exact text, wildcards or regex. Test pasted multiline messages locally, save reusable test cases, and clone existing rules. Local tests send nothing.
Enable it deliberately
Rules and clones start disabled. Grant only the permissions you need. Notification relay needs a separate opt-in and Android access. Pause at any time.
A small app, with a narrow job.
No app delivery logs, analytics, crash reporting or remote administration. Credentials, pending messages and explicitly saved test cases are encrypted locally. Matching messages go to your configured destinations.
Know the boundaries before you rely on it.
No private inbox or message history access. Notification text may be hidden, incomplete or repeated; RCS and MMS are not read directly. Sheets retries can duplicate rows. SMS submission is attempted once, capped at ten parts, and does not confirm carrier delivery.