Connections

A connection is an authenticated link to an external app. Before you can interact with an app (read data, create records), a connection must be established that authorizes access. See Connections API Reference for the full API. Membrane handles the full authentication lifecycle: OAuth flows, token refresh, API key storage, automatic recovery from failures, and credential encryption at rest.

​

Connecting

Create a connection to an external app. You can connect by intent — just describe what you want to connect to and Membrane finds the right app automatically.

​

Managing Connections

​

Listing

List all connections for the current tenant.

​

Status

Each connection carries a status — the single field that says where it stands: When a connection is broken, statusReason names the cause: reauthenticate (the app rejected the stored authorization — a person must re-connect), configure (the connection’s configuration is invalid), unavailable (the app kept failing without ever rejecting the authorization — nothing is asked of the user), or error (an internal setup failure). The connected and state fields remain on the response as projections of status, for consumers written before it existed.

​

Reconnecting

A single failed request does not disconnect a connection. Membrane counts failures, keeps using the connection while the failures look temporary, and marks it broken only when the app confirms the authorization is no longer valid — or when failures persist long enough to be more than a bad afternoon at the provider. Every broken connection is retried automatically in the background, and returns to active on its own as soon as the app answers again. healingExhausted: true means those retries have stopped and a person is now the only way back. To reconnect manually:

​

Deleting

Archive a connection to disconnect and remove it.