apify-booking-host-leads

Anyone selling to hotels and holiday lets needs the owner's own email address, not the booking site's message box — this pulls a whole city's worth of them off Booking.com in one run.

WHEN TO USE

SCOPE

USE FOR

Build a leads list of hosts or property managers for a destination on Booking.com.
Get verified contact emails for accommodation owners without a separate email-finding tool.
Find a host's official website when Booking and Google Maps don't list one.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (7)

Booking.com host & operator lead finder

Turn a Booking.com destination search into a clean table of accommodation hosts / property managers with their real contact details.

The key insight

When you scrape Booking.com, the host's contact email is sometimes already in the data under traderInfo (a trader-transparency disclosure). But this is region-dependent: strong in the EU (Zurich apartments: 80%) and Australia (Melbourne apartments: 82% in a 50-property test), and increasingly present in Asia (Beijing apartments: 65% as of June 2026, typically a QQ, 163, or Gmail address plus a Chinese company name). It is historically sparser in the US and UK. A naive chained Google Maps email scraper found emails for only ~10% and often matched the wrong business.

So use a waterfall: try the cheapest source first, fall through to more expensive ones only for leads still missing a contact. Never start with a Google Maps email extractor.

Tier	Source	Gets	Fires when
1	Booking `traderInfo`	email, phone, company	always (free, already scraped)
2	Google Maps Email Extractor (by name)	email, phone, socials, website	lead still has no email
3	Google Search (by name)	a candidate website	lead still has no website
4	Website contact scraper (on the website)	email / phone / socials	lead has a website but still no email

Prerequisites

Apify account (sign up)
Authentication via one of:
- apify login (OAuth, if using the Apify CLI)
- APIFY_TOKEN environment variable
- Token from Apify Console → Settings → Integrations

Workflow

Collect inputs. Ask the user for: destination (city/area), property type (Apartments / Guest houses / Holiday homes / Villas surface the most independent operators; none = all), max properties, and output format (CSV / JSON / Google Sheet).
Tier 1 - Scrape Booking.com. Run voyager/booking-scraper. Build a lead row per property from traderInfo and hostInfo (see Mapping below). Mark rows where traderInfo.email is present as contactSource: booking-trader.
Tier 2 - Google Maps (only rows still missing an email). Run lukaskrivka/google-maps-with-contact-details with searchStringsArray = ["<name>, <destination>", ...]. Fill email/phone/socials and capture any website it returns. Mark filled rows google-maps.
Tier 3 - Google Search (only rows still missing a website). Run apify/google-search-scraper with one query per lead ("<name> <city> official website"). Take the first non-OTA/non-social organicResults[].url as the candidate website.
Tier 4 - scrape the website (only rows with a website but no email). Default: vdrmota/contact-info-scraper (deterministic, ~14s/site). Optional: apify/ai-web-scraper with a prompt for email/phone/contact-form URL - but in live testing it was slow and failed on multiple sites, so prefer the contact scraper. Mark filled rows website-contact (or website-ai). Cap the count to control cost.
Deliver. Output one row per property. Report total rows, % with an email, and the contactSource breakdown. Rows still empty keep BookingURL (contact via Booking messaging).

Mapping (Booking item → lead row)

Output column	Source field
`name`, `type`, `address`, `city`, `country`, `rating`, `ratingLabel`, `stars`, `reviews`, `BookingURL`	top-level Booking fields (`address.full`, `address.city`, `address.country`, `rating`, `ratingLabel`, `reviews`, `url`)
`email`, `phone`	`traderInfo.email` / `traderInfo.phone` → fallback Google Maps `emails[0]` / `phones[0]`
`companyName`, `registrationNumber`, `traderAddress`	`traderInfo.companyName` / `.registrationNumber` / `.address`
`hostName`, `managedProperties`	`hostInfo.name` / `hostInfo.managedProperties` (operator-size signal)
`website`, `socials`	Google Maps fallback only; drop OTA domains (booking.com, agoda, expedia, etc.)
`contactSource`	`booking-trader` \| `google-maps` \| `none`

Put email and phone immediately after address in the output.

Always return BookingURL (link to the property), rating, ratingLabel (e.g. "Superb", "Exceptional"), and reviews (review count) for every lead. These give each row its own quality signal, so leads can be ranked and prioritized without re-opening Booking.

Actor routing

Waterfall tier	Actor ID	Maintainer	Best for
1 - Booking + trader contacts	`voyager/booking-scraper`	community	Primary. `traderInfo` holds host email/phone/company
2 - email/social/website by name	`lukaskrivka/google-maps-with-contact-details`	community	Emails Booking doesn't disclose; also returns a website
3 - discover a website	`apify/google-search-scraper`	apify	Finding the host's official site when Maps has none
4 - extract from the website (default)	`vdrmota/contact-info-scraper`	community	Deterministic email/phone/social extraction; fast and reliable
4 - extract from the website (alt)	`apify/ai-web-scraper`	apify	LLM extraction via prompt; flexible but slow/unreliable in testing

Prefer apify-maintained Actors where available.

Calling Actors — Apify CLI

Three flags on every call (--json, --user-agent, 2>/dev/null):

# 1. Scrape Booking.com
apify actors call "voyager/booking-scraper" \
  -i '{"search":"Melbourne","maxItems":50,"propertyType":"Apartments","currency":"USD","language":"en-us","sortBy":"distance_from_search","rooms":1,"adults":2}' \
  --json \
  --user-agent apify-awesome-skills/apify-booking-host-leads \
  2>/dev/null

# Tier 2 - enrich names that have no traderInfo email
apify actors call "lukaskrivka/google-maps-with-contact-details" \
  -i '{"searchStringsArray":["<name>, Melbourne"],"locationQuery":"Melbourne","maxCrawledPlacesPerSearch":1,"language":"en"}' \
  --json \
  --user-agent apify-awesome-skills/apify-booking-host-leads \
  2>/dev/null

# Tier 3 - discover a website for leads that still have none
apify actors call "apify/google-search-scraper" \
  -i '{"queries":"<name> Melbourne official website","maxPagesPerQuery":1,"resultsPerPage":5,"countryCode":"us","languageCode":"en"}' \
  --json \
  --user-agent apify-awesome-skills/apify-booking-host-leads \
  2>/dev/null

# Tier 4 - AI-extract a contact email / form URL from the website
# (confirm the prompt/instructions field name against the Actor's input schema)
apify actors call "apify/ai-web-scraper" \
  -i '{"startUrls":[{"url":"<website>"}],"prompt":"Extract the contact email, phone, and contact-form URL. Return JSON keys: email, phone, contactFormUrl."}' \
  --json \
  --user-agent apify-awesome-skills/apify-booking-host-leads \
  2>/dev/null

# Inspect input schema / fetch results
apify actors info "voyager/booking-scraper" --input --json \
  --user-agent apify-awesome-skills/apify-booking-host-leads 2>/dev/null
apify datasets get-items DATASET_ID --format json \
  --user-agent apify-awesome-skills/apify-booking-host-leads 2>/dev/null

The Apify MCP server (https://mcp.apify.com) and any MCP client (e.g. mcpc) are equivalent alternatives.

Troubleshooting

No emails returned → you are probably reading Google Maps output instead of traderInfo. Re-check the Booking item's traderInfo field first.
Emails for the wrong business → that is the Google Maps fallback matching a generic place. Trust contactSource: booking-trader rows; treat google-maps rows as lower confidence.
Many contactSource: none rows → those hosts disclosed no trader info and have no Google Business match. Use the BookingURL to contact via Booking, or accept the blank.
Run cost climbs → skip the Google Maps fallback entirely; traderInfo alone covers ~80%.
See references/gotchas.md for cost notes.

Account or credentials required

1 FOR YOU

01
Get an Apify account and a Booking scraper actor token
Sign up at apify.com and authenticate via apify login, or set APIFY_TOKEN from Apify Console → Settings → Integrations, so the skill can run voyager/booking-scraper.
```
apify login
```

This skill ships inside the Apify Community Skills plugin.

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add apify/awesome-skills --skill "apify-booking-host-leads" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

View on GitHub

Same repository

apify-ads-intelligence
Research, spy on, and analyze ads across Meta (Facebook & Instagram), Google (Ads Transparency Center + paid search results), TikTok (Ads Library + Creative Center), LinkedIn Ad Library, and X (Twitter — promoted tweets, best-effort) using Apify Actors. Use when user asks about competitor ads, ad library research, winning creatives, ad copy analysis, landing page audits from ads, cross-platform ad audits, brand transparency checks, or any task involving paid ad creatives, advertiser data, or ad targeting from public ad libraries.Read full description
apify-ai-search-visibility-tracker
Track whether a brand and its competitors get cited or mentioned across Google AI Overviews, Google AI Mode, ChatGPT Search, Perplexity, Microsoft Copilot, and Google Gemini for a defined set of prompts, on a recurring schedule. Use when user asks to track AI visibility, monitor brand mentions in AI search, track ChatGPT citations, do AI search SEO tracking, GEO tracking (Generative Engine Optimization), AEO tracking (Answer Engine Optimization), monitor Perplexity citations, track AI Overviews mentions, see if their brand shows up in AI search, discover which prompts competitors rank for in AI search, find citation opportunities, or audit a website for AI visibility readiness.Read full description
apify-app-store-intelligence
Pull structured Apple App Store and Google Play data — app metadata, price, rating, the 1–5★ ratings histogram, version, developer, and reviews — and watch it for changes over time. Use when the user asks to look up an iOS or Android app by App ID, bundle ID, package name or app name, compare a set of competitor apps across both stores, monitor a competitor's price or rating for changes, track when an app ships a new version, scrape App Store or Google Play reviews, resolve a bundle ID to a full app record, check an app's rating across multiple country storefronts, build an ASO or app-market dataset, or set up a recurring app-store watch on an app's price, rating and version. One routed Actor, praise-most-high/app-store-intelligence, is built by this skill's author; every other row is unaffiliated (see Disclosure).Read full description
apify-ashby-jobs-scraper
Scrape Ashby jobs or discover companies using Ashby with the Apify Ashby Job Board API Actor (johnvc/ashby-job-board-scraper). Job mode returns live job rows with title, company, location, remote and employment fields, publish date, apply URL, employer-published salary columns, equity flag, and Markdown descriptions. Company mode finds Ashby boards from a bundled directory or checks a prospect list, returning company name, board slug and URL, live open-job count, and verification fields. Takes company names, board slugs, or board URLs; supports pre-billing job filters and publishedAfter feeds. Use for Ashby jobs data or API requests, salary and remote-role collection, job-board pipelines, companies using Ashby/Ashby customers, ATS market maps, prospect checks, and recruiting or sales target lists. Billed per delivered result with no start fee, and MCP-ready for Claude and other AI agents.Read full description
apify-blocked-scrape-triage
Diagnose and recover a scrape that is blocked, throttled, or served empty or partial content, in cost order, before paying for a heavier Actor. Use when a run returns 0 items, when a site answers 403, 429 or a challenge page, when the HTML comes back empty or truncated, when a request fails with no response at all, when the page shows data in a browser that the Actor does not see, or when a scraper that worked yesterday suddenly returns nothing. Triggers - "I'm getting blocked", "403 from the site", "429 rate limited", "Cloudflare challenge", "scraper returns empty results", "connection reset", "page loads in my browser but not in the Actor", "do I need residential proxies", "should I switch to a browser", "my scraper broke overnight". Escalates in cost order - a cheaper published source first, then reachability, request rate and IP spread, request fidelity, session tokens, the site's own internal API, browser last.Read full description
apify-buying-signal-detection
Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises), and LinkedIn content (pain-point posts, hiring announcements) — then aggregates results into a deduplicated leads.csv with the signal source, evidence URL, and detection timestamp per row. Split-schedule architecture — Apify Actor Tasks pull raw data on their own cadence, a Claude-side aggregation task normalizes, deduplicates against a blacklist, and appends new leads with a weekly-idempotent guard. Use when the user says "find companies with buying signals", "detect intent signals for outbound", "set up a weekly lead pipeline", "monitor hiring signals for lead gen", "track startup funding leads", "find LinkedIn buying signals", "schedule Apify Actors for prospecting", "build a signals-based lead list", or "set up buying-intent monitoring for my ICP".Read full description