I indexed 8,000+ n8n workflows, then realized "Search" was broken. Here is how I fixed it.

Question

The "Data Dump" Problem

Last week, the n8n community saw a massive release of 8,000+ raw workflow JSON files. As a developer, my first instinct was pure excitement: "More data = Better, right?"

I immediately indexed them all into my search engine, n8nworkflows.world.

But as I watched the analytics, I noticed a weird pattern. New users would land on the site, stare at the search bar, and... leave.

The "Blank Canvas" Paralysis

I realized that having 8,000 options isn't a feature; it's a bug.

Power users know to search for specific nodes like "HTTP Request" or "Postgres Trigger." But beginners? They don't think in nodes. They think in Job Titles and Goals.

• A Marketer doesn't want "Gmail API"; they want "Cold Outreach Automation."
• A Founder doesn't want "Stripe Webhook"; they want "SaaS Churn Alert."

The raw database was technically "complete," but functionally "useless" for the people who needed it most.

The Solution: Context > Code

I decided to stop just "indexing" files and start "curating" experiences. This weekend, I shipped a major update: The "Who Am I?" Wizard.

Instead of forcing users to guess keywords, I reversed the flow:

1. Select your Role: (e.g., Marketer, Founder, Developer, HR).
2. Get Curated Paths: The engine filters out 90% of the noise and shows only the automations relevant to that persona.

How I Built It (The Tech Stack)

• Frontend: Next.js 14 (App Router) for the dynamic filtering UI.
• Backend: Supabase. I had to restructure my DB schema to support the new metadata.

Old Schema: 
workflow_id -> nodes

New Schema: 
workflow_id -> nodes + target_roles[] + complexity_score

The "Verified" Logic

I also added a "Community Verified" layer. We run a check against the JSON structure to ensure it doesn't contain deprecated nodes (v0.x) that would break in the current n8n version.

The Result

The bounce rate on the search page has already dropped. Users are clicking "Marketer" and instantly finding the Notion-to-LinkedIn generator they didn't even know how to ask for.

If you are building a tool for developers, remember: Don't just give them a database. Give them a map.

---

Try it out here: n8nworkflows.world
(Feedback on the "Role" accuracy is highly appreciated!)