The core message of the provided transcript is that n8n’s value proposition shifted from visual automation toward AI-enabled orchestration while keeping the same underlying goal: helping people build useful, business-critical workflows without depending entirely on specialist developers. The session opens by positioning Jan Oberhauser as a major builder in the current AI wave and describing n8n’s growth from its 2019 origins into a company with more than 1.8 million monthly active users. The introduction also notes a recent SAP investment, though the valuation wording in the transcript is garbled. Ben Fletcher of Accel then frames the conversation around what n8n is today and how it evolved from its original form.

Jan explains that n8n did not begin as an AI company. It started as an automation tool for both private and professional use cases, before AI became part of the product direction. As AI emerged, the team saw that agent-building and orchestration fit naturally into n8n’s existing workflow model. Jan emphasizes that the product’s usefulness came not only from enabling automation, but from making agents and workflows understandable behind the scenes. This visibility matters especially as users move from personal automations into organizational and business-critical processes, including use cases across small teams, Fortune 500 companies, and government organizations.

The discussion then turns to the original pain that led Jan to build n8n. While working in visual effects, he repeatedly wrote Python scripts to make other people’s work more efficient. The harder problem was not writing code; it was the disconnect between the people who understood the problem and the people able to implement a solution. Jan argues that the people experiencing a problem are often best placed to solve it because they understand how it should work, how much effort is worth investing, and how processes change over time. That led him to a node-based, LEGO-like system where reusable blocks could send Slack messages, emails, move data, or create leads.

Ben then compares n8n with earlier promises around connecting systems, including RPA, ETL, and MuleSoft-style integration. Jan’s answer is that n8n originally stood out by prioritizing power and flexibility, avoiding tools that helped quickly but broke down before production-grade use. AI changed the equation further because systems can now make decisions and lower the barrier for non-technical users. Jan says n8n’s AI assistant lets users describe what they want built, then generates it while keeping the workflow visible and auditable.