Gitpulse
Merged
Size
L
Change Breakdown
Feature70%
Bug Fix20%
Maintenance10%
#28494feat(editor): Improve agent builder UX with integrations, one-shot build, and config sync (no-changelog)

Agent builder UX revamped with one-shot builds and Slack integration

Agent builder UX revamped with one-shot builds and Slack integration
DE
DeveloperTheExplorer
·Apr 14, 2026

The agent builder now generates a fully configured agent from a single description, Slack integrations get credential management and manifest JSON, and agent names persist reliably across saves and page refreshes.

Building agents in n8n just got less tedious. The agent builder UI now responds to an initial description by firing a one-shot build request to the server, spinning up a Code section in the settings sidebar while the agent configures itself. Previously, users had to navigate chat threads to test their agent—the new flow separates building from testing, with a dedicated test tab handling subsequent conversations.

Slack integration setup is now a first-class experience. The Triggers section in the agent settings sidebar presents a Slack credential panel with inline buttons to create or edit credentials. When connection fails, an error message appears directly in the panel. After a successful connection, users can copy a Slack App Manifest JSON or view it in a modal—the manifest includes the agent name, webhook URL, and required OAuth scopes.

Agent metadata like name and description now persists correctly. A backend fix ensures that when an agent's name or description is updated, the change syncs to both the entity column and the JSON schema stored in the agent record. Previously, a subsequent config save would overwrite the name with the stale schema value. The frontend also keeps its local copy of the config name in sync after updates.

In the frontend editor package, test and builder tab switching is now more predictable—the chat panel defaults to the test tab regardless of whether the agent is in inline mode. Build requests are abortable, so starting a new build cancels any in-flight one, and callbacks that fire after an agent change are ignored to prevent race conditions.

These changes live in the n8n frontend editor and CLI packages, building on a recent n8n-agents merge and addressing tickets AGENT-1 and AGENT-16.

View Original GitHub Description

Summary

Improves the agent builder UI/UX with several fixes and features built on top of the n8n-agents merge:

  • Integrations panel: Restored Slack integration panel inside the Settings sidebar (Triggers section). Added credential create/edit buttons using existing uiStore.openNewCredential/openExistingCredential, inline error display for connection failures (e.g. missing signing secret), and a Slack App Manifest (copy button + View JSON modal) shown after successful connection.
  • One-shot builder: The initial message from AgentHomeContent now fires a one-shot /build request instead of opening a chat thread. The settings sidebar slides in with the Code section auto-expanded and a spinner while the builder configures the agent. Subsequent chats test the agent via /chat.
  • Name/description sync: updateName and updateDescription now update both the entity column and agent.schema (JSON config) so names persist across config saves and page refreshes. Frontend also syncs localConfig.name and emits agentUpdated to refresh the sidebar nav.
  • Chat panel builder tabs: Added test/builder tab switching with persistent builder message history to AgentChatPanel, with configUpdated event handling for real-time sidebar refresh.
  • AgentSettingsSidebar tests: Updated to pass new projectId, agentId, agentName props and config-based mock data.

How to test

  1. Create a new agent, type an initial description → sidebar should open with Code section expanded and spinner while builder runs
  2. After build completes, edit agent name → should persist after refresh and update in sidebar nav
  3. Open Triggers section → Slack integration panel with create/edit credential flow
  4. Connect Slack credential → manifest shown with Copy button and View JSON modal
  5. Open chat → messages should go to /chat (test tab), not builder

Related Linear tickets, Github issues, and Community forum posts

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)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)
© 2026 · via Gitpulse