How it works

One device, one rule, one HTTPS destination.

The forwarding path is intentionally short. Matching and queue management happen locally; delivery goes to the endpoint you configured.

Step 1
Choose the source applications
Create a rule and select one or more installed apps. Only the package names selected for the rule are stored.
Scope is explicit per rule.
Step 2
Match useful notification text
Noti2Hook evaluates notification content against the filters in that rule while the event is still on the device.
Non-matching events are not forwarded.
Step 3
Build the HTTPS request
The app prepares the JSON payload, adds configured authentication headers, and can attach an HMAC-SHA256 signature.
Cleartext HTTP is rejected.
Step 4
Deliver or queue for retry
The request is sent directly to your endpoint. Temporary failures can be stored in the encrypted local queue and retried.
No Noti2Hook relay receives the event.

Example request

A predictable payload for your automation.

Map these fields in your own endpoint, workflow tool, or serverless function. Exact content depends on the source notification and rule.

POST /hooks/androidapplication/json

{
  "package": "com.example.orders",
  "title": "Order paid",
  "text": "THB 1,250.00",
  "postedAt": "2026-08-24T10:42:18Z"
}