FlowFactory
An experiment in describing n8n workflows in natural language.
A TypeScript experiment: describe an automation in natural language, with multi-agent generation, validation and one-click deploy as the goal.
- Role
- Creator
- Stack
- TypeScript
Context
FlowFactory is a lab: describe an automation in natural language, with a validated, deployable n8n workflow as the goal.
The repository describes multi-agent generation, validation and one-click deploy as the project's goal.
Constraints
- The intended output is a valid n8n workflow, not pseudo-code.
- Generation had to remain verifiable before any import.
- The project remains an experiment, with no promise of a finished product.
Decisions
Several agents, one output
Generation is split into specialised steps, then recomposed into a single workflow.
Trade-offQuality improves with role separation, but cost and latency do too.
Validate before importing
The generated JSON goes through a validation step before import into n8n. One-click deploy remains the goal described in the repository.
Trade-offOne-click deploy depends on a prior step that can reject an incomplete generation.
Stay a lab
FlowFactory is a TypeScript experiment, not a promise of a finished product.
Trade-offThe scope stays deliberately narrow, which limits use but keeps the project honest.
Method
Specify
The output contract is a valid n8n workflow, not pseudo-code; validation is planned before generation.
Orchestrate
Generation is split between specialised agents, then recomposed into a single workflow.
Verify
The JSON goes through a validation step before any import, and one-click deploy remains the goal.
Architecture
Input
- Natural-language description
Generation
- Specialised agents
- JSON validation
Output
- Workflow n8n
- One-click deploy (goal)
One description, one validated n8n workflow, one deployment path.
Project status
- The public repository and the TypeScript code.
- A multi-agent generation path described in the repository.
- Validation and one-click deploy as goals, not as delivered features.
What I would do differently
I would push validation further on connections between nodes, not only on JSON shape.