How to Import JSON File in n8n Easily 2026

How you bring a file into n8n depends entirely on where it lives. If it's hosted somewhere reachable over HTTP, an HTTP Request node fetching that URL will pull it in as binary data automatically.

If it's already sitting on disk in a self-hosted n8n setup, a Read/Write File node can load it directly. If it's arriving as part of an upload — through a webhook or a form trigger — the binary data is typically already attached to the incoming item, and you just need to reference the right property name rather than fetch anything yourself.

Whichever route you used, check the item's Binary tab in the node's output before doing anything else. n8n stores incoming files under a binary property — often named data by default, though HTTP Request and other nodes let you rename it. If you can't see a populated binary property here, nothing downstream will work, so this is worth confirming before you add a parsing node on top of a fetch that silently failed.

Extract From File is the node built specifically to turn binary file content into structured data — it isn't limited to JSON, but JSON is one of its explicit operation modes, alongside CSV, XML, and a handful of other formats. Place it right after whatever node produced your binary data, since it needs that binary property as its input.

Inside Extract From File, set the operation to the JSON option, then double-check the Binary Property field matches whatever your file actually landed under — this is the single most common misconfiguration, since a mismatched property name produces an error that looks like a parsing failure but is really just the node looking in the wrong place. Once that's aligned, the node reads the raw bytes and outputs them as a normal n8n JSON item, with the original file structure now available as regular fields rather than an opaque binary blob.

After running the node, check its output panel — a successfully parsed JSON file appears as structured keys and values just like the output of any other node, which means you can click into individual fields the same way you would with data from an API call. If the source file was an array of objects, expect one n8n item per array entry rather than a single item containing the whole array, since that's how n8n typically expands list-shaped JSON.

If Extract From File throws an error, the two most likely causes are a wrong binary property reference or a file that isn't actually valid JSON despite the extension — a truncated download or a file that's secretly HTML (like an error page returned instead of the real file) will both fail here. Open the raw binary preview if you're unsure, or add a temporary node before Extract From File to inspect exactly what bytes arrived, rather than assuming the parser itself is broken.

Once the output looks right, connect Extract From File to whatever comes next — a database node to store it, an IF or Switch node to route based on its contents, or another API call built from its fields. From this point on, the data behaves like any other n8n item, so nothing about the rest of the workflow needs to know it originally came from a JSON file rather than a live API response.