Agent Builder

Configure an AI agent with purpose, tools, instructions, knowledge, triggers, output format, and test runs before publishing. This example brings Instructions and Tools together so AI product teams can find the next task without losing context.

It includes representative records such as System instructions and CRM search tool. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Agent Builder
Use this template in Figr

Template facts

Screen

Builder

Primary action

Publish agent

Pattern

Builder

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to publish agent while keeping tools, knowledge sources and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Instructions gives users an obvious place to start.
  • Supporting view: Tools keeps the related context close.
  • Primary action: Publish agent stays visible when people need it.
  • First signal: Tools shows a useful value (6).
  • Second signal: Knowledge sources gives additional context (4).
  • Sample record: System instructions.
  • Next record: CRM search tool.

States worth designing

  • No configuration selected: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Invalid rule or block: say what changed, protect progress, and offer a clear next step.
  • Preview generated: say what changed, protect progress, and offer a clear next step.
  • Publish blocked: say what changed, protect progress, and offer a clear next step.
  • Version restored: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Instructions → Tools → Publish agent → Review outcome

Patterns used

Builder, Instructions, Tools, contextual actions, error recovery

Why these choices work

Show constraints before adding blocks, keep a usable preview and protect unsaved changes as people test a different direction.

Pay attention to instructions and tools. People need to distinguish System instructions from CRM search tool. Keep tools visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Publish agent”. Make error recovery as clear as the happy path.

Related screen examples to explore next: AI Chat Workspace, Tool Connector Setup, Knowledge Source Manager.

Start from this in Figr

Design a agent builder screen inside our existing product. Use our current components, tokens and content language. Include Instructions and Tools views, credible records like System instructions, and a clear “Publish agent” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr