reversa-n8n

To convert an n8n workflow export into design documents, you generate language-agnostic SDD specifications from the workflow JSON. The process parses and validates required JSON fields, reconstructing the end-to-end directed graph to produce workflow-overview.md, requirements.md, and design.md artifacts for reimplementation.

Documenting n8n triggers, credentials, and nodes for Python reimplementation involves mapping node types, credential structures, and orchestration patterns into structured System Design Documents. This approach captures the control-flow logic, including branches, merges, and loops, without exposing actual credential secrets.

Yes, you can generate system design documents from multiple n8n workflow JSON files at once. The process applies when you have one or more workflow JSON files, parsing each to document triggers, nodes, and external dependencies, and then organizing the generated artifacts into dedicated output directories.

To start translating an n8n workflow JSON file into reimplementation-ready specs, place your exported workflow JSON into the designated input folder. Running the translation validates the required JSON fields and reconstructs the flow graph, automatically generating workflow-overview.md, requirements.md, and design.md under a specific output directory.

Yes, n8n workflow translation captures complex control-flow structures like sub-workflows and loops. The graph and semantics reconstruction process starts from triggers and explicitly builds the directed flow graph, including iterations, branches, merges, and sub-workflows, to ensure the logic is fully documented for reimplementation.

When preparing n8n specs for a downstream pipeline, the process initializes .reversa/state.json and .reversa/plan.md. These files are generated alongside the System Design Documents to track the translation state and plan the subsequent reimplementation steps for the downstream Reversa pipeline.