OpenClaw OAuth Adapter
An OAuth configuration that lets authorized users connect Google accounts to an operator-controlled OpenClaw environment through gogcli.
Purpose
The adapter identifies this application during Google’s consent flow. Once a user approves the displayed permissions, gogcli stores a separate authorization for that Google account. The operator-controlled OpenClaw environment can then use that authorization to perform tasks requested by the user or an authorized operator.
Access is account-specific: each participating user reviews Google’s consent screen and decides whether to grant the requested permissions.
How authorization works
- The operator starts onboarding.The intended Google account and a local alias are selected in the secured environment.
- Google displays the request.The user signs in directly with Google and reviews the requested permissions.
- The user decides.No Google access is granted unless the user approves the consent screen.
- gogcli stores the credential.The authorization is saved in an encrypted file-based keyring in protected service state, separate from the public website.
- OpenClaw performs requested tasks.The credential is used when an authorized workflow needs a permitted Google service.
Google services and data
The current integration can request access to the services below. The exact permissions and affected Google account are shown by Google before authorization.
- Gmail
- Calendar
- Drive
- Docs
- Contacts
- Tasks
- Photos
Depending on the requested task and granted permissions, the adapter may read, search, organize, create, update, send, or delete data. It does not receive broader authority than the scopes displayed by Google.
Google user data is used only to provide user-facing, authorized features. It is not sold, used for advertising, or supplied to data brokers.
What is—and is not—the adapter
One client, separate grants
The OAuth client identifies the application. Every Google account has its own grant and stored credential.
No token collection here
This public information website does not receive OAuth redirects, credentials, or Google account content.
Controlled processing
Authorized tasks run in the operator-controlled OpenClaw environment, with gogcli and configured service providers where needed.
No Google affiliation
The adapter is independently operated and is not sponsored, endorsed, or operated by Google or OpenClaw.
User choices and controls
These controls have different effects:
- Remove a local alias
- Stops using that friendly account mapping in the OpenClaw service registry. It does not by itself erase the stored Google credential or revoke Google’s grant.
- Delete the local credential
- Removes the stored refresh credential from the secured environment. Backup copies may remain until the relevant backup is removed or expires.
- Revoke Google access
- Stops future API access under the grant. The account holder can do this from Google Account permissions.
- Request data deletion
- Ask the operator to remove locally held account records, credentials, and retained task data, subject to legal or security retention needs.
Full details appear in the Privacy Policy.
Operator and contact
The adapter is independently operated under the OpenClaw OAuth Adapter service name. Questions about access, authorization, privacy, or deletion can be sent to [email protected].