Phone alerts: setup guide
Phone alerts send you a message when a page monitor finds something, so you do not have to sit at your computer. Reloadwright does not have its own phone app. Instead it uses a push service you choose, and sends the alert straight from your browser to that service.
Which service should I pick?
- iPhone: Bark is the simplest.
- Android, or you want to try it without installing anything: ntfy.
- You want the alert in WeChat: ServerChan.
- Your team uses WeCom (企业微信): a WeCom group robot.
- You already use Telegram: a Telegram bot.
- You run your own server or automation: Custom address.
What gets sent
- The page title and the page address.
- What was found: the text that appeared or disappeared, or the old and new text of the area you picked (about 60 characters each).
- Nothing else. The alert goes from your browser to the service you chose and does not pass through our servers.
Set up your service
Bark
For iPhone and iPad. Alerts arrive as normal notifications.
- Install “Bark” from the App Store, open it, and allow notifications.
- The app shows example addresses such as https://api.day.app/AbCdEf123456/… The part between “api.day.app/” and the next “/” is your device key.
- Copy that device key.
Paste into Reloadwright: The device key. If you run your own Bark server, paste the whole address including the key instead.
- Anyone who has your device key can send you notifications, so keep it private.
ntfy
For Android, iPhone or any web browser. No account needed.
- Make up a topic name that nobody could guess, for example alex-reload-8372. Use letters, digits, “-” and “_” only.
- On your phone, install the “ntfy” app and subscribe to that topic. Or, to try it first, open https://ntfy.sh/your-topic-name in a browser and leave the page open.
- Use the same topic name in Reloadwright.
Paste into Reloadwright: The topic name. If you use your own ntfy server, paste the full address, such as https://ntfy.example.com/your-topic-name.
- Topics on ntfy.sh are public: anyone who knows the name can read the alerts. Choose a long, random name.
Telegram bot
Alerts arrive as a chat message from your own bot.
- In Telegram, open a chat with @BotFather, send /newbot and follow the questions. At the end it gives you a bot token that looks like 123456789:AAExampleToken.
- Open your new bot and press Start, or send it any message. A bot cannot write to you before you write to it.
- In a browser, open https://api.telegram.org/bot<your token>/getUpdates and find "chat":{"id":123456789. That number is your chat ID.
Paste into Reloadwright: The bot token in the first box and the chat ID in the second box.
- If getUpdates shows an empty result, send your bot another message and reload that page.
WeCom group robot
Alerts arrive as a message in a WeCom (企业微信) group.
- In WeCom, open a group chat. A small group you create for yourself works too.
- Open the group settings and add a “消息推送” (called “群机器人” in older versions). Give it a name.
- Copy the Webhook address it shows. It starts with https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=
Paste into Reloadwright: The whole Webhook address. The part after “key=” on its own also works.
- Treat the Webhook address like a password: anyone who has it can post in that group.
- WeCom accepts at most 20 messages per minute per robot.
ServerChan
Alerts arrive in WeChat through ServerChan's official account.
- Open https://sct.ftqq.com in a browser and sign in by scanning the QR code with WeChat.
- Follow its official account when asked. This is how the alerts reach your WeChat.
- Open the “SendKey” page and copy your SendKey. It starts with SCT.
Paste into Reloadwright: The SendKey.
- The free plan allows only a few messages per day.
- ServerChan 3 keys, which start with sctp, also work. Those alerts arrive in the ServerChan 3 app instead of WeChat.
Custom address
For your own server, or an automation tool that gives you a webhook address.
- Prepare an https address that accepts POST requests.
- Reloadwright sends JSON with three text fields: title, body and url.
- Your address should answer with any 2xx status. Anything else is shown as a failure.
Paste into Reloadwright: The full https address.
- Plain http is accepted only for this computer (127.0.0.1 or localhost), for testing.
Finish in Reloadwright
- Open the Reloadwright popup and expand “Phone alerts”.
- Choose your service and paste the key or address.
- Click “Save and send a test”. Edge asks whether Reloadwright may contact that service: choose Allow.
- You should see “Test sent. Check your phone.” and receive a message titled “Reloadwright test”.
- From now on every page monitor hit is also sent to your phone. Click “Turn off” to stop.
If the test does not arrive
- The popup says HTTP 400, 401, 403 or 404
- The key or address is wrong or incomplete. Copy it again from the service and make sure nothing is cut off.
- The popup says “errcode” followed by a number (WeCom)
- WeCom rejected the webhook. Copy the whole Webhook address again; if the robot was deleted, create a new one.
- The popup says “no answer”
- Your browser could not reach the service. Check your network; some services are not reachable from every country.
- The popup says the test was sent, but nothing arrives
- Check that notifications are allowed for the app on your phone, and that you subscribed to exactly the same topic or followed the right account.
- Edge did not ask for permission, or you clicked Block
- Click “Save and send a test” again and choose Allow.
- ServerChan stops delivering after a few messages
- The free plan has a small daily limit. It resets the next day.