Hotel Reviews Radar 🛎️

Only the reviews you haven't seen yet — never the ones you already have.

Most review scrapers hand you the entire history every single run, and you pay for the same 500 old reviews again and again. This one remembers what it already showed you. Run it daily and you get exactly what's new since yesterday — nothing else.

Why hotels and management companies use this

• Never miss a new review again. Point it at your hotels on Agoda; every run finds what's genuinely new since the last check, so a fresh 1-star review doesn't sit unanswered for a week.
• Pay only for what's actually new. The first run establishes a baseline of your current reviews — completely free. From then on, you're billed once per new review, ever, no matter how many times you re-run.
• No duplicate charges, guaranteed. Every review is tracked with a permanent, durable record — a re-run, a retry, or a crash never bills you twice for the same review.
• Built for daily automation. Attach an Apify Schedule and forget it — a clean digest lands in your dataset (and optionally your webhook) every morning.

How it works

1. Give it your hotel pages on Agoda and a monitorId to name this watch.
2. The first run silently catalogs every review currently visible — free, no charge, no data written yet.
3. Every run after that fetches the latest reviews and delivers only the ones with a real, dated publish time after your monitor started — with the author, rating, text, and date.
4. A short digest tells you what's new across all your hotels; an optional webhook can push it to Slack, Telegram, or your own system (via Make/Zapier/n8n).

What you pay for

One event only — review-delivered. Billed once per genuinely new review: real Agoda-sourced content, a reliable publish date after your monitor's baseline. Your very first run's entire visible history is free. Repeat deliveries of a review you've already been billed for — impossible, by design (a permanent record per review prevents it). Errors, blocked attempts, and unreadable data cost nothing.

On the rare occasion the charge itself can't be confirmed after a review has already been written to your dataset, we never retry it and never bill you for it later — you keep that row for free rather than risk a duplicate charge. This is intentional: the system always favors undercharging over overcharging.

What it does NOT promise

Real-time push notifications the moment a review appears (this is a scheduled daily check, not a live feed from Agoda), sentiment analysis or an AI-drafted reply, tracking of edited or disappeared reviews (v1 only delivers new reviews — it does not report when a previously-seen review is removed or changed), or coverage of Booking.com/TripAdvisor/Expedia (v1 covers Agoda only).

Input

Field	What it does
monitorId	Names this watch's own durable history — required, since the whole point is remembering what you've already seen
hotels (1–30)	Agoda hotel page URLs
notifyOn	new_reviews (default) fires the webhook only when something new showed up; always/never for the rest
webhookUrl	HTTPS only; delivers the daily digest of new reviews as JSON

Output

• Dataset — one row per genuinely new review found: reviewer, rating, title, text, publish date, and when this monitor first saw it. In the vast majority of cases this is also the review you were billed for; in the rare edge case above, it's a row you got for free.
• Key-value store — a short digest (per-hotel counts, average rating, negatives flagged) and a coverage report showing how many hotels answered cleanly vs. partially vs. failed, with reasons. The digest and any webhook notification only ever count reviews you were actually billed for.
• Run status — a clear reason on bad input, a busy monitor, low coverage, or a run that overran its time budget (reported as failed rather than a silently truncated "success"); anything already saved and billed stays saved and billed.

Limits (v1)

Up to 30 hotels, up to 8 pages of reviews per hotel per run (Agoda-only in v1 — Booking.com, TripAdvisor, and Expedia are on the roadmap); one retry per hotel on a transient error; an early stop if too many hotels fail in a row, so a bad run doesn't burn through your budget for nothing.

A note on the source

Data comes from Agoda's public review pages via the same request pattern a browser makes. Agoda's Terms of Service restrict automated access — use this at your own discretion.