Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Integration Sync Live Banner Block for React

An integrations callout for a hub: a live "3 of 4 integrations syncing" count over four connector chips with a status dot each; the disconnected one offers Reconnect, and the count turns to "4 of 4".

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

An integrations callout for React with Base UI, for a hub that connects other tools. A header band holds a status dot, a heading with the live count ("3 of 4 integrations syncing") and a line about the one that stopped; under it, a second band ruled from the page's own rail marks holds four connector chips, each an outline badge with its own status dot. The disconnected chip carries a small outline Reconnect button: pressing it turns that chip's dot to the warning colour and the button to "Reconnecting…" for a moment, then the dot goes green, the count becomes "4 of 4 integrations syncing" and focus moves to a short line that says so. The connector names are made up; swap them for yours. It's built from Guides, Badge, Button and Status, with your theme's tokens for every colour. For integration pages, workspace settings and onboarding checklists.

FAQ

How do I change the connectors?

Edit INTEGRATIONS (an id and a name each) and FAILED, the id of the one that starts disconnected. The count in the heading is worked out from the chips' states, so adding a fifth chip makes it "3 of 5" with no other change. To start with every connector healthy, set the initial state to "up" and the Reconnect button never shows.

What does Reconnect do?

It simulates a reconnect: the chip goes to "reconnecting" for 1.6 seconds, then to connected. To make it real, call your connector's reconnect endpoint in the handler, set the state to retrying, and set it to up when the request succeeds (or back to down, with a message, when it fails).

Where does the keyboard go when Reconnect disappears?

While reconnecting, the button stays in the page and focusable, marked aria-disabled and ignoring presses, so focus is not lost. When the connector is back the button is removed, and focus moves to a visually hidden line, "Chatwire reconnected. All 4 integrations are syncing.", at the end of the block, which screen readers read out; the next Tab continues from there.

What do screen readers hear?

A polite status line that is in the page from the start says "Reconnecting Chatwire." when the button is pressed. Each chip's dot is decorative, so its state is also written for screen readers after the name: "Chatwire, disconnected". The heading is the section's name and carries the count.

Why doesn't the text jump between states?

The three sub-lines (stopped, reconnecting, back) share one grid cell and the two that aren't showing are invisible and hidden from assistive technology, so the cell keeps the tallest height. The button's two labels share a cell too, so the chip doesn't change width.

How does it fit on a phone?

The chips wrap onto as many rows as they need under the header, each with its button beside it. Nothing scrolls sideways at 320 pixels, and in a right-to-left layout the chips and the dots mirror.

  • Pro

    A services callout for a cloud platform: a green dot and a heading that counts "All 12 of 12 services operational" from the data, a status-page link, and a matrix of the twelve services on shared hairlines.

  • Pro

    A sync callout for a data warehouse: one run plays on load, a counter rolling up to 1,248 records over a thin progress bar, then "Warehouse synced" with a countdown to the next run.

  • Pro

    A presence callout for a team workspace: a live "4 of 5 teammates active" count over a band of five cells, each an initials avatar with an active or idle dot, a name and the document they are in.

  • Pro

    A failed-deploy callout for a deploy platform: a band with a failure icon, a heading naming the commit, a Shine Button to retry, and a framed excerpt that quotes the failing lines with the bad one marked.

  • Pro

    A connection top bar for a collaborative editor, wired to the browser's online and offline events: Connected, then "You're offline" with a Retry now button and a tinted strip, then "Back online" for a few seconds.

  • Pro

    A top bar for a team workspace manager that says which workspace you are in, with your role as a badge and a Switch menu of workspaces behind a divider.