Data table mutations now show preview artifacts
Data table mutation tools now return table metadata so the frontend can display the preview panel after insert, update, or delete operations.
The preview panel was opening empty after the AI agent completed data table mutations. Insert, update, and delete operations would execute successfully, but users saw nothing—no artifact, no clickable link, no confirmation their changes landed.
The fix adds three metadata fields to mutation tool responses: the table ID, table name, and project ID. The frontend resource registry uses these to locate and display the correct artifact after mutations complete. Three tools were updated: insert rows, update rows, and delete rows. Each now returns the same structured metadata, and the frontend extraction logic handles these mutation results by registering or updating the data table in the resource registry.
This is part of a larger effort to unify how the AI agent surfaces results across different tool types, ensuring users always see feedback after running operations.
View Original GitHub Description
Summary
Data table mutation tools (insert/update/delete rows) now return dataTableId, tableName, and projectId in their results so the frontend resource registry can create a proper artifact tab. Without this, the preview panel opened empty after the data-table agent completed mutation tasks, or it would not update.
Including the name also makes the clickable link to be shown rather than just ID / textual name without the link component.
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/[TICKET-ID] --> <!-- 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)