Booking.com Hotel Price Drop Alerts (n8n + Apify + Gmail)

Get automated Booking.com hotel price drop emails—every morning

This n8n workflow checks the same Booking.com hotel shortlist each day, compares the re-priced totals with yesterday’s prices for the same stay, and emails you only the hotels that got cheaper—showing the old price, new price, and savings.

What this workflow does

• Runs daily at 07:00 using an n8n Schedule Trigger.
• Re-prices your shortlisted properties by calling the Booking.com Prices Scraper via an n8n core HTTP Request node (run-sync endpoint).
• Sends one input row per hotel with hotelIds (or hotelNames/startUrls), plus checkIn (e.g., relative “45 days”), nights, adults, and currency.
• Compares totals with the last run in a Code node:
  • Keys each property as hotel_id|check_in
  • Reads previous totals from n8n workflow static data (up to 5,000 keys)
  • Computes change_pct and keeps drops of at least DROP_PCT (default 3%)
  • Tracks sold-out cases
• Emails only price drops with a ready-to-send subject, table, and body via Gmail; if nothing changed, it performs a NoOp.

Use cases

• Travelers monitoring a shortlist and wanting “deal alerts,” not constant manual checking.
• Travel agents watching client stays and notified when Booking.com totals drop.
• Revenue managers tracking comp sets and confirming price movement over time.

Technical details

• n8n nodes: Schedule, HTTP Request, Code, IF, Gmail, NoOp, Sticky Note
• Apify integration: “Booking.com Prices Scraper” using a Header Auth credential (Authorization: Bearer <Apify token>), no database—state is stored in workflow static data.