Integrations · n8n
Fare logic as an n8n workflow
A community node for live flight and hotel data. Because every fare arrives with Google's low | typical | high verdict, “alert me when it's cheap” is one IF condition: no price-history database to build first.
Free tier on RapidAPI. No card to try.
n8n-nodes-flightpowersv0.2.2 on npm. Install by name, then add your RapidAPI key once as a credential. Every workflow reuses it.
Setup
Three steps to a working node
No repo to clone and no build step: n8n pulls the package from npm.
- 1
Install the node
Settings → Community nodes → Install, enter n8n-nodes-flightpowers, confirm. n8n fetches it from npm and restarts the node list.
- 2
Create the credential
Add a credential for the node and paste your RapidAPI key. It is stored by n8n and referenced by name. Exported workflow JSON never contains it.
- 3
Drop it into a workflow
Add the node to a canvas, pick what to search, and wire the output into the rest of your flow like any other node.
What to build
Three workflows that earn their cron slot
Each pattern below is prose plus the step list. The full recipes, with the exact request and response fields, are linked from each card.
Fare-watch cron
A schedule trigger runs a flight search every morning. An IF node checks whether price_range_in_relation_to_other_periods equals "low". Google's band is the price history, so that one comparison is the whole alert. On true, send the fare and its buy_link to email, Slack, or Telegram.
- 1. Schedule trigger (daily)
- 2. Flight search via the node
- 3. IF: verdict == "low"
- 4. Notify with price + buy_link
Rate-parity check
Look up the same hotel several times, identical except proxy_country: each request is priced from a residential proxy in that market. Merge the results, compute the spread on price, and flag when one market undercuts your contracted rate.
- 1. Schedule trigger (weekly)
- 2. Hotel lookup × per market
- 3. Merge + compute spread
- 4. Alert when spread > threshold
Cheapest-date scan
Generate the dates of a month, run a search per date, and sort the merged results on price_as_number. The output is a fare calendar: post the cheapest dates to a sheet or feed a weekly “when to fly” digest. Budget one request per date.
- 1. Generate date list
- 2. Search per date via the node
- 3. Merge + sort by price
- 4. Write calendar to sheet
Questions, answered plainly
- I found n8n-nodes-flight-hotel-data. Is that this?
- That is the old package name, now superseded. Install n8n-nodes-flightpowers instead: it is the maintained node (v0.2.2 on npm). If you have the old one installed, switch; new releases land only on the new name.
- Where does my key live?
- As an n8n credential. You create it once (the value is your RapidAPI key) and every workflow that uses the node references the credential. n8n stores it encrypted; it never sits in the workflow JSON you export or share.
- Is my key billed to me?
- Yes. The node calls the live API with your key, so every execution meters against your own RapidAPI subscription. A daily fare-watch is about 30 requests a month; a 30-day date scan is 30 requests per run. Size your plan to your schedule.
- Does it work on n8n Cloud and self-hosted?
- Community nodes install by package name from the Settings screen on instances that allow them; self-hosted n8n always can. The node itself is ordinary JavaScript from npm: nothing about it requires self-hosting.
- Can I use plain HTTP Request nodes instead?
- Yes. The REST API works from a stock HTTP Request node with your key in an x-api-key header, no community node needed. The node saves you the request-building and gives you typed parameters; the API is the same either way.
All seven n8n recipes
Step-by-step, per task
One credential, every workflow
Install the node, paste your RapidAPI key once, and every fare your workflows touch arrives already judged: low, typical, or high.
Free tier: 10 requests/month. No card to try.