Google_admin Automation

What This Skill Does

This skill automates Google Admin operations using Composio's Google Admin toolkit via Rube MCP. It allows users to manage user accounts, organizational units, groups, and domain settings. It is designed for users who need to streamline Google Admin tasks.

When to Use

Automate user provisioning and deprovisioning. Manage Google Workspace groups and memberships. Configure organizational unit settings. Automate domain-related tasks. Discover available Google Admin tools. Execute multi-step Google Admin workflows.

Key Features

Automates Google Admin tasks via Rube MCP.Uses Composio's Google Admin toolkit. Requires an active Google Admin connection. Discovers available tools using RUBE_SEARCH_TOOLS.Executes operations via RUBE_MULTI_EXECUTE_TOOL.Supports multi-step workflows.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedGoogle Admin Automation via Rube MCP Automate Google Admin operations through Composio's Google Admin toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/google_admin

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Google Admin connection via RUBE_MANAGE_CONNECTIONS with toolkit google_admin Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit google_admin If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows: RUBE_SEARCH_TOOLS: queries=[{"use_case": "user management, org units, groups, and domain administration", "known_fields": ""}] This returns: Available tool slugs for Google Admin Recommended execution plan steps Known pitfalls and edge cases Input schemas for each tool

Core Workflows

1. Discover Available Google Admin Tools

RUBE_SEARCH_TOOLS: queries: - use_case: "list all available Google Admin tools and capabilities" Review the returned tools, their descriptions, and input schemas before proceeding.

2. Execute Google Admin Operations

After discovering tools, execute them via: RUBE_MULTI_EXECUTE_TOOL: tools: - tool_slug: "<discovered_tool_slug>" arguments: {<schema-compliant arguments>} memory: {} sync_response_to_workbench: false

3. Multi-Step Workflows

For complex workflows involving multiple Google Admin operations: Search for all relevant tools: RUBE_SEARCH_TOOLS with specific use case Execute prerequisite steps first (e.g., fetch before update) Pass data between steps using tool responses Use RUBE_REMOTE_WORKBENCH for bulk operations or data processing

Common Patterns

Search Before Action

Always search for existing resources before creating new ones to avoid duplicates.

Pagination

Many list operations support pagination. Check responses for next_cursor or page_token and continue fetching until exhausted.

Error Handling

Check tool responses for errors before proceeding If a tool fails, verify the connection is still ACTIVE Re-authenticate via RUBE_MANAGE_CONNECTIONS if connection expired

Batch Operations

For bulk operations, use RUBE_REMOTE_WORKBENCH with run_composio_tool() in a loop with ThreadPoolExecutor for parallel execution.

Known Pitfalls

Always search tools first: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via RUBE_SEARCH_TOOLS. Check connection status: Ensure the Google Admin connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. Respect rate limits: If you receive rate limit errors, reduce request frequency and implement backoff. Validate schemas: Always pass strictly schema-compliant arguments. Use RUBE_GET_TOOL_SCHEMAS to load full input schemas when schemaRef is returned instead of input_schema.

Quick Reference

Toolkit docs: composio.dev/toolkits/google_adminGoogle Admin Automation via Rube MCP Automate Google Admin operations through Composio's Google Admin toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/google_admin

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Google Admin connection via RUBE_MANAGE_CONNECTIONS with toolkit google_admin Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit google_admin If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows: RUBE_SEARCH_TOOLS: queries=[{"use_case": "user management, org units, groups, and domain administration", "known_fields": ""}] This returns: Available tool slugs for Google Admin Recommended execution plan steps Known pitfalls and edge cases Input schemas for each tool

Core Workflows

1. Discover Available Google Admin Tools

RUBE_SEARCH_TOOLS: queries: - use_case: "list all available Google Admin tools and capabilities" Review the returned tools, their descriptions, and input schemas before proceeding.

2. Execute Google Admin Operations

After discovering tools, execute them via: RUBE_MULTI_EXECUTE_TOOL: tools: - tool_slug: "<discovered_tool_slug>" arguments: {<schema-compliant arguments>} memory: {} sync_response_to_workbench: false

3. Multi-Step Workflows

For complex workflows involving multiple Google Admin operations: Search for all relevant tools: RUBE_SEARCH_TOOLS with specific use case Execute prerequisite steps first (e.g., fetch before update) Pass data between steps using tool responses Use RUBE_REMOTE_WORKBENCH for bulk operations or data processing

Common Patterns

Search Before Action

Always search for existing resources before creating new ones to avoid duplicates.

Pagination

Many list operations support pagination. Check responses for next_cursor or page_token and continue fetching until exhausted.

Error Handling

Check tool responses for errors before proceeding If a tool fails, verify the connection is still ACTIVE Re-authenticate via RUBE_MANAGE_CONNECTIONS if connection expired

Batch Operations

For bulk operations, use RUBE_REMOTE_WORKBENCH with run_composio_tool() in a loop with ThreadPoolExecutor for parallel execution.

Known Pitfalls

Always search tools first: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via RUBE_SEARCH_TOOLS. Check connection status: Ensure the Google Admin connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. Respect rate limits: If you receive rate limit errors, reduce request frequency and implement backoff. Validate schemas: Always pass strictly schema-compliant arguments. Use RUBE_GET_TOOL_SCHEMAS to load full input schemas when schemaRef is returned instead of input_schema.

Quick Reference