Connections
A connection is a saved set of credentials used to authenticate requests against an external service. Connections are defined once and reused across multiple workflows.
Where connections are used
The HTTP Request node has an Auth field that accepts a connection. When the node executes, Blokkio resolves the connection and applies the credentials automatically — you do not need to manage headers or tokens manually.
Managing connections
Go to Connections in the sidebar to view, create, and manage connections for the current project.
Connections are project-scoped. A connection created in one project is not visible in another.
Connection types
Blokkio includes four built-in connection types:
| Type | Use case |
|---|---|
| Basic Auth | Username/password HTTP Basic authentication |
| OAuth 2.0 | OAuth 2.0 flows (Authorization Code, Client Credentials, etc.) |
| API Key | API key passed as a header or query parameter |
| Bearer Token | Static bearer token in the Authorization header |
Custom connection definitions can also be created via Connections → Definitions if you need a non-standard credential format.
Security
Credential values are encrypted at rest. Secret values are never returned by the API after creation — the UI shows a masked placeholder. To update a credential, overwrite the field with a new value.
Connection definitions
Connection definitions are templates that describe the structure of a credential type. Built-in definitions cover the four standard types above. You can create custom definitions from Connections → Definitions by specifying the fields and where they map to in an outgoing request (header, query parameter, body, or none).