Actions49
- Airbnb Actions
- AppStore Actions
- Booking Actions
- Company Insight Actions
- Emails & Contact Actions
- Expedia Actions
- G2 Review Actions
- Geocoding Actions
- GetApp Review Actions
- Google Map Actions
- Google Search Actions
- Indeed Actions
- Phone Identity Finder Actions
- Phones Owner Actions
- Product Hunt Actions
- Target Review Actions
- TikTok Profile Actions
- TripAdvisor Actions
- Trustpilot Actions
- Twitter Profile Actions
- Universal AI Scraper Actions
- Walmart Review Actions
- WebPage Screenshoter Actions
- Whitepages Addresses Scraper Actions
- Yellow Pages Search Actions
- Yelp Actions
- YouTube Actions
- Zillow Actions
Overview
This node interacts with the Outscraper API to retrieve pricing information for hotels listed on Booking.com. It is designed to fetch prices based on direct links or IDs of Booking.com hotels. This functionality is useful for users who want to automate the extraction of hotel price data for comparison, market research, travel planning, or integration into other systems.
Typical use cases include:
- Automatically gathering current hotel prices from Booking.com for a list of properties.
- Monitoring price changes over time for competitive analysis.
- Feeding hotel price data into travel booking platforms or dashboards.
Properties
| Name | Meaning |
|---|---|
| Query | Direct links or IDs of any Booking.com hotel to query prices for. Examples: full URL or hotel ID slug. |
| Async Request | Whether to make the request asynchronously. If true, the task runs in the background and results are delivered later. |
| Webhook | URL to which Outscraper will send a POST request once the asynchronous task is finished (callback URL). |
| Additional Fields | Collection of optional parameters: • UI: Execute the request as a UI task (boolean). • Fields: Specific fields to return, comma-separated string. |
Output
The node outputs JSON data containing the pricing details retrieved from the Outscraper API for the specified Booking.com hotel(s). The structure typically includes hotel identifiers, dates, room types, prices, and possibly additional requested fields depending on the "Fields" parameter.
If the request is asynchronous, the output may initially contain task status information, and the final detailed results will be sent to the provided webhook URL.
No binary data output is indicated.
Dependencies
- Requires an active Outscraper API key credential configured in n8n.
- Network access to the Outscraper API endpoint.
- For asynchronous requests, a publicly accessible webhook URL must be provided to receive callbacks.
Troubleshooting
Common issues:
- Invalid or missing hotel URLs/IDs in the Query property can cause empty or error responses.
- Not providing a webhook URL when using asynchronous mode will prevent receiving results.
- API key misconfiguration or quota limits may result in authentication errors or request failures.
Error messages:
- Authentication errors indicate invalid or missing API credentials; verify and update the API key.
- Validation errors for the Query parameter suggest incorrect hotel link format; ensure correct URLs or IDs.
- Timeout or network errors may require checking internet connectivity or Outscraper service status.
Links and References
- Outscraper API Documentation
- Booking.com Hotel URLs Format (for understanding valid hotel links)