ComposioHQ/awesome-claude-skills / composio-skills/google-admin-automation
google-admin-automation
VerifiedAutomate Google Workspace Admin tasks via Rube MCP (Composio): manage users, groups, memberships, suspend accounts, create users, add aliases. Always search tools first for current schemas.
Google Workspace Admin Automation via Rube MCP
Manage Google Workspace users, groups, memberships, and organizational settings programmatically using Rube MCP (Composio).
Toolkit docs: composio.dev/toolkits/google_admin
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active connection via
RUBE_MANAGE_CONNECTIONSwith toolkitgoogle_admin - Google Workspace admin privileges for the authenticated account
- Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitgoogle_admin - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List All Users
Use GOOGLE_ADMIN_LIST_USERS to retrieve Google Workspace users with optional filtering and pagination.
Tool: GOOGLE_ADMIN_LIST_USERS
Parameters:
- customer: Customer ID or "my_customer" (default)
- domain: Domain to list users from
- query: Filter string (e.g., "orgName=Engineering", "isSuspended=false")
- max_results: Maximum results (1-500, default 100)
- order_by: Sort by "email", "givenName", or "familyName"
- sort_order: "ASCENDING" or "DESCENDING"
- page_token: Pagination token
2. Create a New User
Use GOOGLE_ADMIN_CREATE_USER to provision a new Google Workspace account.
Tool: GOOGLE_ADMIN_CREATE_USER
Parameters:
- primary_email (required): User's email (e.g., "john.doe@company.com")
- given_name (required): First name
- family_name (required): Last name
- password (required): Password meeting domain requirements
- org_unit_path: Organizational unit (default: "/")
- change_password_at_next_login: Force password change (default: true)
- recovery_email: Recovery email address
- recovery_phone: Recovery phone number
- suspended: Whether account starts suspended (default: false)
3. List and Manage Groups
Use GOOGLE_ADMIN_LIST_GROUPS to list groups, and GOOGLE_ADMIN_CREATE_GROUP to create new ones.
Tool: GOOGLE_ADMIN_LIST_GROUPS
Parameters:
- customer: "my_customer" (default)
- domain: Filter by domain
- query: Filter (e.g., "name=Engineering*")
- max_results: Max results (1-200)
- order_by: Sort by "email"
- page_token: Pagination token
Tool: GOOGLE_ADMIN_CREATE_GROUP
Parameters:
- email (required): Group email address (e.g., "engineering@company.com")
- name (required): Display name (e.g., "Engineering Team")
- description: Group purpose description
4. Add Users to Groups
Use GOOGLE_ADMIN_ADD_USER_TO_GROUP to manage group membership.
Tool: GOOGLE_ADMIN_ADD_USER_TO_GROUP
Parameters:
- group_key (required): Group email or ID
- user_key (required): User email or ID to add
- role: "MEMBER" (default), "MANAGER", or "OWNER"
5. Suspend or Unsuspend Users
Use GOOGLE_ADMIN_SUSPEND_USER to toggle user account suspension.
Tool: GOOGLE_ADMIN_SUSPEND_USER
Parameters:
- user_key (required): User's email or unique ID
- suspended: true to suspend, false to unsuspend (default: true)
- suspension_reason: Reason for suspension (optional)
6. Get User or Group Details
Use GOOGLE_ADMIN_GET_USER or GOOGLE_ADMIN_GET_GROUP to retrieve detailed information.
Tool: GOOGLE_ADMIN_GET_USER
Parameters:
- user_key (required): User's email or unique ID
Tool: GOOGLE_ADMIN_GET_GROUP
Parameters:
- group_key (required): Group's email or unique ID
Common Patterns
- Onboarding workflow: Use
GOOGLE_ADMIN_CREATE_USERto provision the account, thenGOOGLE_ADMIN_ADD_USER_TO_GROUPto add them to relevant groups. - Offboarding workflow: Use
GOOGLE_ADMIN_SUSPEND_USERto disable access, orGOOGLE_ADMIN_DELETE_USERfor permanent removal. - Audit group membership: Use
GOOGLE_ADMIN_LIST_GROUPSto find groups, thenGOOGLE_ADMIN_LIST_GROUP_MEMBERSto review members. - Bulk user management: List users with
GOOGLE_ADMIN_LIST_USERSand filter queries, then iterate for updates. - Add email aliases: Use
GOOGLE_ADMIN_ADD_USER_ALIASto add alternative email addresses for a user. - Look up user details: Use
GOOGLE_ADMIN_GET_USERto retrieve full profile information before making changes.
Known Pitfalls
- Admin privileges required: All tools require the authenticated user to have Google Workspace administrator privileges. Non-admin accounts will receive permission errors.
- Delete is permanent:
GOOGLE_ADMIN_DELETE_USERpermanently removes a user account. This action cannot be undone. - user_key accepts email or ID: The
user_keyparameter accepts both the user's primary email address and their unique numeric user ID. - Group membership replaces: When adding to groups, the
roleparameter controls the member's role. There is no "update role" -- remove and re-add to change roles. - Customer ID: Use
"my_customer"as thecustomerparameter for the authenticated user's organization. Specific customer IDs look likeC01abc123. - Pagination: Both user and group list endpoints may return paginated results. Always check for
page_tokenin responses for complete results. - Password requirements:
GOOGLE_ADMIN_CREATE_USERrequires a password that meets the domain's password policy. Weak passwords will be rejected.
Quick Reference
| Action | Tool | Key Parameters |
|---|---|---|
| List users | GOOGLE_ADMIN_LIST_USERS | customer, domain, query, max_results |
| Get user details | GOOGLE_ADMIN_GET_USER | user_key |
| Create user | GOOGLE_ADMIN_CREATE_USER | primary_email, given_name, family_name, password |
| Delete user | GOOGLE_ADMIN_DELETE_USER | user_key |
| Suspend user | GOOGLE_ADMIN_SUSPEND_USER | user_key, suspended |
| Add user alias | GOOGLE_ADMIN_ADD_USER_ALIAS | (see full schema via RUBE_SEARCH_TOOLS) |
| List groups | GOOGLE_ADMIN_LIST_GROUPS | customer, domain, query |
| Get group details | GOOGLE_ADMIN_GET_GROUP | group_key |
| Create group | GOOGLE_ADMIN_CREATE_GROUP | email, name, description |
| Add to group | GOOGLE_ADMIN_ADD_USER_TO_GROUP | group_key, user_key, role |
| List group members | GOOGLE_ADMIN_LIST_GROUP_MEMBERS | (see full schema via RUBE_SEARCH_TOOLS) |
Powered by Composio
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |