n8n-ops

Manage n8n workflows on a Hostinger VPS via docker exec import, export, and backup operations.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill n8n-ops-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: n8n-ops
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/n8n-ops
Command: npx skills add https://github.com/tkogut/agents-os-core --skill n8n-ops-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Managing n8n workflows on a remote VPS requires repetitive SSH, docker cp, and docker exec commands that are error-prone, especially when juggling multiple isolated n8n instances behind Traefik. This Skill standardizes and automates those operations. ## Core Features & Use Cases - Automated CLI Helper: The n8n_helper.py script lists instance status, imports local workflow JSON files, exports workflows by ID, and backs up all workflows from an instance in one command. - Multi-Instance Isolation: Documents the architecture for running separate n8n containers (g7tq, pkogut) with Traefik routing and provides a docker-compose template for new instances. - Error Recovery Guide: Includes a lookup table for common n8n CLI failures such as missing --input flags, ENOENT file path errors, and SQLite NOT NULL constraint violations. - Use Case: You built a workflow JSON locally and need it live on the pkogut instance. Run the import command and the script validates the JSON, adds a temporary ID if missing, transfers the file, imports it into the container, and cleans up. ## Quick Start Ask the agent to import your local workflow JSON file into the g7tq n8n instance using the n8n-ops helper script.

Frequently Asked Questions about n8n-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import an n8n workflow JSON into a Docker container on a VPS?▼

Run python3 scripts/n8n_helper.py import --instance g7tq --file workflow.json. The script validates the JSON, adds a temporary id if missing, copies the file via scp and docker cp, runs n8n import:workflow inside the container, and cleans up temporary files.

How to back up all n8n workflows from a remote server?▼

Use the backup command: python3 scripts/n8n_helper.py backup --instance g7tq --dir ./n8n_backups. It runs n8n export:workflow --all inside the container and saves each workflow as a separate JSON file named by id and workflow name.

Why does n8n import fail with SQLITE_CONSTRAINT NOT NULL workflow_entity.id?▼

This error occurs when the workflow JSON lacks a root-level id field. Add an alphanumeric id such as "id": "TEST123456789ABC" to the JSON root, or let the helper script auto-generate a temporary id during import.

Can multiple users share one n8n instance on the free tier?▼

No, n8n free tier allows only one user per instance. To support multiple users, deploy separate isolated instances using the provided docker-compose template with unique container names, volumes, and Traefik host rules.

What causes ENOENT no such file or directory during n8n import?▼

The file exists on the VPS host but not inside the container. You must run docker cp to copy the JSON into the container before executing n8n import:workflow with docker exec.