Skip to main content
AnyAPI ships an official n8n community node so you can run any API in the catalog from inside a workflow. Add one credential, drop in the AnyAPI node, pick an API from a live dropdown, and pass its normalized input. The same node reaches the whole catalog, so a single workflow can fan out to many AnyAPI endpoints on one key and merge the results.

​
Prerequisites

  • An AnyAPI key. Create one in the dashboard under API keys.
  • A funded USD wallet. Run API bills your wallet per successful request; discovery is free. New accounts start with a small free credit, so you can test before topping up.
  • An n8n instance where you can install community nodes (self-hosted, or any plan that allows them).

​
Install

1

Open community nodes

In n8n, go to Settings > Community Nodes and select Install.
2

Install the package

Enter the package name and confirm:
n8n downloads and installs the node. See the community nodes installation guide for details.
3

Add the AnyAPI node

In any workflow, search for AnyAPI in the node panel and add it.

​
Create the AnyAPI credential

The node authenticates with one AnyAPI API credential.
1

Add a new credential

On the AnyAPI node, create a new AnyAPI API credential.
2

Paste your key

Paste your AnyAPI key into API Key. It is sent as Authorization: Bearer <key>.Leave Base URL at its default, https://api.getanyapi.com. Change it only for a self-hosted or staging gateway.
3

Save

On save, n8n validates the key against the wallet balance endpoint. A valid key with a reachable wallet passes; an invalid one is rejected before you build a workflow.

​
Operations

The single AnyAPI node exposes execution, Request retrieval, discovery, and balance operations.
Run an API by its SKU with a normalized JSON Input payload. The API dropdown loads live from the public catalog, so available SKUs appear without being hard-coded into the node.Returns the normalized output, the serving provider (always AnyAPI), the costUsd of the call in real dollars, and items (the number of results charged for). You are billed on success only.The node waits and polls long-running calls by default. Enable Return Immediately to emit a resumable Request ID. The node sends the paid POST once and polls AnyAPI’s Request state.
Get Request returns the current stored state. Wait for Request polls that state until the terminal result is ready. Connect the Request ID from a Run API node configured with Return Immediately.
Fetch the input and output JSON Schema for one API. Use the input schema to build a valid payload for Run API.
Browse the AnyAPI catalog, optionally narrowed with Category (a category slug). Returns one item per API.
Run a ranked free-text catalog search, optionally narrowed with Category or Platform. Results include the description and relevance metadata you need to choose a SKU.
Return the remaining wallet balance in USD for the key on the credential. Never charges.

​
Gateway and node responsibilities

The node is a lightweight n8n transport and presentation adapter. It uses n8n’s native HTTP and credential helpers, projects the discovery fields its UI needs, and tolerates safe additions to catalog responses. The AnyAPI gateway owns input validation, provider selection, routing, failover, pricing, health semantics, and billing. Discovery operations display those gateway-published facts: pricing.from is the primary static offer, pricing.failoverMaxUsd is the fallback ceiling, and failover reports whether AnyAPI currently has an alternate route. The node does not calculate these values from lanes, and input and output schemas pass through as opaque JSON Schema objects. Each static maximum is published in two denominations: maxUsd for one request and maxPer1kUsd for 1,000 of them, with failoverMaxPer1kUsd beside failoverMaxUsd. Per 1,000 requests is the denomination AnyAPI quotes customers in, because most of the catalog costs a fraction of a cent per call and per-request figures cannot be compared by eye. Read the published per-1k field rather than scaling maxUsd yourself, which drifts in floating point (0.0966 * 1000 is 96.60000000000001 in most languages). baseUsd and perUnitUsd have no per-1k twin, because they are charged per billable item inside one call, and the costUsd on a completed run stays per request.

​
Response budget options (Run API)

Run API has three optional controls under Options that shrink the response payload so a large result does not flood the next node. They change only what is returned to you, never what you are billed (costUsd reflects the full result the API produced):

​
Worked example

Add an AnyAPI node, select Run API, pick Reddit Search (reddit.search) from the API dropdown, and set Input to:
Execute. The node returns the normalized envelope, including the exact costUsd of the call:
provider is always AnyAPI and costUsd is what the call cost you in real dollars. Pricing is pay per request in USD, with no subscription, and failed calls are never charged.

​
One key, many APIs

Because every API shares one credential and the same response envelope (output plus costUsd), a single workflow can fan out across many AnyAPI endpoints (for example Google News, Trustpilot, Similarweb, Reddit, LinkedIn, Google Search, and X / Twitter), then merge them with a Merge node and hand the combined result to an AI Agent. Adding a sixth source is just another AnyAPI node on the same key.
Prefer to call AnyAPI directly? The same catalog is available over plain REST (see the Quickstart) and through one MCP server for AI agents. Need help? Reach out at support@getanyapi.com.