Taming 12,000 Workflows: How n8n Runs on n8n

Our internal estate grew to roughly 12,000 workflows — powering everything from sales pipelines to all-hands meetings — built by an enthusiastic company of builders over several years. Then we looked closer: workflows whose builders had left the company and whose functions nobody could explain, a shared credential that silently broke automations across multiple teams for a week before anyone noticed, documentation that lived only in the head of someone no longer on payroll.

Sound familiar? Every organization that succeeds with n8n eventually meets this problem — sprawl is what success looks like before governance catches up. This is the honest story of how n8n's internal automation team is bringing its own estate under control retroactively, without freezing the builder culture that created the value in the first place.

We'll cover the machinery we built: a classification standard for business-critical workflows, a cleanup process with a grace period for owners to claim their work, and an n8n workflow that documents other n8n workflows — pulling a workflow's JSON, sending it to an LLM, and producing a first-draft documentation page for a human to review.

We'll also share the ownership principle the mess taught us: the owner of an automation should be the owner of the process it automates — not the person who built it.