reversa-n8n

Convert exported N8N workflow JSON into specification documents for reimplementation.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-n8n-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-n8n
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-n8n
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-n8n-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents legacy N8N automations from remaining trapped inside opaque workflows by converting exported N8N JSON into clear, traceable specification artifacts that AI coding agents can safely use.

Core Features & Use Cases

  • Workflow-to-SDD translation: Converts an N8N workflow JSON (nodes, connections, settings) into SDD files (workflow overview, requirements, and design) that are independent of N8N.
  • Python reimplementation preparation: Produces an implementation-oriented spec suitable for porting to Python or another language without losing the operational structure of the original workflow.
  • Guardrailed validation & handoff: Validates input JSON structure, detects triggers/flow branches, lists credentials/secrets by type only, and initializes .reversa/state.json and .reversa/plan.md for the broader Reversa pipeline.

Quick Start

Place your exported N8N workflow JSON into the folder n8n_json_workflows/ and then ask the agent to run reversa-n8n to generate the SDD spec for that workflow.

Frequently Asked Questions about reversa-n8n

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

FAQPage Schema
How do I convert an exported n8n workflow JSON into a specification document?

To convert n8n workflow JSON into a specification document, you place the exported file into the n8n_json_workflows folder. The tool then parses triggers, validates the node graph, and generates SDD artifacts detailing the workflow overview, requirements, and design.

Can I port legacy n8n automation logic to Python without losing the workflow structure?

Yes, you can port legacy n8n automation logic to Python by translating the exported JSON into an implementation-oriented SDD spec. This specification preserves the operational structure of the original workflow, making it ready for Python reimplementation.

Does reversa-n8n expose or migrate credentials stored in my n8n workflow exports?

No, reversa-n8n does not expose or migrate credentials from n8n workflow exports. It performs guardrailed validation by detecting and listing secrets by type only, ensuring sensitive data remains secure while initializing the handoff state.

What is the best way to prepare n8n workflows for AI coding agents to reimplement?

The best way to prepare n8n workflows for AI coding agents is generating traceable SDD specification contracts. Converting the exported JSON into operational design artifacts provides the clear, independent documentation agents need for safe reimplementation.

What happens if my n8n workflow JSON is missing minimum required fields during validation?

During validation, if the n8n workflow JSON is missing minimum required fields, the conversion process relies on structural checks to parse the node graph. The tool validates input JSON structure to ensure accurate generation of workflow-overview and design artifacts.

When do I need to generate a Reversa handoff state from an n8n workflow?

You need to generate a Reversa handoff state from an n8n workflow when transitioning legacy automation into traceable contracts for reimplementation. This initializes the .reversa/state.json and .reversa/plan.md files required for the broader Python migration pipeline.