# n8n — CryptoDataAPI

> Add live crypto market data to n8n automations: connect the CryptoDataAPI MCP server via the MCP Client Tool node, or call the REST API with an HTTP node. Free.

Bring live crypto market data into **n8n** workflows — prices, funding, open interest, liquidations, market regimes, Fear & Greed, dealer gamma and whale activity — to power alerts, dashboards and AI-agent automations.

Two ways in: give an n8n **AI Agent** our MCP tools through the **MCP Client Tool** node (so the agent decides what to fetch), or call any endpoint deterministically with a plain **HTTP Request** node. Both authenticate with an `X-API-Key` header. The MCP server is documented on the [MCP Server page](/ai-agents/mcp-server).

- **Vendor:** n8n
- **Agent docs:** https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp/
- **Config:** `MCP Client Tool node → Endpoint + Header Auth credential`
- **MCP transports:** http (streamable)

## Step 1 — Connect via the MCP Client Tool node

Add an **AI Agent** node, then attach an **MCP Client Tool** sub-node. Set the transport to **HTTP Streamable** (SSE is deprecated; you need n8n 1.104+) and the endpoint to `https://cryptodataapi.com/mcp`.

For auth, create a **Header Auth** credential with name `X-API-Key` and value `cdk_live_YOUR_KEY` (the node also supports Bearer and multi-header credentials). The agent can now call any of our MCP tools as part of a workflow.

**MCP Client Tool node:**
```text
Transport:  HTTP Streamable
Endpoint:   https://cryptodataapi.com/mcp
Auth:       Header Auth credential
  Header name:  X-API-Key
  Header value: cdk_live_YOUR_KEY
```

## Step 2 — Or call the REST API with an HTTP Request node

For deterministic pulls (no agent), use an **HTTP Request** node against any of our 180+ endpoints. Send your key as the `X-API-Key` header. Add `?format=markdown` to many endpoints to get clean, LLM-ready text you can drop straight into a message node.

Example: fetch the whole-market snapshot to feed a scheduled report.

**HTTP Request node:**
```text
Method:  GET
URL:     https://cryptodataapi.com/api/v1/daily
Header:  X-API-Key: cdk_live_YOUR_KEY
```

## Step 3 — Build an automation

A common pattern: a **Schedule** trigger every 15 minutes → HTTP Request to `/api/v1/regimes` (or the `get_cycle_regime` MCP tool) → an **If** node that checks whether the regime changed since the last run → a **Slack** or **Telegram** node that posts the alert. Mind the rate limits (Free 5/min) and the `Cache-Control` cadence — polling every 1–30 minutes is plenty.

## Example prompts

- "When the market regime flips, post a summary to our #trading Slack channel."
- "Every morning at 8am, send a Telegram message with the daily market snapshot."
- "If BTC funding turns sharply positive, alert me — it may signal crowded longs."
- "Log the Fear & Greed index to a Google Sheet every hour."
- "Watch for a spike in liquidations and DM me the top affected coins."

## FAQ

### Does it cost anything?

No. The **Free** API tier (no card) covers market health, regimes, Fear & Greed, macro, flows, coin profiles and full-universe Hyperliquid funding + open interest — plenty for most alerts. Per-coin quant, gamma and whale signals need [Pro](/pricing).

### MCP node or HTTP node — which should I use?

Use the **MCP Client Tool** node when an n8n **AI Agent** should decide which data to pull. Use the **HTTP Request** node for fixed, scheduled pulls where you already know the endpoint — it's simpler and fully deterministic.

### The MCP node won't connect.

Confirm you're on n8n **1.104+** (older versions only have the deprecated SSE transport), that the transport is set to **HTTP Streamable**, and that the Header Auth credential sends `X-API-Key` with a valid `cdk_live_` key. A 429 means you've hit the rate limit — slow the schedule down.

## Related

- [MCP Server](https://cryptodataapi.com/ai-agents/mcp-server)
- [REST API docs](https://cryptodataapi.com/api/docs)
- [LangChain setup](https://cryptodataapi.com/ai-agents/langchain)
- [OpenClaw setup](https://cryptodataapi.com/ai-agents/openclaw)
- [Prompt library](https://cryptodataapi.com/prompts)

---

Canonical: https://cryptodataapi.com/ai-agents/n8n
Machine-readable API map: https://cryptodataapi.com/llms.txt
Agent skill repo: https://github.com/Crypto-Data-API/cryptodataapi-skills (`npx skills add Crypto-Data-API/cryptodataapi-skills -g -y`)
Free API key (no signup): POST https://cryptodataapi.com/api/v1/auth/keys {"email":"you@example.com"}