Planner now routes data-table operations correctly
The AI planner no longer wraps standalone data-table operations in unnecessary workflows. Creating, deleting, or modifying tables routes directly to the data-table agent.
The AI planner had a workflow bias problem. When users asked to create a table or delete some rows, the system would attempt to wrap these operations in workflow items, falling back to a generic delegate with incomplete tools. This routing error caused failures and unnecessary complexity.
Data-table operations now route correctly. Standalone table creation, deletion, modification, and seeding work without requiring automation triggers, schedules, or workflow scaffolding. The planner recognizes when a request is purely about table CRUD and emits only data-table kind items.
When replanning after failures, the orchestrator handles single remaining tasks directly instead of always spawning a new plan. If only one simple task remains—such as a data table operation or credential setup—it executes directly with the appropriate tool.
View Original GitHub Description
Summary
- Planner now uses data-table kind for all table operations (create, delete, modify) instead of falling back to delegate with incomplete tools
- Made blueprint data-table columns optional to support non-creation operations
- Updated accumulator to derive task title/spec from purpose when columns absent
- Added scope boundary to data-table agent to prevent cross-task side effects
- Orchestrator now handles single remaining tasks directly on replan instead of always creating a new plan via create-tasks
- Added standalone data-table operations section to best-practices guide
Related Linear tickets, Github issues, and Community forum posts
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->Review / Merge checklist
- I have seen this code, I have run this code, and I take responsibility for this code.
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)