Integration Beam

Your product between the tools it connects, with light flowing along the beams.

PROGet Integration Beam and 168 other Pro components with pro lifetime — Get Pro

Category
Creative
Access
Pro
Source
493 lines · one file
States
5 drawn
Added
21 Oct 2026

The decision inside it

Beams run the way the data does

Each tool says whether data comes in, goes out or both, and the light travels that way, so the picture shows which tools feed you and which you feed. Pointing at a tool spells it out too: "Liro → Liro · Payments".

When to use it

Use Integration Beam on a landing page to show your product between the tools it connects, with light flowing along each beam in the direction the data really goes (in, out or both). Four to eight tools; pass icons and colours yourself.

Installation

How you get it

Paste this into Claude Code, Cursor, Codex or any coding agent. It installs the file and uses it as it is, instead of writing a new one.

Use Liro's Integration Beam for this.
Install it: npx shadcn@latest add @liro/integration-beam
(the @liro registry is set up in components.json, with LIRO_KEY in .env.local)
Import it from @/components/ui/integration-beam.
Do not rewrite or restyle it. Pass my data through its props
and keep its built-in states.

For the full brief with every prop and the mistakes assistants usually make, use Copy prompt above. Pro components install through the @liro registry with your CLI token: see the Namespaced tab.

Usage

components/integrations-hero.tsx
import { IntegrationBeam } from "@/components/ui/integration-beam";

export function IntegrationsHero() {
  return (
    <IntegrationBeam
      centerLabel="Liro"
      caption="Syncing"
      tools={[
        { id: "crm", name: "CRM", direction: "both", label: "Contacts", color: "#f97316" },
        { id: "pay", name: "Payments", direction: "in", label: "Payments", color: "#6366f1" },
        { id: "mail", name: "Mail", direction: "out", label: "Receipts", color: "#ef4444" },
        { id: "drive", name: "Drive", direction: "out", label: "Signed PDFs", color: "#3b82f6" },
      ]}
    />
  );
}

API reference

“Copy prompt” above puts a full brief on your clipboard, install command, dependencies, props, and the mistakes an assistant usually makes with this component.

Props

Read from the component’s own TypeScript interface when the site is built, so this table cannot drift from the file you install.

TypeNotes
toolsBeamTool[] Yes4 to 8 tools. More than 8 are not drawn.
centerReact.ReactNode NoThe centre node: your logo. Default: the first letter of centreLabel.
centerLabelstring NoYour product's name, used in captions and labels. Default "Your app".
heightnumber NoHeight of the stage, in px. Default 400.
durationnumber NoSeconds a pulse takes to cross its beam. Default 2.4.
pausedstring[] NoTools whose beams are paused, controlled.
defaultPausedstring[] NoTools whose beams start paused, uncontrolled.
onPausedChange(ids: string[]) => void No–
showNamesboolean NoShow tool names under the tiles when there is room. Default false.
pulseClassNamestring NoColour class for pulses of tools without a `color`. Default blue.
captionReact.ReactNode NoA small status chip under the hub, e.g. "Syncing".
gridboolean NoA faint dot grid behind the scene. Default true.

Dependencies

npm packages

clsxlucide-reacttailwind-merge

Liro foundations, installed alongside it

liro-theme

States

All of them are drawn by the component. None is left for you to design.

  • Flowing
  • Tool focused
  • Beam paused
  • Off screen
  • Reduced motion

Accessibility

  • Keyboard reachable throughout, in visual order
  • Focus trapped in overlays, Escape closes them
  • Focus returns to whatever opened it
  • Live regions announce what changed, not that something did
  • Honours prefers-reduced-motion

Responsive behavior

  • Sizes to its container, not the viewport
  • Usable from 320px up
  • Pointer-based interaction, so trackpad and touch both work
  • No hover-only affordances