xferops-gogGoogle Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Install via ClawdBot CLI:
clawdbot install parker-xferops/xferops-gogGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://gogcli.shAudited Apr 16, 2026 · audit v1.0
Generated Mar 21, 2026
Marketing teams can use gog to automate sending personalized email campaigns, track responses via search, and manage drafts. It enables bulk email operations with HTML formatting and attachment handling, streamlining outreach efforts.
Project managers can schedule and update team meetings across Google Calendar, using color-coding for priority and status. This helps in organizing events efficiently and maintaining visibility in distributed work environments.
Data analysts can automate data updates and retrieval from Google Sheets, using gog to append, clear, or fetch data in JSON format. This supports real-time reporting and integration with other tools for business intelligence.
Content creators can export Google Docs to various formats or view content directly via command line, facilitating batch processing and backup. This is useful for managing documentation and collaborative writing projects.
Sales teams can list and manage Google Contacts through gog, enabling quick access to contact details for outreach. It integrates with email and calendar functions to support CRM activities and follow-ups.
Offer a subscription-based service that integrates gog with existing business workflows, providing automated email, calendar, and document management. Revenue comes from monthly fees for API access and support.
Provide consulting services to help businesses set up and customize gog for specific needs, such as automated reporting or campaign management. Revenue is generated through project-based fees and ongoing maintenance contracts.
Develop training courses and certifications for using gog in enterprise environments, targeting IT professionals and teams. Revenue streams include course fees, certification exams, and workshop materials.
💬 Integration Tip
Set GOG_ACCOUNT environment variable to avoid repeating --account flags, and use --json with --no-input for scripting to ensure reliable automation.
Scored Jun 19, 2026
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.
Query Google Places for text search, place details, resolve, reviews, or scriptable JSON via goplaces.
Google Contacts API integration with managed OAuth. Manage contacts, contact groups, and search your address book. Use this skill when users want to create, read, update, or delete contacts, manage contact groups, or search for people in their Google account. 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 Contacts connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Contacts 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 Contacts examples; they add no Google Contacts capability - Google Contacts is not an event source, a trigger cannot read Google Contacts 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).