Skip to main content
Agent skill

Googlemeet Automation

Automate Google Meet tasks via Rube MCP (Composio): create Meet spaces, schedule video conferences via Calendar events, manage meeting access. Always search tools first for current schemas.

Get started

Get the complete skill folder, including its scripts and reference files.

This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.

When to use this skill

Use Googlemeet Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Google Meet tasks via Rube MCP (Composio): create Meet spaces, schedule video conferences via Calendar events, manage meeting access. Always search tools first for current schemas.

When not to use it

Skip Googlemeet Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/googlemeet-automation
# Save SKILL.md to ~/.claude/skills/googlemeet-automation/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/googlemeet-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/googlemeet-automation/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Googlemeet Automation skill for this task: Use Googlemeet Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Google Meet Automation via Rube MCP

Create Google Meet video conferences, schedule meetings with Meet links, and manage meeting spaces using Rube MCP (Composio).

**Toolkit docs**: [composio.dev/toolkits/googlemeet](https://composio.dev/toolkits/googlemeet)

## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlemeet` - For scheduling meetings with attendees, also connect the `googlecalendar` toolkit - 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlemeet` 3. Optionally also connect `googlecalendar` for scheduling meetings with calendar events 4. If connection is not ACTIVE, follow the returned auth link to complete setup 5. Confirm connection status shows ACTIVE before running any workflows

## Core Workflows

### 1. Create a Standalone Meet Space Use `GOOGLEMEET_CREATE_MEET` to create a new Google Meet meeting space with optional access configuration. ``` Tool: GOOGLEMEET_CREATE_MEET Description: Creates a new Google Meet space, optionally configuring its access type and entry points. Note: Call RUBE_SEARCH_TOOLS to get the full schema for this tool. ```

### 2. Schedule a Meeting with Google Meet Link Use `GOOGLECALENDAR_CREATE_EVENT` to create a calendar event that automatically generates a Google Meet link (enabled by default). ``` Tool: GOOGLECALENDAR_CREATE_EVENT Parameters: - start_datetime (required): ISO 8601 format (e.g., "2025-01-16T13:00:00") - summary: Meeting title - attendees: List of email addresses - timezone: IANA timezone (e.g., "America/New_York") - event_duration_hour: Duration hours (default: 0) - event_duration_minutes: Duration minutes (default: 30, max: 59) - create_meeting_room: true (default) -- generates Meet link - description: Meeting agenda/notes - location: Physical or virtual location ```

### 3. Find Available Time Slots Use `GOOGLECALENDAR_FIND_FREE_SLOTS` before scheduling to find when participants are available. ``` Tool: GOOGLECALENDAR_FIND_FREE_SLOTS Parameters: - items: List of calendar IDs to check (e.g., ["primary", "[email protected]"]) - time_min: Start of time window (ISO format) - time_max: End of time window (ISO format) - timezone: IANA timezone ```

### 4. Update an Existing Meeting Use `GOOGLECALENDAR_PATCH_EVENT` to modify meeting details, reschedule, or update attendees. ``` Tool: GOOGLECALENDAR_PATCH_EVENT Parameters: - calendar_id (required): Calendar ID (use "primary") - event_id (required): Event ID (from search/list) - summary: Updated title - start_time / end_time: Rescheduled times - attendees: Updated attendee list (replaces existing) - send_updates: Notification preference ("all", "externalOnly", "none") ```

## Common Patterns

- **Quick meeting link**: Use `GOOGLEMEET_CREATE_MEET` for an instant meeting space without a calendar event. - **Scheduled meeting with attendees**: Use `GOOGLECALENDAR_CREATE_EVENT` with `create_meeting_room: true` (default) to create a calendar event with an embedded Meet link. Workspace accounts get a Meet link automatically. - **Check availability first**: Use `GOOGLECALENDAR_FIND_FREE_SLOTS` to find open time slots before scheduling with `GOOGLECALENDAR_CREATE_EVENT`. - **Resolve names to emails**: Use `GMAIL_SEARCH_PEOPLE` (gmail toolkit) to look up email addresses from names before adding attendees. - **Get current time**: Use `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` with a timezone to get the current date/time for scheduling relative to "now".

## Known Pitfalls

- **Attendees must be email addresses**: `GOOGLECALENDAR_CREATE_EVENT` only accepts email addresses for attendees, not names. Use `GMAIL_SEARCH_PEOPLE` to resolve names to emails first. - **Personal Gmail vs Workspace**: The `create_meeting_room` feature works best with Google Workspace accounts. Personal Gmail accounts will gracefully fallback to creating an event without a Meet link. - **start_datetime format**: Must be exact ISO 8601 (e.g., `2025-01-16T13:00:00`). Natural language like "tomorrow at 3pm" is NOT supported. - **Duration limits**: `event_duration_minutes` max is 59. For 1+ hour meetings, use `event_duration_hour` combined with `event_duration_minutes`. - **Timezone is critical**: Always provide `timezone` as a valid IANA identifier (e.g., `America/New_York`). Abbreviations like "EST" or "PST" are NOT valid. - **Event IDs are opaque**: To update or delete events, you must first retrieve the event ID using a search or list tool.

## Quick Reference | Action | Tool | Key Parameters | |--------|------|----------------| | Create Meet space | `GOOGLEMEET_CREATE_MEET` | (see full schema via RUBE_SEARCH_TOOLS) | | Schedule meeting | `GOOGLECALENDAR_CREATE_EVENT` | `start_datetime`, `summary`, `attendees`, `timezone` | | Find free slots | `GOOGLECALENDAR_FIND_FREE_SLOTS` | `items`, `time_min`, `time_max`, `timezone` | | Update meeting | `GOOGLECALENDAR_PATCH_EVENT` | `calendar_id`, `event_id`, `summary`, `start_time` | | Get current time | `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` | `timezone` | | Look up contacts | `GMAIL_SEARCH_PEOPLE` | `query` |

--- *Powered by [Composio](https://composio.dev)*

Intended uses

  • Use Googlemeet Automation when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.