# Manually update JSON config file by key in n8n without database
This workflow enables updating a local JSON configuration file by key-value pairs without relying on external databases. Designed for developers and admins who need lightweight, file-based persistence within n8n.
## Who it´s for
- Developers using n8n for local state storage
- System administrators automating config file management
- Integrators needing a simple key-value store without a database
## What the automation does
- Triggered manually via manual trigger
- Constructs the file path and write parameters
- Reads an existing binary JSON file and parses it into an object
- Updates the specified key with a new value from input data
- Writes the modified object back as binary
- Supports batch processing of multiple updates
## What´s included
- Ready-to-use n8n workflow
- Trigger and handler logic
- Integrations with Local File System
- Basic textual guide for setup and adaptation
## Requirements for setup
- Access to n8n (self-hosted or cloud)
- Read/write permissions to the target directory
- Correct file path configured in the workflow
## Benefits and outcomes
- Simplified config management through n8n
- No dependency on external databases
- Centralized control over settings via one interface
- Remote configuration updates without direct server access
- Reusable operations suitable for larger automation chains
## Important: template only
Important: you are purchasing a ready-made automation workflow template only. Rollout into your infrastructure, connecting specific accounts and services, 1:1 setup help, custom adjustments for non-standard stacks and any consulting support are provided as a separate paid service at an individual rate. To discuss custom work or 1:1 help, contact via chat
No feedback yet