Connections

The connections commands manage integration connections — typed records that flows, agents, and triggers reference for OAuth apps, webhooks, SQL, LLM providers, and more.

Credential values never appear on the command line. Store secrets with vault put or secrets set, then reference a vault key when provisioning a connection.

Prerequisites

akos auth login
akos serve    # or AKOS_HEADLESS_URL for a remote sidecar

See Authentication for login, vault, secrets, and creds workflows.

List connections

akos connections list
akos connections list --kind slack --json

Read one connection

akos connections get slack-main --json
akos connections sql-get analytics-db --json

Integration setup registry

The setup registry powers the assistant, Connections UI, and this CLI surface. Print provider-specific guidance before wiring credentials:

akos connections guide slack
akos connections guide discord --json
akos connections guide --category llm --implemented-only

Each entry includes:

• Preferred setup mode (OAuth, bot install, guided secret, …)
• Required scopes and health-check RPC method
• Assistant-safe wording hints
• Links to external credential pages when applicable

This mirrors the Integration setup product guide and akos creds guide.

Provision a connection

akos connections set \
  --id slack-main \
  --kind slack \
  --label "Engineering Slack" \
  --secret-id SLACK_BOT_TOKEN

Use --no-auth for connections that do not require stored credentials. Optional flags: --scopes (comma-separated), --schema, --workspace. Supported kinds: slack, github, linear, discord, email, cron, file, webhook, cdc, twilio, sentry, pagerduty, stripe, s3, mcp, llm.

Remove a connection

akos connections rm my-slack

Removing a connection does not delete the underlying vault secret.

Preflight readiness

Before a demo or deploy, verify that required credential keys exist (values are never printed):

akos connectors test --workspace default
akos connectors test --workspace default --kind slack --json

External automation API keys

Scoped keys for /v1/automations/* are provisioned through the Connections UI (External apps) or the sidecar integration surface — not via a separate CLI verb today. See Public automation API for request shapes after keys exist.

Related topics

• Connections in the app — OAuth cards, SQL, cloud sync, coding agents.
• Authentication — vault, secrets, and creds check.
• Integration setup — guided setup narrative for operators.
• Triggers — SaaS triggers that share OAuth connections.
• Command reference — full connections.* and connectors tables.