Block 1 - Write Binary File
- Type / Role
- n8n-nodes-base.writeBinaryFile - writeBinaryFile
- Config choices
- Version 1
Write JSON to disk (binary)
Workflow preview
100%
$20/month : Unlimited workflows
2500 executions/month
THE #1 IN WEB SCRAPING
Scrape any website without limits
HOSTINGER 
Early Deal
DISCOUNT 20% Try free
Early DealDISCOUNT 20%
Self-hosted n8n
Unlimited workflows - from $4.99/mo
#1 hub for scraping, AI & automation
6000+ actors - $5 credits/mo
Important notice
This workflow is provided as-is. Please review and test before using in production.
1. Workflow Overview
The “Write Binary File” expects binary data. The JSON data is, however, JSON ;) There should really be a node that allows moving data around between both of them. For now, it can be done with a Fun...
Best for
- File Management automation workflows
- beginner n8n builders looking for reusable templates
Tools used
n8n-nodes-base.writebinaryfile, n8n-nodes-base.function
Source and attribution
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by mike.
Original n8n.io source1.1 Workflow description
- Title
- Write JSON to disk (binary)
- Workflow name
- Write JSON to disk (binary)
The “Write Binary File” expects binary data. The JSON data is, however, JSON ;) There should really be a node that allows moving data around between both of them. For now, it can be done with a Function-Node. At least till a proper one is in place. The first node is example data, wich you can customize or replace. The second node named “Make Binary” is the important one with the custom code which makes the data binary and writes it to the correct location.
1.2 Logical Blocks
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
2. Block-by-Block Analysis
Block 2 - Make Binary
- Type / Role
- n8n-nodes-base.function - function
- Config choices
- Version 1
Block 3 - Create Example Data
- Type / Role
- n8n-nodes-base.function - function
- Config choices
- Version 1
3. Summary Table
| Workflow | Write JSON to disk (binary) |
|---|---|
| Complexity | beginner |
| Nodes | 3 |
| Categories | File Management |
| Author | mike |
| Published | 11 Oct 2019 |
4. Reproducing the Workflow from Scratch
-
1. Download the workflow JSON
Use the JSON export at /data/workflows/101/101.json as the source template for this automation.
-
2. Import the template into n8n
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
-
3. Configure credentials and variables
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
-
4. Test with sample data
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
-
5. Activate and monitor
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
5. General Notes & Resources
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Frequently asked questions
What does Write JSON to disk (binary) do?
The “Write Binary File” expects binary data. The JSON data is, however, JSON ;) There should really be a node that allows moving data around between both of them. For now, it can be done with a Fun...
What do I need before importing this workflow?
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Can I customize this workflow?
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.