Resources · n8n integration

CoinGecko n8n integrationAutomate CoinGecko with n8n.

Crypto data belongs in the same workflow as the rest of your reporting. The CoinGecko n8n integration exposes 9 operations spread over 2 resources, coins and events. No trigger node ships with it, so a schedule or another app starts the run. Written for ops and finance people who build their own automations.

Try the CoinGecko integration on n8nSee the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the CoinGecko n8n integration actually cover?

The CoinGecko node reads public market data and writes nothing back. It groups 9 operations under 2 resources: Coin, which answers questions about a currency pair or a single coin, and Event, which lists what CoinGecko has on its calendar. You choose a resource, you choose an operation, and the node returns items that any downstream node can use.

Three shapes of workflow cover most of what teams build here. The first is the recurring snapshot: a Schedule Trigger fires, coin.market returns every trading pair quoted in your reference currency, and the rows land in Google Sheets where finance already works.

The second is the alert. coin.price answers with the current value of the coins you follow, an If node compares that value to a threshold you store yourself, and Slack gets a message only when the comparison flips. Quiet days stay quiet.

The third is the archive. coin.history reads one calendar day at a time, coin.marketChart returns a whole series for a pair, and a page in Notion keeps a record that outlives whatever a public dashboard chooses to display today. Run it once per date and the archive fills itself in the background.

Reach for the HTTP Request node the moment the endpoint you want is not one of the 9 operations. It calls any CoinGecko endpoint directly and reuses the same predefined authentication, so the rest of the workflow does not change. The limits are worth saying out loud. There is no CoinGecko trigger node, so nothing here is event-driven. The contract address path only offers Ethereum as a platform. Return All walks the pages of a list, which means a broad market pull is a series of API calls rather than one.

If the platform itself is still an open question, the n8n review goes through the trade-offs, and the n8n training covers expressions and error handling, the two things that break unattended data workflows first.

Connect

How do you set the CoinGecko node up?

  1. 01

    Drop the node into a workflow

    Search CoinGecko in the node panel and add it. The node ships with n8n, on n8n Cloud and on a self-hosted instance alike, so there is nothing to install and nothing extra to pay on the n8n side. It exposes no authentication selector: where a credential is involved, you create it once from the Credentials menu and every workflow reuses it from the node's dropdown.

  2. 02

    Pick the resource, then the operation

    Resource comes first. Coin carries eight of the nine operations, from a single price to a full candlestick chart. Event carries one, Get many events. The operation you select rewrites the parameter list underneath it, which is why the node looks different depending on what you asked for. Nothing is shared between the two resources beyond Return All and Limit.

  3. 03

    Give it a starting point and run it

    CoinGecko has no trigger node, so the workflow needs another starting point: a Schedule Trigger at a fixed interval, an n8n Webhook, meaning a URL another service calls, or the trigger of a different app. Fill the required fields, use an expression such as {{ $json.coinId }} to read a value from the item before, then hit Execute and read the output.

Actions

What can the CoinGecko node do?

The CoinGecko node exposes 9 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGetGet ManyCandlestickHistoryMarketMarket ChartPriceTicker
Coin✓✓✓✓✓✓✓✓
Event✓

Coin

8 operations
01

Get a candlestick for a coin

coin.candlestick

What you see in n8n

Notes & use cases

Builds the open-high-low-close chart of one currency pair over a window you choose, and hands back one item per interval.

Key parameters

  • Base Currency Name or ID: the first currency in the pair, BTC in BTC:ETH. Pick it from the list, or pass an ID with an expression such as {{ $json.base }}.
  • Quote Currency Name or ID: the second currency, ETH in BTC:ETH, from the same list or the same kind of expression.
  • Range (Days): how far back the chart reaches, from 1 to 365, or max for everything available.
Use cases
a weekly candlestick pull for the pairs a treasury actually holds, stored somewhere that keeps the chart once the free dashboard has moved on.
02

Get a coin

coin.get

What you see in n8n

Notes & use cases

Fetches the current record of one coin. Optional blocks decide how much of that record travels with it.

Key parameters

  • Search By: Coin ID or Contract Address, and the choice decides which of the fields below the node asks for.
  • Coin Name or ID: the CoinGecko identifier, bitcoin style, from the list or from an expression.
  • Platform ID: the chain that issued the token, with Ethereum offered in the list.
  • Contract Address: the token's contract address, used instead of the coin identifier.
  • Options: Community Data, Developer Data, Localization, Market Data, Sparkline and Tickers each add a block to the response.
Use cases
enriching a token watchlist so each row carries developer and community data next to the name.
03

Get many coins

coin.getAll

What you see in n8n

Notes & use cases

Lists the coins CoinGecko knows, one item per coin. This is where the identifiers the other operations expect come from.

Key parameters

  • Return All: switched on, n8n keeps requesting pages until the list runs out; switched off, it stops at Limit.
  • Limit: the maximum number of coins a single run brings back.
Use cases
refreshing a lookup table of coin identifiers in a spreadsheet, so no expression elsewhere in the workflow ever points at a name the API no longer resolves.
04

Get history for a coin

coin.history

What you see in n8n

Notes & use cases

Goes back to one calendar day and returns the coin as it stood then: name, price, market and stats in a single snapshot.

Key parameters

  • Coin Name or ID: which coin the snapshot belongs to, chosen from the list or supplied by an expression.
  • Date: the date of the snapshot, a dateTime value, often {{ $json.date }} when a previous node loops over a range of days.
  • Localization (in Options): excludes localized languages from the response and keeps the payload small.
Use cases
rebuilding a quarter of daily snapshots for an accounting export, one run per date, without touching a spreadsheet by hand.
05

Get market prices for a coin

coin.market

What you see in n8n

Notes & use cases

Covers every trading pair quoted in one currency at once, with the market figures attached and the sort order under your control.

Key parameters

  • Base Currency Name or ID: the currency everything gets quoted against.
  • Return All and Limit: all pairs page by page, or a capped slice.
  • Coin IDs (in Options): a comma-separated list that narrows the result to the coins you care about.
  • Order (in Options): sort by market cap, volume, id or gecko rank, ascending or descending.
  • Price Change Percentage (in Options): adds change columns for the windows you tick, from 1h to 1y.
Use cases
a daily watchlist table ordered by market_cap_desc, filtered to the handful of coins a fund reports on.
06

Get market chart for a coin

coin.marketChart

What you see in n8n

Notes & use cases

Feeds a chart with the historical series of one pair: price, market cap and 24h volume, at a granularity the API picks automatically.

Key parameters

  • Search By: Coin ID or Contract Address, the same fork as the single-coin operations.
  • Platform ID and Contract Address: the issuing chain, Ethereum in the list, and the token address when you take the contract route.
  • Base Currency Name or ID and Quote Currency Name or ID: the two sides of the pair, BTC then ETH in BTC:ETH.
  • Range (Days): 1, 7, 14, 30, 90, 180, 365 or max.
Use cases
a monthly performance report that needs a full series rather than a single reading.
07

Get the price for a coin

coin.price

What you see in n8n

Notes & use cases

Answers with the current price of one or several coins in one or several quote currencies. It is the shortest path from CoinGecko to an If node.

Key parameters

  • Search By: Coin ID or Contract Address.
  • Base Currency Names or IDs: a multi-select, since this operation prices several coins in one call.
  • Quote Currency Names or IDs: also a multi-select, for the currencies you want them priced in.
  • Platform ID and Contract Addresses: the chain, and the addresses comma-separated, on the contract route.
  • Options: Include 24hr Change, Include 24hr Vol, Include Market Cap and Include Last Updated At.
Use cases
a threshold alert that reads a target stored in a sheet, compares it, and only then posts to a channel.
08

Get the ticker for a coin

coin.ticker

What you see in n8n

Notes & use cases

Tickers are the quotes a coin gets on each exchange, and this operation returns them as separate items you can filter and rank.

Key parameters

  • Coin Name or ID: the coin whose tickers you want, from the list or an expression.
  • Return All and Limit: every ticker across the pages, or a fixed number.
  • Exchange Names or IDs (in Options): keeps only the exchanges you name.
  • Include Exchange Logo (in Options): adds the exchange logo to each ticker.
  • Order (in Options): rank by trust score, ascending or descending, or by volume, descending only.
Use cases
checking where a coin trades before a treasurer routes an order by hand.

Event

1 operation
09

Get many events

event.getAll

What you see in n8n

Notes & use cases

Switches the node over to the Event resource and returns the events CoinGecko lists, one item each, with filters to keep the list relevant.

Key parameters

  • Return All and Limit: the whole list page by page, or a capped number of events.
  • Country Code (in Options): keeps events from one country.
  • From Date and To Date (in Options): a window, events after the first and before the second.
  • Type Name or ID (in Options): filters on the type of event.
  • Upcoming Events Only (in Options): drops everything already past.
Use cases
a weekly digest of upcoming events pushed into a shared calendar so a research team plans around them.
Need help

Need help automating CoinGecko with n8n?

A person reads every message.

FAQ

CoinGecko and n8n, the questions that come up

01Is the CoinGecko n8n integration free?
Yes, on the n8n side. The CoinGecko node ships with n8n, so there is nothing to install, nothing to buy as an add-on, and the same node is available on n8n Cloud and on a self-hosted instance running the Community Edition under the Sustainable Use licence. A workflow built in one place behaves the same in the other. What CoinGecko itself charges for API access is a separate question, and the n8n documentation for this node does not cover it, so check that on their side before you schedule anything that runs often.
02What credentials or permissions does the CoinGecko node need?
Less setup than most nodes. The CoinGecko node has no authentication selector in its parameters, and the n8n documentation page for it lists the operations without publishing a separate credentials page. Where a credential is involved in n8n, the pattern is always the same: you create it once from the Credentials menu, and every workflow picks it up from the node's dropdown rather than storing keys in the workflow itself. If you need an endpoint the node does not expose, the HTTP Request node reuses that same credential through predefined authentication.
03What are the limits of the CoinGecko node in n8n?
Three worth knowing. The node covers 9 operations across 2 resources, so anything outside that list goes through the HTTP Request node, which calls any CoinGecko endpoint directly while the rest of the workflow stays untouched. Lists are paginated: with Return All off, the node stops at Limit, and with it on, n8n chains the pages, so a wide market query costs several API calls. And the contract address route offers Ethereum as the issuing platform, so a token on another chain needs the coin identifier instead.
04Does the CoinGecko node react in real time?
No, and not because of a delay. CoinGecko has no trigger node in n8n, so nothing in this integration listens for changes on its own. The workflow needs its own starting point. A Schedule Trigger runs it at a fixed interval, which is what most price checks and daily snapshots use. An n8n Webhook, meaning a URL that another service calls, starts it on demand from outside. The trigger of another app works too: a new row, a new message, a form submission, then the CoinGecko node runs as the next step.
05n8n or Make for CoinGecko?
It depends on three things, and price is only one of them. Make is hosted by Make, with no self-hosting option, and bills by operation, so a workflow that polls prices often has a cost that grows with the schedule. n8n runs on n8n Cloud or on your own server through Docker or npm, which matters when the data or the API key should not leave your infrastructure, and the cost model follows that choice rather than the number of runs. The visual logic differs too: branching, looping and expressions feel different enough that the honest test is to rebuild one real workflow in both.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations