Plan flights or a complete trip with Apify

Turn travel data into a decision rather than a list of results. Preserve the requested scope, distinguish sourced prices from estimates, and keep unresolved price or itinerary coverage explicit.

Disclosure: The skill author also maintains the two paid Apify Actors used here.

Route the request

• Flights only: read references/flights.md. This includes flight-only round-trip, multi-city, and open-jaw requests. Do not load the hotel or whole-trip references merely because the flight has several segments.
• Whole trip: when the requested output combines flights with lodging, an event plan, overnight bases, or a full trip budget, read references/whole-trip.md, then references/flights.md and references/hotels.md.
• Hotel or lodging only: do not use this skill. Use the selected Actor's current documentation or a dedicated lodging skill.
• Supplied results: analyze usable supplied Actor output without rerunning the Actor unless fresher data is requested or required.

Data sources and prerequisites

For live flight searches, use Google Flights Data Scraper. For lodging within a whole-trip plan, use Google Hotels Search Scraper. Access them through Apify MCP or another available Apify interface.

Before a live call, inspect the Actor's current README, input schema, pricing, and returned payload. Estimate the intended run before starting paid work. Keep optional billable features off unless the user needs them. Treat the Actor documentation as the source for current inputs and operation; use this skill for the judgment that the documentation does not provide.