Integrations

Architecture exists; provider coverage is rolling out

The catalog of supported providers and the per-Node Connection lifecycle (pending, connected, error, disconnected) are real and live today. What's still rolling out is the Provider Adapter layer — the piece that actually authenticates with and syncs live data from most external providers. This page draws that line deliberately rather than implying every catalog entry is already a working, connected integration.

Why the layers are separated

A Node exposes Capabilities (what it can share — read-only metrics, for instance). An Integration Definition is the catalog entry describing how a given provider connects to a Capability. A Connection is the per-Node record of that relationship's current state. Separating these means a Connection can honestly report "pending" or "error" without the whole Integration concept being fake — the state is real even where the underlying adapter isn't finished.

Where it's tested

A Workflow's Invoke Integration step is the operational surface that actually exercises a Connection — it tests whether the link between a Node and a published Integration is live, the same distinction this page draws between architecture and provider readiness.