n8n-deploy: Database-First n8n Workflow Management CLI
Overview
n8n-deploy is a Python CLI that remembers your workflow configuration. Built on SQLite, it stores paths, servers, and settings - so deployment commands stay simple.
n8n-deploy wf push my-workflow
The database knows where your workflow lives and which server it belongs to.
Key Features
-
🧠 Smart Configuration
- Stores workflow paths, server links, and SSL settings
- Push/pull by workflow name or ID
- Override anytime with explicit flags
-
🚀 Multi-Server Support
- Push and pull workflows to any n8n server
- Per-server SSL verification settings
- API key management with server linking
-
📦 Batch Operations (NEW in v0.9.0)
- Push or pull multiple workflows in a single command
- Progress indicators and summary tables for batch operations
- Continue processing even if some workflows fail
-
📁 Folder Synchronization (NEW in v0.2.0)
- Bidirectional folder sync between local and n8n server
folderCLI command group for folder operations- Automatic folder mapping and tracking
-
💻 Versatile CLI Interface
- Emoji-rich output for interactive use
- Script-friendly mode with
--no-emojiflag - Verbose logging with
-vand-vvflags at any command level - Comprehensive workflow operations
Installation
# Pip install
pip install n8n-deploy
# Use uv for faster setup and virtual environment
uv venv --python /usr/bin/python3 .venv
source .venv/bin/activate
uv pip install n8n-deploy
Quick Start
# Initialize database
n8n-deploy db init --data-dir ~/.n8n-deploy
# Create server and add API key
n8n-deploy server create production https://n8n.example.com
n8n-deploy apikey add "your-n8n-api-key" --name "prod-key" --server production
# Or via stdin (key not saved in shell history)
# echo "your-n8n-api-key" | n8n-deploy apikey add - --name "prod-key" --server production
# Configure SSL for self-signed certificates (optional)
n8n-deploy server ssl production --skip-verify
# Link workflow to server with flow directory (automatic server resolution)
n8n-deploy wf add workflow.json --flow-dir ./workflows --link-remote production
# Push/pull uses linked server AND stored flow-dir automatically!
n8n-deploy wf push workflow-name # No --flow-dir or --remote needed!
n8n-deploy wf pull workflow-name # Uses stored paths automatically
# Push/pull multiple workflows at once (NEW in v0.9.0)
n8n-deploy wf push wf1 wf2 wf3 --remote production
n8n-deploy wf pull wf1 wf2 wf3 --remote staging
# Update workflow metadata without push/pull
n8n-deploy wf link my-workflow --flow-dir ./new-location
n8n-deploy wf link my-workflow --server staging
# Override with --remote for ad-hoc operations
n8n-deploy wf push workflow-name --remote staging
# Delete workflow from local database
n8n-deploy wf delete workflow-name
# List workflows from server
n8n-deploy wf server --remote production
# Folder synchronization (NEW in v0.2.0)
n8n-deploy folder sync --remote production # Sync folders with server
# Enable verbose logging for debugging
n8n-deploy -v wf push workflow-name # Basic verbose
n8n-deploy -vv wf push workflow-name # Extended verbose
Community & Support
💬 Get Help & Connect:
- Discussions - Ask questions, share ideas, showcase workflows
- Issues - Report bugs or request features
- Documentation - Complete guides and API reference
Discussion Categories:
- 📣 Announcements - Project updates and releases
- 🙏 Q&A - Get help from the community
- 💡 Ideas - Suggest new features
- 🎯 Show and Tell - Share your workflows
- #️⃣ General - Everything else
Configuration
n8n-deploy supports multiple configuration methods:
- CLI Flags
- Environment Variables
.envFiles (in development mode)
Environment Variables
N8N_DEPLOY_FLOWS_DIR: Workflow files directoryN8N_DEPLOY_DATA_DIR: Application data directoryN8N_SERVER_URL: n8n server URL for remote operations
Documentation
Quick Links:
Contributing
We welcome contributions! Please see our Contributing Guide and Code of Conduct.
Quick Links:
License
This project is licensed under the MIT License - see the LICENSE file for details.
Requirements
- Python 3.9+
- n8n server (local or remote)
- Basic understanding of workflow management
Performance Note
Designed for efficient workflow management with minimal overhead. Ideal for DevOps, automation engineers, and workflow enthusiasts.
Metadata
Release files for n8n-deploy 0.9.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| n8n_deploy-0.9.1.tar.gz | 332.2 kB | With provenance | Details for n8n_deploy-0.9.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| n8n_deploy-0.9.1-py3-none-any.whl | Python 3 | none | any | Details for n8n_deploy-0.9.1-py3-none-any.whl |
Total release size: 440.2 kB
Release files / n8n_deploy-0.9.1.tar.gz
| Download URL | n8n_deploy-0.9.1.tar.gz |
|---|---|
| Size | 332.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ada5b8359d20818d64b16e8a5f989f946f91c60522b81705f408b0d1334dc80e
|
|
BLAKE2b-256 checksum How to use checksums |
b889f5a525224add1f11e784b0e21871c5486e4151d18ee7b2e5e7237840c667
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 10, 2026.
Transparency logRelease files / n8n_deploy-0.9.1-py3-none-any.whl
| Download URL | n8n_deploy-0.9.1-py3-none-any.whl |
|---|---|
| Size | 108.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae9859f0170083b30fd94564c5e87b8e3079d168b8282162c0e96095b76c54ec
|
|
BLAKE2b-256 checksum How to use checksums |
aeb6bedaf3576138e21c40cd370269fd63218ab686b89cb1dd54ab787f19cf80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 10, 2026.
Transparency logSecurity for n8n-deploy 0.9.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for n8n_deploy-0.9.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.