AI-built workflows stay unpublished until users test
Users can now test n8n AI-built workflows before deciding whether to publish them — the builder no longer forces auto-publishing at completion.
The AI builder was auto-publishing workflows as soon as they were submitted, leaving users without a chance to test first. When errors or misconfigurations appeared, users had no recourse. Now the builder's job ends at successful submission — setup runs only when needed (missing credentials, unconfigured triggers), users are prompted to test, and publishing becomes an explicit choice made after verification. This gives users control over when their workflows go live and ensures they catch problems before deployment. The change spans the AI orchestration layer in the n8n instance-ai package, affecting how the builder agent and detached background tasks interpret completion criteria.
View Original GitHub Description
Summary
- Restructures the post-build flow in the system prompt as clear numbered steps: build → setup (if needed) → test → publish (only when user asks)
setup-workflowis only called when there's actually something to configure (mocked credentials, missing parameters, unconfigured triggers)- Removes auto-publish from the builder agent prompt — the builder's job ends at a successful submit
- Publishing is always the user's explicit decision after they've had a chance to test
Related
https://www.notion.so/n8n/InstanceAI-asks-me-to-publish-before-i-get-a-chance-to-test-and-there-is-no-other-option-33b5b6e0c94f80c7b3aed05cdb5d226f https://www.notion.so/n8n/Instance-AI-issues-reported-3285b6e0c94f802ca27cd2d2e067c5d7?p=33c5b6e0c94f8008abaac1b534b1b54a&pm=s