n8n Launches n8n Assistant to Plan, Build, and Troubleshoot Workflows

n8n Launches n8n Assistant to Plan, Build, and Troubleshoot Workflows n8n has introduced n8n Assistant, an AI tool that translates plain-language automation requests into standard, editable n8n workflows while assisting with credential requests, execution testing, and debugging. Users describe intended automation outcomes in plain language, and n8n Assistant plans, builds, tests, and iterates on fixes on the existing canvas. Generated workflows are standard n8n workflows that can be edited by hand, logged, and maintained without relying on original prompts. n8n Assistant replaces the earlier AI Workflow Builder by actively running workflows and debugging issues rather than stopping after generation. The tool draws on plan AI credit allocations—with more debug iterations consuming more credits—and is currently available behind a preview flag. Interactive Workflow Generation n8n Assistant is designed to solve the translation gap between knowing what to automate and understanding the exact nodes, configurations, and connections required. Users describe their intended outcome, and the tool builds the node graph directly on the standard canvas, prompts for required credentials, tests the run, identifies broken steps, and iterates on fixes with the user. Standard Canvas and Team Maintainability Unlike tools that lock logic into opaque prompts or separate surfaces, n8n Assistant produces standard n8n workflows with normal execution logs and manual editing capabilities. Team members who were not involved in the initial prompt can inspect nodes and update routing rules directly on the canvas. Credits, Replacement of Prior Builder, and Preview Status Superseding the previous AI Workflow Builder, n8n Assistant actively runs and refines workflows instead of stopping at one-time generation. Usage draws from plan-based AI credit allocations, with multi-round debugging consuming more credits than workflows succeeding on the first run. The feature currently ships under a preview flag while remaining in active development.

n8n 推出 n8n Assistant：支持自然语言规划、自动构建与错误调试的工作流助手 自动化平台 n8n 宣布推出 n8n Assistant，旨在解决用户用自然语言描述需求与在画布上具体选定、配置节点之间的断层。该工具可根据自然语言描述自动在画布上规划、搭建工作流，并协助运行排错与迭代。 用户使用自然语言描述预期结果，n8n Assistant 负责规划、在画布上生成标准节点图并索取凭据。 助手支持运行测试、识别报错并与用户协同修复，最终交付标准且可手动维护的工作流。 n8n Assistant 取代了原有的单次生成工具 AI Workflow Builder，并消耗方案中的 AI 额度。 该功能目前处于预览（preview）阶段并保持活跃开发，未来几周将增加额度充值方式。 闭环的工作流生成与调试 针对以往自动化在节点选择、排序和初始报错排查中容易卡壳的问题，n8n Assistant 支持由用户直接描述目标结果。助手会自动在画布上搭建对应节点、在需要时请求 CRM 等服务的凭据，并运行测试排查错误（例如处理富化步骤返回空数组的边界情况），经过迭代调试后交付可以直接运行的标准工作流。 标准资产与团队维护 n8n Assistant 生成的结果不是孤立的黑盒，而是与手工构建完全一致的标准 n8n 工作流。工作流完全可视化、记录每次运行日志，并归团队所有。后续规则发生变动时，其他成员无需知晓最初的提示词，直接在画布上修改节点即可继续维护。 计费规则与开发阶段 n8n Assistant 取代了此前仅支持一次性生成的 AI Workflow Builder。新助手会消耗套餐内的 AI 额度，需要多轮调试的任务会消耗更多额度，官方计划在未来几周上线额度充值渠道。目前该助手在预览标记（preview flag）下提供，整体仍处于活跃迭代中。

If you've built anything in n8n, you know the gap: you can describe what you want to automate in a sentence, but that's not the same as knowing which nodes to use, in what order, configured how, and connected to which accounts. And when the first execution fails with an error you haven't seen before, you're back in the docs and the forum. That translation step is where most automation projects stall. Not because the platform can't do it, but because working out how takes an afternoon you didn't plan to spend. With n8n Assistant, you describe the automation you want in plain language and it plans the workflow, builds it on your canvas, asks for the credentials it needs, runs it, works out what broke, and iterates on the fix with you. What you get at the end is an standard n8n workflow: visible on the canvas, editable by hand, logged on every run, and owned by your team rather than by whoever wrote the prompt. You'll get something working in a few minutes, then you tighten it: swap a node, adjust a filter, add error handling, decide what needs a confirmation step. If you'd rather assemble it yourself, nothing stops you. It's the same canvas, and the workflows are the same workflows. There's no shortage of AI tools that'll produce an automation from a sentence, and several of them are fairly good at it. But problems show up later, when a team has to depend on the result: So the question isn't whether you can generate an automation. It's whether it still runs next month, whether you can see what it did, and whether a colleague can pick it up. You start by describing the outcome you want rather than the steps to get there: None of this happens in a separate product surface. The workflow n8n Assistant builds is the workflow you would have built by hand, in the same project, with the same nodes and the same execution history. Here's a typical example. Someone wants inbound form submissions triaged: enrich the company, check whether they're already a customer, then either route to sales or send a templated reply. They know all of that as a sentence and none of it as a node graph. n8n Assistant plans it, builds it, asks for the CRM credential when it reaches the node that needs one, runs it against a test submission, and finds that the enrichment step returns an empty array for sole traders. It fixes that, runs it again, and hands over a workflow with eight nodes and a clean execution. A week later the routing rules change. Someone who wasn't involved opens the workflow, reads it, and edits a node. They don't need to know what anyone typed to get it built. Generating the workflow is only the first step. What you get after that: n8n Assistant draws on your plan's AI credit allocation. Existing users keep the allocation they already have, and usage is counted separately from the previous AI workflow builder, so nothing you spend here changes what you had before. A build that needs several rounds of debugging costs more than one that lands first time. Credits are allocated per plan, and we will be adding ways to top these up in the coming weeks. Please note that n8n Assistant still ships behind a preview flag. That isn't a limit on who can use it: it's in active development with more features coming soon. Some things aren't here yet, but we're working on for the future: Also, n8n Assistant supersedes the **AI Workflow Builder**. Where the old builder generated a workflow once and stopped, n8n Assistant builds it, runs it, and finds improvements. Open n8n Assistant in your instance and describe an automation you've been putting off. Something real, with a couple of integrations and at least one step that could plausibly go wrong. Here are some ideas to get started with: Check out the n8n Assistant documentation here: [https://docs.n8n.io/build/ways-of-building-workflows/n8n-assistant](https://docs.n8n.io/build/ways-of-building-workflows/n8n-assistant) While n8n Assistant is behind the preview flag, the most useful feedback is the specific kind: what you asked for, what it built, and where it fell down. We're reading the [community forum](https://community.n8n.io/) closely. We can't wait to see what you build with it.