Integration Settings

Connect external tools with clear permissions, data direction, sync status, owner, and recovery when a connection breaks. The screen connects Integrations and Connected so workspace admins can find the “Add integration” action while checking connected and healthy.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Slack · Healthy and Salesforce · Healthy, rather than an empty visual shell.

Integration Settings
Use this template in Figr

Template facts

Screen

Form

Primary action

Add integration

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Add integration” action without losing sight of connected, healthy and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Add integration is clearly available where the task happens.
  • Main view: Integrations keeps the starting point obvious.
  • Connected view: Connected supplies nearby context.
  • Metric: Connected is visible with a meaningful value.
  • Another signal: Healthy helps people judge what to do next.
  • Representative record: Slack · Healthy makes the example specific.
  • Second record: Salesforce · Healthy shows the pattern works beyond one item.

States worth designing

  • Missing required details; show what people can do instead of leaving a blank panel.
  • Loading integrations without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for connected; clarify who can continue.
  • Success after choosing Add integration; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Integrations → Connected → Add integration → Review outcome

Patterns used

Form, Integrations, Connected, Catalog, accessible states, contextual actions

Why these choices work

Put requirements beside each field and show validation near the source of the error. Keep entered details if saving fails.

In this design, people should be able to compare Slack · Healthy with Salesforce · Healthy. Make connected clear, then use healthy to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Add integration” action. The happy path alone is not enough.

Related UI examples: API Access, Notification Preferences, Security Incidents.

Start from this in Figr

Design a integration settings screen for our existing software product. Use our real design-system tokens, components and product language. Show Integrations and Connected, include believable records such as Slack · Healthy, and make add integration easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr