Connections

Swirls provides three kinds of credential declarations for external services:

1. Secrets store sensitive values. Declare variable names in the file and set their values in the project vault. Nodes receive only the variables they request.
2. Credential profiles describe how to apply those values. An auth block configures OAuth client credentials, API keys, basic auth, or bearer tokens for HTTP requests. Basic auth can also protect a public form.
3. Connections bind named slots to provider accounts. Swirls brokers OAuth for managed connections; self-managed connections read vault credentials. Action blocks declare typed API operations. Browse the catalog, install them with swirls add, or request provider support.

Use a managed connection when the provider is supported and you want Swirls to handle OAuth. Use a credential profile when you manage the credentials. On HTTP nodes, auth: and connection: are mutually exclusive. Integration nodes take connection:; OAuth-backed channels use it for replies.

Project Networks declare private routes for selected interfaces and outbound consumers. See that guide for binding requirements and availability.

To control who may invoke agents and workflows, see Access.