n8n-nodes-rapidapi-pro

The n8n node to call any API on RapidAPI — and track your usage.

RapidAPI is a marketplace where you can subscribe to thousands of third-party APIs (weather, translation, databases, currency, AI models…) and call them all through one gateway with one key. This community node turns that gateway into a drag-and-drop node for your n8n workflows: paste your RapidAPI key once, then start calling services in seconds.

What it does

• 🔑 One credential, every API — your RapidAPI key is added automatically to every request as the X-RapidAPI-Key header. No per-request setup.
• 🗂️ Built-in Service Library — store one or more services inside the node, then call them from a dropdown. A ready-to-use Example Weather service ships pre-loaded (with a pre-selected operation), so a freshly dragged-in node works out of the box — no setup required.
• 🔗 Discover from a link — paste a RapidAPI project link (or a direct OpenAPI/Swagger JSON URL) and the node automatically finds the operations and pre-fills sample values for every parameter. No manual setup needed.
• 📊 Usage & quota tracking — see how many requests and credits you have used and how many remain, or ask the node to attach X-RateLimit-* metadata to every response so you can watch consumption without an extra call.
• 🧰 Full control when you need it — override query/header/path parameters and request bodies per execution, change timeouts and response formatting, or build a fully manual request.

Requirements

• n8n 1.0 or newer.
• A RapidAPI key from rapidapi.com. Open the Security tab of any API you have subscribed to (or Apps) to find your key. Your key needs an active subscription for the API you want to call.

Installation

There are two ways to install a community node in n8n: automatically from inside n8n, or manually with npm.

Automatic (recommended)

The easiest way — install straight from n8n's user interface:

1. Open n8n and go to Settings → Community Nodes.
2. Click Install a community node.
3. Search for n8n-nodes-rapidapi-pro (or “RapidAPI”).
4. Click Install. n8n downloads, builds and reloads the node for you — no terminal needed.
5. When the page reloads, the RapidAPI node appears in the node panel — just drag it into your workflow. The node calls RapidAPI itself, so you don’t need a separate HTTP Request node.

If you don’t see the node after installing, restart n8n once.

Manual (npm)

If you prefer a command line, or your n8n instance doesn’t offer the Community Nodes UI, install the package directly:

1. Open a terminal and install into the directory where n8n itself is installed — this is a single shared location for all n8n services (the core, the management panel, the triggers and any add-ons all run inside one Node process). Use the folder of your n8n install, or run npm root -g to find your global folder.
2. Install the package:

   npm install n8n-nodes-rapidapi-pro

   …or for a globally-installed n8n:

   npm install -g n8n-nodes-rapidapi-pro

3. Restart the whole n8n process — not a single service. Because every n8n service (core, panel, triggers, add-ons) runs in the same shared process, the new node is only registered when that whole process restarts once. Restart it the way you normally run n8n, for example...

   docker compose restart n8n            # Docker
   sudo systemctl restart n8n            # systemd (Linux)
   pm2 restart n8n                       # PM2

   …or restart it from your n8n management panel / process manager if you use one.
4. After the restart, the RapidAPI node appears in the node panel, ready to use.

If you later update the package (npm update n8n-nodes-rapidapi-pro), restart the whole process again so the new version gets registered.

Credentials

Before your first call, create a RapidAPI API credential:

1. Get your key on rapidapi.com → Security tab of your subscribed API (or Apps).
2. In n8n, open the node (or Credentials → New credential → RapidAPI API).
3. Paste your RapidAPI Key.
4. (Optional) Set a Default API Host — only a fallback for fully manual requests; services always carry their own host.

The credential includes a test request that reaches the usage endpoint, so n8n can confirm your key is valid before you save it.

[!WARNING] Geo-blocked? RapidAPI refuses to serve some regions and answers with HTTP 451 (Sorry, we are unable to provide RapidAPI services to your location.). If the credential test (or any call) fails with that message, your key is fine — it’s your location that’s blocked. The node now detects this and explains it in the error instead of showing a generic failure. To use the node you’ll need to run n8n from an allowed region (or proxy/VPN through one). This is a RapidAPI-side restriction the node cannot bypass.

Usage examples

Call any service from your library

Add the RapidAPI node and keep Operation = Call API. It arrives with the Example Weather service and its GET /current operation already selected and parameter values pre-filled — hit Execute and it works immediately.

To call your own API instead:

1. Set Source = From My Library. Only then does the Service Library editor appear — link and manual modes have their own fields, so the three sources never mix.
2. Click Add a service, give it a Name and the API Host (e.g. weatherbit-v1-mashape.p.rapidapi.com).
3. Inside that service, Add an operation — pick a method, give it a path (e.g. /current) and define its parameters (e.g. lat, lon).
4. Back on the node, choose the service and operation from the dropdowns — the operation inputs update to match.
5. Fill in the parameter values (or use expressions), then run. Your key is added automatically.

Store several services and switch between them with one click — each brings its own host, operations and parameters.

Discover an API from a link (no manual setup)

1. Set Source = Import from a link.
2. Paste your RapidAPI project link, e.g. https://rapidapi.com/{owner}/{api}/, or a direct OpenAPI/Swagger JSON URL.
3. Pick an operation from the dropdown — the node fills the parameters with sample values from the spec.
4. Run it. First-time users: if RapidAPI blocks the server-side request to its docs page, use the direct openapi.json/swagger.json URL from the provider’s site instead.

Track your usage

Set Operation = Check Usage & Quota. The node returns requestsUsed, requestsRemaining, requestsQuota, creditsUsed, creditsRemaining, creditsQuota, percentUsed, and the billing window (from / to). Want per-request consumption without an extra call? Turn on Options → Response → Include Usage Metadata on any Call API request to append a _usage object built from the X-RateLimit-* headers.

Import a service for reuse

Set Operation = Import Service, paste a link/URL and the node builds a ready-to-use service definition (host + operations + sample parameters) with an endpoints summary. Copy serviceJson into the Service Library of a Call API node to keep it around.

Compatibility

• n8n 1.0+ (n8nNodesApiVersion: 1, built with @n8n/node-cli).
• Node.js 20+ locally to build/develop.
• No runtime dependencies — every HTTP request goes through n8n’s built-in helpers. Ships credential, node and icons only.

[!NOTE] RapidAPI occasionally blocks server-side requests to its documentation pages. If Import from a link can’t find the spec, grab the direct OpenAPI/Swagger JSON URL from the provider (look for openapi.json / swagger.json) — the node accepts those links too.

Development

Run the tests

Unit tests run with vitest — no network access needed:

npm test          # run once
npm run test:watch  # watch mode

The suite covers the parsers (parseServices / parseOperations / parseParameters), URL building, header/query/path collection, OpenAPI import, usage normalization, and the request builder.

Build

npm run build      # compiles TypeScript into dist/
npm run lint       # n8n community-node style checks
npm run lint:fix   # auto-fix style issues

Try it in a locally-running n8n

If n8n runs locally (e.g. on port 5678) and the node isn't linked yet:

npm run build
npm link                 # register this package globally (repo root)
cd "$(npm root -g)/n8n"  # or wherever your n8n install lives
npm link n8n-nodes-rapidapi-pro

Then restart the whole n8n process — the node only registers on full restart. For live reload while developing, use n8n-node dev in this directory.

⚙️ Testing from a geo-blocked region? You can still verify the node end-to-end: the Example Weather service is pre-loaded, the UI now separates the three sources, and a blocked credential test/call surfaces a clear 451 explanation instead of a generic error — so you can confirm the node itself works even where RapidAPI won't answer.

Resources

• n8n community nodes documentation
• RapidAPI marketplace
• @n8n/node-cli

Version history

0.2.0

• UX overhaul: clearer "Action" selector + per-mode notices; the Service Library only appears in From My Library mode (it no longer mixes into link/manual modes); numbered setup steps; clearer field descriptions.
• Works out of the box: the pre-loaded Example Weather service parses correctly and the dropdowns arrive pre-selected — a fresh node runs immediately.
• Clearer errors: RapidAPI's geo-block (HTTP 451) is now detected and explained ("your key is fine, your region is blocked") instead of showing a generic failure.
• Robust parsing: parseServices/parseOperations/parseParameters accept both n8n's wrapped fixedCollection shape and plain arrays (legacy/default data).
• Tests: added vitest + 61 unit tests (npm test).

0.1.0

• Initial release: Call API, Check Usage & Quota, Import Service, internal Service Library, automatic headers.

License

MIT

💼 Need a custom n8n workflow?

Get professional n8n development & automation support at https://tally.so/r/q4q1L9