Integrations
When a watch matches, RefreshPilot posts the event to a web address you choose. Five presets format the message for you; the Custom JSON preset reaches everything else.
Every integration on this page is the same mechanism: the Monitor tab's Webhook option, pointed at a different URL. RefreshPilot builds the request in your browser and posts it directly to that address — nothing is relayed through a RefreshPilot server, so the destination sees your browser and nobody else does.
Webhooks are a PRO feature. The destination must be a public https address — localhost and private ranges like 192.168.x.x are rejected by design.
Whatever the destination, the same six facts describe the match. The presets fold them into each service's own message format; Custom JSON hands them over untouched.
Message text is capped at roughly 1900 characters, so a very long snippet is trimmed rather than rejected.
Create an incoming webhook for a channel in your Slack workspace and paste its URL. The alert arrives as an ordinary channel message.
The URL you paste
https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
What the destination receives
{
"text": "RefreshPilot — Keyword found: \"in stock\"\nshop.example.com/sneakers"
}Create an incoming webhook on a Discord channel and paste its URL. The alert posts as a normal message from the webhook's name.
The URL you paste
https://discord.com/api/webhooks/000000000000000000/XXXXXXXXXXXXXXXXXXXXXXXX
What the destination receives
{
"content": "RefreshPilot — Keyword found: \"in stock\"\nshop.example.com/sneakers"
}Telegram goes through a bot, so the token and your chat id are both part of the URL. Paste the whole thing exactly in this shape — the bot token on its own will not deliver.
The URL you paste
https://api.telegram.org/bot<token>/sendMessage?chat_id=<id>
What the destination receives
{
"text": "RefreshPilot — Keyword found: \"in stock\"\nshop.example.com/sneakers"
}Subscribe to a topic in the ntfy app and paste that topic's URL. The alert arrives as a plain-text push with the page title carried in the Title header.
The URL you paste
https://ntfy.sh/your-topic-name
What the destination receives
Title: Sneakers — Example Shop
Keyword found: "in stock"
shop.example.com/sneakersZapier has no dedicated preset and does not need one. Add a Webhooks by Zapier trigger, choose Catch Hook, and paste the URL it gives you into the Custom JSON preset — every field below arrives as a named value you can map into any of Zapier's apps.
The URL you paste
https://hooks.zapier.com/hooks/catch/000000/xxxxxx/
What the destination receives
{
"source": "refresh-pilot",
"title": "Sneakers — Example Shop",
"url": "https://shop.example.com/sneakers",
"keyword": "in stock",
"snippet": "In stock — ships tomorrow",
"mode": "found",
"time": "2026-08-13T09:24:11.000Z"
}Trustpilot is a page to watch rather than a place to post. Point a watch at your company's review page, monitor just the review list with the area selector so the rest of the page cannot trigger it, and route the alert to any destination above. A new review then reaches your team without anyone refreshing a tab.
The URL you paste
Any of the destinations above
What the destination receives
{
"source": "refresh-pilot",
"title": "Example Ltd Reviews | Trustpilot",
"url": "https://www.trustpilot.com/review/example.com",
"keyword": "any change",
"snippet": "Rated 4.6 · 1,284 reviews",
"mode": "change",
"time": "2026-08-13T09:24:11.000Z"
}Any https address you control. RefreshPilot sends a POST with a JSON body and no authentication header, so put the secret in the URL itself if the endpoint needs one. This is also the route to n8n, Make, Home Assistant and anything else that accepts a JSON POST.
The URL you paste
https://api.example.com/hooks/refresh-pilot?token=…
What the destination receives
POST /hooks/refresh-pilot HTTP/1.1
Content-Type: application/json
{
"source": "refresh-pilot",
"title": "Sneakers — Example Shop",
"url": "https://shop.example.com/sneakers",
"keyword": "in stock",
"snippet": "In stock — ships tomorrow",
"mode": "found",
"time": "2026-08-13T09:24:11.000Z"
}A webhook is one of several things a match can do. If nobody needs to be told in a chat channel, these may fit better:
FAQ
작동 방식, 무료 범위, PRO로 열리는 기능까지 솔직하게 답해 드립니다. 빠진 내용이 있나요? 영업일 기준 하루 안에 답변해 드려요.
No. The request is built and sent by the extension in your browser, straight to the address you configured. Our servers never see the page, the match or the destination.
Two causes cover almost every case. The destination must be a public https address, so localhost, 127.0.0.1, 192.168.x.x and 10.x.x.x are refused by design. And Telegram needs the complete URL including the bot token and chat id — the token alone is not enough.
One webhook URL is configured per watch. To reach several places at once, point the Custom JSON preset at an automation tool such as Zapier or n8n and let it fan the event out.
The five presets each use their service's expected shape and are not editable. Custom JSON sends the full event, so any formatting you need is done at the receiving end.
At most once every 20 seconds per watch, which is the same throttle every alert type uses. Turning on Stop on match — the default — means it fires once and the job stops.
No, webhooks are part of PRO, which is $2.99 a year. Desktop notifications and one keyword in found mode are free forever.
시작하기
RefreshPilot이 페이지를 새로고침하고 변화를 지켜보다가 중요한 일이 생기면 알려 드립니다.
무료 플랜 평생 제공 · 카드 등록 불필요 · 첫 모니터 1분 안에 가동