n8n-live-workflows

Enforce placeholder-LIVE consistency for n8n workflow JSON pairs.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/eyecrackcodes/ROLI --skill n8n-live-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-live-workflows
Source: https://github.com/eyecrackcodes/ROLI/tree/main/.cursor/skills/n8n-live-workflows
Command: npx skills add https://github.com/eyecrackcodes/ROLI --skill n8n-live-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining consistency between placeholder workflow templates and their LIVE equivalents in the /n8n directory to prevent drift and misconfiguration during development and deployment.

Core Features & Use Cases

  • Pair maintenance: Keep both <workflow>.json and <workflow>-LIVE.json synchronized whenever a workflow changes.
  • Safe deployment guidance: Ensure LIVE files remain gitignored and are not committed, avoiding credential leakage.
  • Operational guidance: Provide a clear workflow for updating, testing, and deploying n8n flows without breaking existing setups.

Quick Start

Edit the placeholder <workflow>.json and mirror all changes to the corresponding -LIVE.json to keep both files synchronized.

Frequently Asked Questions about n8n-live-workflows

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

FAQPage Schema
How do I keep n8n workflow JSON pairs synchronized during development?

To keep n8n workflow JSON pairs synchronized, edit the placeholder <workflow>.json and mirror all changes to the corresponding -LIVE.json file to prevent configuration drift.

What is the placeholder-LIVE convention for n8n workflows?

The placeholder-LIVE convention maintains a paired template and LIVE equivalent for n8n workflows in the /n8n directory, ensuring updates apply to both files to guard against drift.

How do I prevent credential leakage when deploying n8n LIVE workflows?

Prevent credential leakage when deploying n8n LIVE workflows by keeping LIVE files gitignored and uncommitted, ensuring sensitive data stays local while placeholder templates track in version control.

Do I need external services to manage n8n workflow version control?

No external services are needed to manage n8n workflow version control; the process relies entirely on repository conventions, gitignore rules, and clear edit-mirroring workflows.

What is the best way to safely import updated n8n workflows?

The best way to safely import updated n8n workflows is to follow operational guidance for updating, testing, and deploying flows by mirroring changes across placeholder and LIVE files without breaking existing setups.

Why does my n8n LIVE configuration drift from the template?

n8n LIVE configuration drifts from the template when edits to the placeholder <workflow>.json are not mirrored to the corresponding -LIVE.json, breaking the synchronization required by repository conventions.