What is the difference between a private and a team connection?

A private connection is only available to the user who created it and the Claws they configure. A team connection is shared across all team members and can be used by any Claw on the team.

Can I revoke a connection?

Yes. You can disconnect any connection at any time from the Connections page. This immediately removes the Claw's access to that service.

Do I need to set up connections for every Claw?

Connections are registered per-Claw, but a single connection can be shared with multiple Claws. You choose which Claws have access to each connection.

What happens when a connection expires?

WorkClaw tracks connection status automatically. If an OAuth token expires, WorkClaw will notify you and prompt you to re-authorize. The Claw will not attempt to use an expired connection.

Can I connect custom or internal APIs?

Yes. WorkClaw supports custom app connections where you provide API credentials (stored securely in the Vault) and define the endpoints your Claw can access.

What are Connections?

Connections are secure integrations that let Claws interact with external services like Google, Slack, and custom APIs. Learn about OAuth, scopes, status tracking, and per-Claw registration.

What is a Connection?

A Connection is a secure integration between a Claw and an external service. Connections let your Claw interact with the tools you already use -- reading and sending emails through Gmail, posting messages in Slack, accessing files in Google Drive, or calling custom APIs.

Without connections, a Claw can converse and reason. With connections, it can reach into your existing workflow and take action.

How are Connections authenticated?

WorkClaw supports two authentication methods:

OAuth -- the standard for services like Google and Slack. You click "Connect," authorize access in the service's login flow, and WorkClaw stores the token securely. OAuth connections handle token refresh automatically so you do not need to re-authorize regularly.

Custom API credentials -- for services that do not support OAuth or for internal APIs. You provide an API key, token, or other credentials, and WorkClaw stores them in the encrypted Vault. The Claw uses these credentials when calling the service.

What are Connection scopes?

Every connection has a scope that controls who can use it:

Scope	Visibility	Best for
Private	Only the user who created it	Personal accounts, individual tool access
Team	All members of the team	Shared service accounts, team-wide integrations

When you create a connection, you choose its scope. Private connections are ideal for personal email or calendar accounts. Team connections work well for shared tools like a company Slack workspace or a team CRM.

How does per-Claw registration work?

Creating a connection does not automatically give every Claw access to it. Connections are registered per-Claw -- you explicitly choose which Claws can use each connection. This gives you granular control:

Your "Sales Assistant" Claw might have access to the CRM connection but not your personal email.
Your "Executive Support" Claw might have both email and calendar connections.
Your System Claw might have access to all team-scoped connections.

You manage these registrations from the Claw's settings page or from the Connections overview.

How does WorkClaw track Connection status?

Each connection has a status that WorkClaw monitors:

Active -- the connection is working and the Claw can use it.
Expired -- an OAuth token has expired and needs re-authorization.
Error -- something went wrong (invalid credentials, service unavailable).
Disconnected -- the connection was manually revoked.

WorkClaw notifies you when a connection needs attention. A Claw will not attempt to use a connection that is not in an active state, preventing failed actions and confusing errors.

What services can I connect?

WorkClaw has built-in support for common services:

Google -- Gmail, Calendar, Drive, Docs, Sheets
Slack -- messaging, channels, DMs
Custom Apps -- any API with key-based or token-based authentication

The list of supported integrations is growing. Many skills include requirements for specific connections and will guide you through setup during installation.