Connections & keys

Third-party integrations and credential handling.

Bring your own key

AI-provider keys are configured per workspace, stored encrypted at rest, and resolved only at call time. Keys never appear in logs, run records, or API responses.

Connections

Third-party apps connect through a brokered connection system: OAuth or token credentials are held host-side, calls are pinned to each provider’s real API hosts, and revoking a connection immediately disables everything that used it.

Connection packs

New providers are described by connection packs — declarative manifests validated against a schema — so adding an integration does not mean adding trusted code.

Egress governance

Outbound calls from workflows go through governed adapters. Vendor-write operations (posting, sending, paying) are marked adapter-only, so a workflow node can never smuggle a raw credential to an arbitrary host.