Skip to content
FlightPowers
Get a key

Recipe · Flights API

Round-trip search with n8n

Round-trip is a first-class paired-leg search: one object per itinerary with both legs already matched and a combined total, not two one-way lists the agent has to cross-join. The agent reads total_price and presents real bookable combinations.

Get a key on RapidAPI →All n8n recipes

Free tier on RapidAPI. No card to try.

Step 1 · Connect

Install the community node

Settings → Community nodes → Install → n8n-nodes-flightpowers (v0.2.2 on npm). Add your RapidAPI key once as a credential; every workflow reuses it.

community node package name
n8n-nodes-flightpowers

Bring your own RapidAPI key: every request is billed to your own subscription, never ours.

Step 2 · Ask it

The prompt

The job in plain words. In n8n you express it as the node configuration below instead of a prompt.

“I need a round trip New York to Paris, out October 6, back October 13. What are my options?”

Step 3 · Under the hood

What the node sends

The node issues this request against the same live API: real parameter names, exactly as the endpoint takes them.

request the node issues
// search_roundtrip_flights
{
  "from_airport": "JFK",
  "to_airport": "CDG",
  "departure_date": "2026-10-06",
  "return_date": "2026-10-13",
  "limit": 5
}

Step 4 · Read the response

Fields your logic reads

The response is flat JSON. These are the fields this recipe branches on, with what each one means.

total_pricestring

The combined price of the paired round-trip itinerary: one number for both legs, because they were searched together. total_price_as_number is the integer.

total_duration_secondsnumber

Travel time across both legs, in seconds, sortable without parsing a display string.

departure_flight_airlinestring

Operating carrier on the outbound leg.

return_flight_airlinestring

Operating carrier on the return leg, paired to the same itinerary, not cross-joined.

buy_linkstring (URL)

A Google Flights deep link that reopens this exact itinerary. Hand it to the user; it just works.

Questions, answered plainly

Is my key billed to me?
Yes. Your RapidAPI key lives in an n8n credential, the node sends it on every request, and usage meters against your own subscription on RapidAPI. There is no FlightPowers account and no second bill.
Does this need a server of mine?
Only your n8n instance, cloud or self-hosted. The node calls the API directly from wherever n8n runs; there is nothing of ours to deploy.
What does it cost?
The Google Flights Live API's free tier is 10 requests/month with a hard cap: enough to verify your key works, not to evaluate. The PRO plan is $10/month for 2,500 requests, and every plan includes every endpoint.

Also works with

Round-trip search, elsewhere in your stack

Round-trip search in ClaudeRound-trip search in ChatGPTRound-trip search in CursorRound-trip search in Claude CodeRound-trip search in OpenClaw

More recipes

More to build in n8n

One-way flight search

Flights API · search_oneway_flights

Price-insights check

Flights API · search_oneway_flights

Cheapest-date scan

Flights API · search_oneway_flights

Hotel search

Hotels API · search_hotels

Rate-parity check

Hotels API · find_hotel_by_name

Fare-alert cron

Flights API · search_oneway_flights

Ready to judge a fare, not just fetch it?

Live Google Flights and Booking.com data, with the price band and verdict attached to every result. Free tier on RapidAPI, no card to try.

Get a key on RapidAPI →See pricing

Free tier: 10 requests/month. No card to try.