SearchApiInstall

Summary

Search Google Flights for an itinerary and return matching flight results. Choose airports and dates for standard searches, or provide a multi-city itinerary; optional settings tune passenger counts, locale, flight filters, pagination, and data retention.

Inputs

• Departure Airport and Arrival Airport — Enter a three-letter airport code or a location identifier beginning with /m/. Multiple airports or locations can be comma-separated. These are not required for multi-city searches.
• Outbound Date and Return Date — Use YYYY-MM-DD dates. Outbound date is not required for multi-city searches; return date is not required for one-way or multi-city searches.
• Multi City Json — For a multi-city search, provide a JSON string describing itinerary legs, each with departure_id, arrival_id, outbound_date, and optional time ranges.
• Localization — Optionally set the search country (default us), result currency (default USD), and interface language (default en).
• Filters — Optionally filter or sort results by flight type, airlines, connecting airports, stops, travel class, bags, emissions, layover and flight duration, price, departure and arrival times, separate tickets, or hidden and cheapest flights. Defaults generally leave filters unset; stops defaults to any.
• Number of Passengers — Set adults (default 1), children, infants in seats, and infants on laps (each default 0). The UI notes a maximum of 9 passengers; bag counts cannot exceed passenger count.
• Pagination — Pass a booking_token to retrieve booking options for selected flights, or a departure_token to select a flight and retrieve return flights or the next multi-city leg.
• Zero Retention — Enable to disable logging and persistent storage of request parameters and responses.
• Request Options — Configure request batching, SSL certificate handling, an HTTP proxy, or request timeout.

Output shape

A SearchApi response containing flight search results.

The provided source pack exposes only signatures for the node and flight engine, so it does not show the response fields or any result transformation. Flight data shape is therefore unspecified here.

Links

• n8n community nodes installation guide