System №05 · 2024

case study — shipped

HatAssembly

Describe a workflow in plain English — get deployable n8n JSON back.

n8n · Supabase pgvector · OpenAI · Claude⬈ source on github

00 brief

Building n8n workflows by hand means knowing hundreds of node schemas. LLMs hallucinate node configs unless they are grounded in the real schema.

built for — Internal tooling — accelerating every client build.

Ground the model in 794 real schemas and it stops guessing.

01 the system

step 01

Three agents, one artifact

A natural-language enhancer sharpens the brief, the retriever pulls exact node schemas from pgvector, and the builder (Claude + Gemini) assembles JSON that validates against the real schema before it ships.

02 the hard parts

incident report · 01

Hallucinated node configs

Unassisted LLMs invent plausible-looking n8n node parameters that fail on import.

resolutionIndexed all 794 node schemas into Supabase pgvector with OpenAI embeddings; the builder only sees retrieved, real schemas, and output is validated before delivery.

03 results

Production-ready n8n workflow JSON from natural language.

794 node schemas indexed and retrievable by semantic search.

04 stack & ops

  • Supabase pgvector + OpenAI embeddings
  • Claude + Gemini dual-model builder
  • Schema validation gate

next system

Sorcer AI