google-workspace-adminGoogle Workspace Admin SDK integration with managed OAuth. This is a write-capable administrative integration for users, groups, organizational units, roles, and domain settings. Only connect with a least-privileged Google admin account, restrict OAuth scopes to the specific resources needed, and revoke the connection after use. All write operations require explicit user approval showing the exact HTTP method, endpoint path, and target resource identifier before execution. Use this skill only when users need Google Workspace administration. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Workspace Admin connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Workspace Admin action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Workspace Admin examples; they add no Google Workspace Admin capability - Google Workspace Admin is not an event source, a trigger cannot read Google Workspace Admin data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Install via ClawdBot CLI:
clawdbot install byungkyu/google-workspace-adminGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Scored Sep 24, 2026
Calls external URL not in known-safe list
https://clawhub.ai/byungkyu/api-gatewayUses known external API (expected, informational)
discord.comAudited Apr 16, 2026 · audit v1.0
Generated Mar 1, 2026
IT departments can automatically create Google Workspace accounts for new hires by integrating this skill with HR systems. The skill allows setting up user profiles, assigning to organizational units, and configuring email aliases without manual intervention, streamlining the onboarding process.
Administrators can manage group memberships and permissions for different departments like Sales, Engineering, or Finance. The skill enables bulk updates to user roles, suspension of accounts for departed employees, and auditing of access levels to maintain security compliance.
Companies with multiple domains can use this skill to synchronize user directories across different Google Workspace instances. It allows querying users by domain, migrating accounts between organizational units, and ensuring consistent settings for subsidiaries or acquired businesses.
Compliance teams can generate reports on user activities, login times, and administrative changes. The skill facilitates extracting user data, filtering by suspension status or admin roles, and monitoring for unauthorized access to meet regulatory requirements.
Developers can integrate Google Workspace user management into custom applications like CRM or project management tools. The skill provides API endpoints to create, update, or delete users programmatically, enabling seamless data flow between systems.
MSPs can offer Google Workspace administration as a service to multiple clients, using this skill to manage users, groups, and settings across different domains. It enables scalable billing based on user counts or administrative actions, with automation reducing manual overhead.
Companies can develop internal tools for IT teams to automate user lifecycle management, such as onboarding/offboarding workflows. The skill reduces operational costs by minimizing manual admin tasks and integrating with existing HR or identity systems.
Platforms can expose this skill's capabilities to developers through a managed API, charging for usage based on request volume or features. It simplifies OAuth management and provides a reliable gateway for building apps that interact with Google Workspace.
💬 Integration Tip
Ensure MATON_API_KEY is securely stored in environment variables and use the Maton-Connection header to manage multiple Google Workspace instances, especially in multi-tenant applications.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Gmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. Just OAuth sign-in. Zero setup complexity vs traditional Google API integrations.
Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).