clawbus-google-workspace

Manage Google Calendar, Google Drive, and Google Sheets through MyBrandMetrics-connected data sources and the local Google Workspace CLI (gws).

Use this skill when the user wants to work with Calendar events, Drive files, or Google Sheets data from chat.

Website: https://www.clawbus.com/
MyBrandMetrics API: https://mybrandmetrics.com/

Core Capabilities

Requirements

• A Google account.
• Access to MyBrandMetrics.
• The needed Google data sources connected in MyBrandMetrics: Google Calendar, Google Drive, or Google Sheets.
• A MyBrandMetrics API key.
• The local Google Workspace CLI (gws) installed.
• A clear task, such as a calendar action, Drive file operation, or Google Sheets read/write request.

Setup Flow

1. Open https://mybrandmetrics.com/ and sign in with Google.
2. In MyBrandMetrics, open Data sources.
3. Connect the data sources required for the workflow: Google Calendar for calendar tasks, Google Drive for file tasks, and Google Sheets for spreadsheet tasks.
4. Wait until the selected MyBrandMetrics connections are ready.
5. Get the MyBrandMetrics API key.
6. Install the clawbus-google-workspace skill.
7. Install the Google Workspace CLI if gws is not already available.
8. Start the Google Workspace workflow with natural-language instructions.

How It Works

The wrapper script uses the MyBrandMetrics API key with the configured MyBrandMetrics token service to get a short-lived Google session for the selected data source, then runs the matching gws command.

For local script usage, provide the MyBrandMetrics API key with one of these options:

export GWS_SKILL_API_KEY="YOUR_MYBRANDMETRICS_API_KEY"

or:

echo "YOUR_MYBRANDMETRICS_API_KEY" > ~/.google_workspace_api_key

Do not paste short-lived Google session values into chat, files, examples, or logs. The wrapper handles them for the current command.

The runtime should provide the token service location through GWS_TOKEN_URL.

Example Requests

Natural-language examples:

Show my upcoming Google Calendar events for this week.

Upload this report to Google Drive and put it in the campaign folder.

Read rows A1:D20 from this Google Sheet and summarize the status column.

Append these rows to the sales tracker sheet after I confirm the target range.

Command Reference

Run Google Workspace commands through the wrapper:

python3 scripts/gws_wrapper.py \x3Cservice> \x3Ccommand> [args]

Useful patterns:

python3 scripts/gws_wrapper.py calendar events list
python3 scripts/gws_wrapper.py calendar events create --title "Meeting" --start "2026-05-15T10:00:00Z"
python3 scripts/gws_wrapper.py drive ls
python3 scripts/gws_wrapper.py drive upload \x3Cfilename>
python3 scripts/gws_wrapper.py sheets get \x3Cspreadsheet-id> \x3Crange>
python3 scripts/gws_wrapper.py sheets append \x3Cspreadsheet-id> \x3Crange> --data '[[1, 2], [3, 4]]'

Review Before Changes

Before creating, updating, uploading, appending, or deleting anything, confirm:

• the connected Google account or workspace;
• the calendar, Drive folder, file, spreadsheet, sheet, or range;
• the exact data to write or upload;
• whether the action changes existing content.

Troubleshooting

• If MyBrandMetrics is not ready, reconnect the needed data source in MyBrandMetrics and try again: Google Calendar, Google Drive, or Google Sheets.
• If the wrapper asks for a MyBrandMetrics API key, set GWS_SKILL_API_KEY or save the key to ~/.google_workspace_api_key.
• If the wrapper asks for the token service, set GWS_TOKEN_URL in the runtime environment.
• If gws is not found, run scripts/install_gws.sh or install the Google Workspace CLI manually.
• If a sheet or Drive file cannot be found, check that the connected Google account has access.