Tool Connector Setup

Connect an external tool to an AI workflow with scopes, authentication status, allowed actions, test calls, and permission review. This example brings Connector and Permissions together so AI product teams can find the next task without losing context.

It includes representative records such as Google Drive · read files and Slack · send messages. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Tool Connector Setup
Use this template in Figr

Template facts

Screen

Settings

Primary action

Connect tool

Pattern

Settings

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to connect tool while keeping connectors, healthy and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Connector gives users an obvious place to start.
  • Supporting view: Permissions keeps the related context close.
  • Primary action: Connect tool stays visible when people need it.
  • First signal: Connectors shows a useful value (8).
  • Second signal: Healthy gives additional context (7).
  • Sample record: Google Drive · read files.
  • Next record: Slack · send messages.

States worth designing

  • Default preferences: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Policy blocks edit: say what changed, protect progress, and offer a clear next step.
  • Changes applied: say what changed, protect progress, and offer a clear next step.
  • Restricted settings: say what changed, protect progress, and offer a clear next step.
  • Connectivity interrupted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Connector → Permissions → Connect tool → Review outcome

Patterns used

Settings, Connector, Permissions, contextual actions, error recovery

Why these choices work

Separate safe everyday choices from risky changes, show who can edit them, and confirm irreversible actions.

Pay attention to connector and permissions. People need to distinguish Google Drive · read files from Slack · send messages. Keep connectors 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 “Connect tool”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Agent Builder, Knowledge Source Manager, AI Chat Workspace.

Start from this in Figr

Design a tool connector setup screen inside our existing product. Use our current components, tokens and content language. Include Connector and Permissions views, credible records like Google Drive · read files, and a clear “Connect tool” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr