Connect Integrations and Credentials Safely

1. 01.1

   Deployment secrets operate Agent Barn infrastructure.

2. 01.2

   Agent Secrets are for one Agent’s tool Integrations.

3. 01.3

   Shared Credentials are owned by an Organization and can be attached to permitted Agents.

4. 01.4

   Communication Connection credentials are owned by one Agent-subordinate Connection.

1. 02.1

   Current providers are GitHub, Jira, Confluence, Bitbucket, Google Workspace, Zoho Mail, Zoho Calendar, Firecrawl, Slack, and Pipedrive.

2. 02.2

   Gmail, Google Calendar, and Google Sheets are no longer separate credential providers. Configure Google access through one Google Workspace credential, selecting services and an access level.

1. 03.1

   Agent Secrets belong to one Agent. Shared Credentials belong to one Organization.

2. 03.2

   An Agent may use either a Shared Credential or a per-Agent Secret for a provider, never both simultaneously, and has at most one attached credential source per provider.

3. 03.3

   Multiple named Shared Credentials for the same provider may exist within an Organization, but their names are unique there. Deletion is blocked while a non-deleted Agent references the credential.

4. 03.4

   Shared Credentials currently support GitHub, Jira, Confluence, Bitbucket, and Zoho Mail. Google Workspace OAuth credentials are not shareable under the current contract.

5. 03.5

   Read APIs expose provider and display metadata, never credential contents.

1. 04.1

   The user selects Google services and read-only versus write access. Signed, short-lived OAuth state carries those choices; stored services, access level, granted scopes, and account identity are validated together.

2. 04.2

   Google Workspace materializes through gog, separately from aai-cli.

3. 04.3

   Slack, Microsoft Teams, Telegram, and Discord messaging credentials belong to Communication Connections. Shipped Platform Plugins define typed settings and credential schemas, validate values before encrypted persistence, and enforce provider identity uniqueness where required.

4. 04.4

   Connection credential values are write-only and omitted from read responses. They are never materialized into Hermes or OpenClaw.

5. 04.5

   For messaging setup, see Set up Slack and manage Communication Connections.

1. 06.1

   Build aai-cli configuration and its secret store.

2. 06.2

   Build Google Workspace gog setup and inject permitted provider environment.

3. 06.3

   Mount exact assigned Skill versions and eligible bundled Skills, then append tool Integration policy to rendered Agent instructions.

1. 07.1

   Create: the Platform Plugin validates settings and credentials before encryption.

2. 07.2

   Read: only safe metadata, schema information, status, and health are returned.

3. 07.3

   Update: replacement credentials and settings are revalidated, and the Connection revision advances.

4. 07.4

   Reconcile: the Communications supervisor recreates or updates the provider session without restarting the Agent.

5. 07.5

   Disable: provider ingress stops while the Connection remains available for later enablement.

6. 07.6

   Retire: credentials are scrubbed, pending Deliveries are cancelled, provider identity is released, and canonical Conversation history is preserved.

Connection health can change independently of Agent lifecycle.

1. 08.1

   Tool Integrations: prefer read-only access, restrict repositories, spaces, accounts, and services, assign only required Skills, and use Shared Credentials only when reuse is intentional.

2. 08.2

   Communication Connections: grant only required bot scopes and provider permissions; restrict allowed locations, users, groups, roles, and direct messages through Connection settings; rotate or replace credentials on the Connection; and diagnose provider failures through Connection health and Communication Diagnostics.

1. 09.1

   Agent Secret changes require Agent access and agent.secret.manage.

2. 09.2

   Connection setting changes require agent.update; creating, replacing, or retiring Connection credentials additionally requires agent.secret.manage.

3. 09.3

   Organization Members can see available Shared Credentials without seeing their secret values. Attaching one to an existing Agent also requires permission to update that Agent and manage its credentials. Organization Owners and Admins manage the shared credentials themselves.

4. 09.4

   Selecting an eligible Shared Credential while creating an Agent follows the Agent creation workflow. For step-by-step instructions, see Use shared credentials.

1. 10.1

   Browse tool Integrations and manage Agent credentials.

2. 10.2

   Use Shared Credentials for eligible reusable tool access.

3. 10.3

   Manage Communication Connections, browse Platforms, and use Communication diagnostics for provider delivery concerns.