SHIPPED WORK2026
n8n AI Workflow Generator
Describe the workflow in plain language, get a ready-to-import n8n JSON · all nodes wired, credentials slotted, test data included.
A Chainlit-based chat UI where you describe your workflow ('when a new lead lands in Typeform, send a Slack message and log to Notion'), the AI produces real n8n JSON with the right nodes, credential slots, and test data. Import-ready. Trained on many templates with fastembed vector search to find the closest-matching pattern.
THE PROBLEM
- -n8n is huge · browsing the node catalogue takes hours
- -The template gallery is limited · rarely fits your exact case
- -Building a custom workflow is just node-parameter wrangling
- -ChatGPT-generated JSON rarely imports cleanly
WHAT THE CLIENT GOT
- Workflow idea → running n8n flow in 2 minutes
- Non-technical PM can mock valid n8n JSON
- Example-driven · modernise legacy workflows fast
- Chat-based iteration · refine as you go
WHAT WE DELIVERED
- +Natural-language input · Hungarian and English both supported
- +Export · ready-to-import n8n JSON
- +FastEmbed vector template search · starts from the closest match
- +Chainlit chat UI · iterate in a conversation
- +Local aiosqlite · conversation and template history stay on your machine
STACK
- Python
- TypeScript
- Greenlet
- FastEmbed
- aiosqlite
- Chainlit
RELATED READING
- AI solutions · Website & online shoppgvector at 10M+ rows · index choice, query patterns, real performance numberspgvector at 10M rows is not scary · if you pick the right index. HNSW vs IVFFlat, filter patterns, real numbers.
- AI solutionsLLM prompt caching in production · a 60-80% cost cutPrompt caching is the single biggest LLM cost lever in 2026. 4 patterns, real savings numbers, 2 gotchas worth knowing.
- AI solutions · CybersecurityAgentic AI · the safe tool-use pattern we ship by defaultAgentic AI that can send email and move money is not just a chatbot. Here's the safe tool-use pattern we ship.
- AI solutionsLLM evals-as-code · the CI gate we run on every RAG deployAn eval that's not in CI is not an eval. Here's the evals-as-code workflow we run on every RAG project.