Read new SMS from your Android phone on your computer through your own n8n workflow. Message487 transfers incoming SMS text, sender and time to the HTTPS webhook you choose. This is one-way transfer of new messages: it does not import SMS history, send SMS or provide a two-way messaging inbox.

HOW TO READ SMS ON YOUR COMPUTER

Set up and publish an n8n webhook workflow with Bearer-token authentication.
In Message487 Connection, save its HTTPS URL and token. In Sources, turn on Incoming SMS and grant the receive-SMS permission.
Receive a new SMS on the phone. On your computer, open the workflow's Executions in n8n and view the received message text and sender. Compare the event ID with Message487 Journal.
The Journal shows delivery status, not message contents. Notification access is not needed for SMS transfer. Without RECEIVE_SMS, Message487 cannot capture and transfer new incoming SMS; its separate notification feature can still be used.

You supply the n8n service or another compatible HTTPS receiver and token. Message487 does not include a hosted inbox or an n8n subscription. Another receiver does not require an n8n account.

OTHER FEATURES

• Choose which applications can forward notifications, or select all visible launcher apps.
• Authenticate requests with a Bearer token and optionally require an event acknowledgement.
• Keep events in an encrypted local outbox and retry temporary delivery failures.
• Pause forwarding, review delivery status, retry or delete queued events.
• Identify your phone using a custom device code.
• Use light or dark themes and English or Russian interfaces.
• View rotating local diagnostics and optionally share a report by email.

Notification and SMS capture are off by default. Android notification access and SMS permission are requested for the corresponding features. Android may hide sensitive notification content. The app lists visible launcher apps rather than requesting access to the entire installed-app inventory.

You need your own HTTPS endpoint and token. The app has no advertising, analytics or automatic crash uploads. Your endpoint and downstream services receive forwarded message contents and apply their own retention policies. Retried requests can produce duplicates; configure deduplication on your server if needed.