Convert CSV to JSON File Using n8n Binary Data Tools

Overview

This workflow reads a CSV file from the local filesystem, parses it into structured JSON data, and then writes the result as a JSON file. It is a simple, reusable pipeline for converting tabular data (CSV) into a JSON format that can be used by other applications, APIs, or data processing tools. The workflow is triggered manually, making it ideal for on-demand file conversions without needing to write any code.

Nodes and Steps

1. On clicking 'execute' (Manual Trigger) — No auth. This node starts the workflow when you click the "Execute Workflow" button in the n8n editor. It requires no credentials or configuration.

2. Read Binary File — No auth. This node reads a binary file from the local filesystem. The configured parameter filePath is set to /username/n8n_spreadsheet.csv. You must change this path to the actual location of your CSV file on the server where n8n is running.

3. Spreadsheet File1 — No auth. This node parses the binary CSV data into structured JSON. The options parameter is empty, meaning it uses default settings (first row as headers, comma delimiter). The output is an array of JSON objects, one per row.

4. Move Binary Data — No auth. This node converts the JSON data back into a binary format (file). The mode parameter is set to jsonToBinary, which tells n8n to take the incoming JSON and prepare it for writing as a file.

5. Write Binary File — No auth. This node writes the binary data to a file on the local filesystem. The fileName parameter is set to /username/n8n_spreadsheet.json. You should change this to your desired output path and filename.

Setup Instructions

• n8n instance: You need a running n8n instance (self-hosted or cloud).
• File system access: The n8n process must have read/write permissions to the directories specified in the filePath and fileName parameters. On self-hosted instances, ensure the user running n8n can access those paths.
• CSV file: Place your CSV file at the path specified in the Read Binary File node (e.g., /username/n8n_spreadsheet.csv). The CSV should have headers in the first row for best results.
• No external accounts or API keys are required — this workflow works entirely with local files.

Use Cases and Variations

• Data migration: Convert legacy CSV exports to JSON for use in modern APIs or databases.
• Automated reporting: Combine with a Schedule Trigger to run daily, converting a CSV report into JSON for further processing.
• Integration with other nodes: After the Spreadsheet File node, you could add an HTTP Request node to send the JSON data to a webhook or API.
• Different file formats: You can adapt this workflow to convert Excel (.xlsx) files by changing the Spreadsheet File node options (e.g., set sheetName or range).
• Cloud storage: Replace Read Binary File with a node like "Read Binary File from S3" or "Google Drive" to fetch CSV from cloud storage, then write the JSON back to cloud storage.

To adapt, simply change the file paths, add a trigger (e.g., Cron or Webhook), or insert transformation nodes between Spreadsheet File and Move Binary Data.

{
  "nodes": [
    {
      "name": "On clicking 'execute'",
      "type": "n8n-nodes-base.manualTrigger",
      "position": [
        -240,
        180
      ],
      "parameters": {},
      "typeVersion": 1
    },
    {
      "name": "Read Binary File",
      "type": "n8n-nodes-base.readBinaryFile",
      "position": [
        -60,
        180
      ],
      "parameters": {
        "filePath": "/username/n8n_spreadsheet.csv"
      },
      "typeVersion": 1
    },
    {
      "name": "Spreadsheet File1",
      "type": "n8n-nodes-base.spreadsheetFile",
      "position": [
        120,
        180
      ],
      "parameters": {
        "options": {}
      },
      "typeVersion": 1
    },
    {
      "name": "Move Binary Data",
      "type": "n8n-nodes-base.moveBinaryData",
      "position": [
        300,
        180
      ],
      "parameters": {
        "mode": "jsonToBinary",
        "options": {}
      },
      "typeVersion": 1
    },
    {
// ... truncated (copy to see full JSON)