Resources · n8n integration

Marketstack n8n integrationAutomate Marketstack with n8n.

Stock data is worth more inside a workflow than in a browser tab. A Marketstack n8n integration rests on one node: 3 operations spread over 3 resources, end-of-day data, exchanges and tickers. Marketstack has no trigger node, so a Schedule Trigger or a Webhook starts the run.

Try the Marketstack integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

Why build a Marketstack n8n integration?

The Marketstack node connects n8n to the Marketstack stock market API. It groups 3 operations across 3 resources: end-of-day data for one or several tickers, a single exchange looked up by its Market Identifier Code, and a single ticker. Authentication runs through one API key credential, and the workflow itself starts from whatever trigger you already use.

Take a portfolio tracker first. A Schedule Trigger fires after the closing bell, endOfDayData.getAll pulls the day's records for a comma-separated list of symbols, and each row lands in a tab your analysts already open every morning. Google Sheets is the usual destination, though the same branch can end in a database just as well.

Second pattern: the alert. Read the latest end-of-day figures, compare them in a Code or IF node against what the workflow stored yesterday, and only speak up when the gap deserves someone's attention. A message in Slack for the desk, a mail through Gmail for the client who asked to be told. What makes that workflow good is the silence between two alerts.

Third one is reference data. ticker.get and exchange.get each take a single value, one symbol on one side, one Market Identifier Code on the other. That makes them natural validation steps: someone submits an instrument in a form, the workflow asks Marketstack whether it exists before the value reaches a chart in Grafana.

For anything outside these 3 operations, the answer is not a plugin and not a wait. The HTTP Request node calls any endpoint of the Marketstack API and reuses the same credential through n8n's predefined authentication. A credential is the block of secrets you save once in the Credentials menu and every workflow reuses.

On volume: Return All walks the API pages until everything matching your filters is in the workflow, while leaving it off caps the result at Limit. Required fields matter too, an empty Ticker stops the node instead of guessing, which beats a silently empty table. If the platform choice is not settled yet, the n8n review digs into hosting and cost.

Connect

How do you connect Marketstack to n8n?

  1. 01

    Generate your Marketstack API key

    Start in your Marketstack account. The dashboard is where you view and generate API keys, so open it and copy the one n8n will use. Note the plan level the account sits on while you are there, because it decides a switch in the next step. The key never belongs in the workflow itself, it belongs in a credential.

  2. 02

    Create the Marketstack credential in n8n

    In n8n, open the Credentials menu and add a Marketstack credential. Paste the value into API Key, then set Use HTTPS according to the plan: off on the free plan, on for every other plan. A credential is created once and reused by every workflow that talks to Marketstack, so this is a one-time job even if you end up running several of them.

  3. 03

    Run one operation before wiring anything

    Drop a Marketstack node on the canvas and pick the credential from its dropdown list, then choose a resource and an operation. Ticker with a single symbol such as AAPL is the shortest round trip. Execute that node on its own and read what comes back, so a mistake in the credential shows up now instead of inside a scheduled run at night.

Actions

What can the Marketstack node do?

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

Resources × operations matrix
ResourceGetGet Many
End-of-Day Data✓
Exchange✓
Ticker✓

End-of-Day Data

1 operation
01

Get many EoD data

endOfDayData.getAll

What you see in n8n

Notes & use cases

This operation returns end-of-day records for one or several stock symbols, over the date window you define. It is the one that feeds a price series.

Key parameters

  • Ticker: one or multiple comma-separated stock symbols, for example AAPL or AAPL,MSFT, or {{ $json.field }} when the list comes from the previous node.
  • Return All: on, n8n keeps walking the API pages; off, Limit sets the maximum number of results returned.
  • Timeframe Start Date and Timeframe End Date: the bounds of the window, in YYYY-MM-DD or ISO-8601 format.
Use cases
build the history of a watchlist in a sheet, one row per symbol and per date.

Exchange

1 operation
02

Get an exchange

exchange.get

What you see in n8n

Notes & use cases

Point this operation at a single venue and the node asks Marketstack about that exchange, then hands the result to the next step.

Key parameters

  • Exchange: the stock exchange to retrieve, given as a Market Identifier Code such as XNAS, or {{ $json.field }} when the code arrives from an earlier step.
Use cases
before importing a list of instruments received from a data provider, run every venue code through this operation to spot the ones that match nothing.

Ticker

1 operation
03

Get a ticker

ticker.get

What you see in n8n

Notes & use cases

One symbol in, whatever Marketstack holds on that symbol out. Reserve it for the moments when the workflow already knows which company it cares about.

Key parameters

  • Ticker: a single stock symbol, for example AAPL. This field expects one symbol, where end-of-day data accepts a comma-separated list.
Use cases
check the symbols typed into an internal form before they feed a report, and answer with a readable error rather than an empty table.
Need help

Need help automating Marketstack with n8n?

A person reads every message.

FAQ

Marketstack and n8n, the questions that come next

01Is the Marketstack integration free in n8n?
Yes on the n8n side. The Marketstack node ships with n8n, so there is nothing to install and nothing extra to pay for it, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both setups, which means you can prototype in one and move it to the other. What your Marketstack account costs is a separate question, handled on their side, and this page does not cover it. The one thing your plan level does change inside n8n is the Use HTTPS setting in the credential.
02What credentials does the Marketstack node need?
One API key. You view and generate API keys in your Marketstack account dashboard, then paste the value into the API Key field of a Marketstack credential in n8n. The same screen asks you to select whether to Use HTTPS, and the answer depends on the plan level of your Marketstack account: turn it off on the free plan, turn it on for every other plan. Credentials live in their own menu in n8n, separate from workflows, so you create this one once and every Marketstack node you add later simply picks it from a dropdown list.
03What are the limits of the Marketstack n8n integration?
The node covers 3 operations across 3 resources: end-of-day data, exchange and ticker. For any endpoint of the Marketstack API outside that catalog, use the HTTP Request node, which reuses the same credential through n8n's predefined authentication, so you keep one key for the whole workflow. The other thing to watch is volume. End-of-day data returns results page by page: leave Return All on to walk through all of them, or turn it off and let Limit cap the number of items. And a field marked required stops the node when it is empty, rather than running with a guess.
04Does Marketstack trigger an n8n workflow in real time?
There is no Marketstack trigger node in n8n, so nothing on the Marketstack side can start a workflow by itself. You pick the starting point instead. A Schedule Trigger runs the workflow at a fixed interval, which is the natural fit for end-of-day data since the useful moment is after the close. An n8n Webhook, meaning a URL that a third-party service calls, works when another system decides the timing. And the trigger of another tool can open the workflow too, for instance a form submission that then checks a symbol with the ticker operation.
05n8n or Make for Marketstack?
It comes down to four criteria, not to which tool is better. Hosting first: n8n self-hosts with Docker or npm and also exists as n8n Cloud, while Make is hosted only. Data control follows from that, since a self-hosted instance keeps market data and API keys on infrastructure you own. Cost model next: Make bills per operation, which changes how you think about a workflow that loops over many symbols. Visual logic last, the two editors approach branching differently and that is mostly a matter of habit. Both call the Marketstack API, so the API key question is identical.
Same platform

Other docs you might need on this stack.

Browse all integrations