Continuum Link attaches a saved snapshot from an operational platform to a stratum, as its own read-only tab. Alert state, service ownership and change context sit beside the thing on the diagram they refer to.

It needs an Enterprise licence, edit access to the blueprint, and continuum_integrations.manage on the organisation or team that owns the connection. Below Enterprise the engine refuses with "Continuum integrations are an Enterprise feature." This is a separate gate from the Teams licence Continuum Cloud uses; holding one does not grant the other.

Continuum Link never draws on a canvas. It cannot add, move, recolour or delete anything on a diagram. To generate a diagram from infrastructure, use Continuum Cloud.

Connect a platform

Open Settings → Continuum on the organisation or team, find Operational integrations, and choose New integration. The form asks for a Type, a Name, whatever non-secret fields that connector declares, and one credential. Choosing Connect & verify stores the credential and runs a handshake against the platform in one step.

Jira Cloud and Jira Service Management Operations replace that button with Connect with Atlassian and sign you in instead. Most other connectors take a pasted token or key, GitHub and GitLab included.

Two groups store no credential here. AWS CloudWatch reuses a verified AWS cloud connection: pick that connection and a region, and widen that connection's role with the CloudWatch and Logs actions the form lists. The seven on-premise connectors keep their credential in the Continuum Local agent's own configuration.

Credentials are encrypted at rest, are never returned to the browser, and are never written into a snapshot. To replace one, enter the new value; there is no way to read the old one back.

Link an object to a stratum

Save the blueprint, open a stratum, and choose Continuum Link from its + Add tab menu. Search across every verified connection you can use, review the candidate's identity, then choose Link object. The first snapshot is fetched before the binding is saved, so a link that would have failed never lands.

One connection holds one linked object per stratum. Selecting a different object from the same connection replaces that connection's binding. A stratum can carry 20 linked tabs; a twenty-first is refused with "This stratum already has the maximum of 20 integration tabs."

Two aids propose candidates instead of you searching. Suggest integrations… on a shape's right-click menu scores matches from that shape's own identifiers. Scan for integrations does the same across a whole blueprint, reading titles, tab bodies, file content and diagram shape labels, up to 200 identifiers per scan. Neither writes anything: Scan attaches only what you tick and apply.

Refreshing is manual

Opening a tab shows its saved snapshot and contacts nothing. Nothing polls, and no schedule exists.

Each linked row has two icon buttons with no visible text. The circular-arrows icon re-fetches, and its tooltip reads "Re-fetch this integration's data". The broken-link icon removes the tab, with the tooltip "Remove this integration tab", and asks you to confirm.

A banner above every saved tab states which of these applies:

Banner	Meaning
Saved snapshot	The last fetch succeeded and is still considered fresh
Snapshot needs a refresh	Older than the connector's freshness window
Incomplete snapshot	Some sections could not be read; counts are lower bounds
Last refresh failed	The previous snapshot is still shown, unchanged
Refresh paused	The connection is suspended

Only nine connectors declare a freshness window: PagerDuty, incident.io, Rootly, Datadog, LogicMonitor, Auvik, Jira Cloud, Jira Service Management Operations and ServiceNow. Most set five minutes. Jira Cloud work items set fifteen, Jira Service Management on-call coverage sets two, and ServiceNow sets one day.

The other nineteen connectors never report a snapshot as needing a refresh. A months-old Grafana or GitHub tab still reads "Saved snapshot". Check the fetch time on the tab rather than trusting the banner.

A failed read never becomes a healthy-looking zero. Missing sections are marked unavailable or partial, and a failed refresh keeps the previous snapshot.

Who can read a saved panel

This depends on the connector, so check it before linking.

Connector	Default audience for a new connection
Datadog, LogicMonitor, Auvik, Rootly, ServiceNow	Blueprint editors only
Every other connector	Everyone who can read the stratum

Where a connector has no audience setting, its panel reaches every reader of the blueprint. On a public blueprint that includes anonymous readers, embeds and exports. The five connectors above offer a reader-visible option, labelled All Blueprint readers.

A connection created before those settings existed keeps its historical behaviour, which is reader-visible and detailed, until an administrator opens Configure and saves. Check old connections rather than assuming the newer defaults apply.

An audience change applies to later fetches. It does not rewrite snapshots already saved, and it cannot recall versions, templates, exports, embeds or AI answers that already carry the data. Unlinking a tab and revoking a credential cannot recall them either.

Managing a connection

Control	What it does
`Configure`	Edits the connection's non-secret settings, including audience and detail
`Verify`	Re-runs the handshake, including optional capabilities
`Suspend` and `Resume`	Stops and restarts search and refresh. Saved snapshots stay readable
`Rotate token` or `Replace credentials`	Reveals a field, then `Verify & replace` swaps the credential only if the new one verifies
`Remove token…`	Clears the stored credential and suspends the connection

Deleting a connection is refused while tabs are still bound to it: "This integration has N stratum tab(s) bound to it. Remove those first."

If the plan lapses, the section stays open in a cleanup-only mode. You can suspend, inspect, unlink and disconnect. Adding or refreshing data needs Enterprise again.

Which platforms

38 connectors are registered. 28 work directly, 7 more need Continuum Local for systems Blueprintr cannot reach, and 3 are declared but not built, shown as "On the roadmap".

The connector reference lists all of them with what each one asks for and shows. Eight have a guide of their own:

PagerDuty

Service ownership, incident state and on-call coverage.

incident.io

Catalog services and the incidents attached to them.

Rootly

Incident response and follow-up progress.

Jira

Work items, and alerting from Service Management Operations.

Datadog

Hosts, monitors, catalog services and reliability objectives.

LogicMonitor

Devices, DataSource instances and resource groups.

Auvik

Network device context and recent alert history.

ServiceNow CMDB

The configuration item, its relationships and its open work.