google-drive-upload-fileAtomic node skill to upload a file to Google Drive using the gog CLI.
Install via ClawdBot CLI:
clawdbot install zvirb/google-drive-upload-fileGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 5, 2026
Creative agencies generate final design files, reports, and media assets that must be uploaded to a shared Google Drive folder for client access. The agent detects completed files in a local output directory and runs `gog drive upload` to archive them automatically. This eliminates manual drag-and-drop steps and ensures clients always see the latest versions.
A small SaaS team dumps nightly database backups to a local server and needs them stored off-site in Google Drive for disaster recovery. A cron job invokes the agent skill to upload each dump and capture the returned Drive ID for logging. This provides a verifiable, timestamped off-site backup chain without cloud-specific SDK code.
Construction site supervisors complete daily inspection reports as local PDFs on tablets. When connectivity is restored, the agent uploads each report to a project-specific Google Drive folder. Project managers then review consolidated reports without needing supervisors to manually sync devices.
University labs produce instrument output files that researchers need to share with collaborators across institutions. The agent watches a local staging folder and uploads new datasets to a shared Google Drive, returning file IDs that get recorded in the lab's metadata catalog. This standardizes data handoff and reduces email attachments.
Independent podcasters export finished audio episodes and show notes locally before distribution. The agent uploads each episode to a Google Drive folder shared with their editor and distributor, returning the Drive ID for the publishing checklist. This keeps the production pipeline moving without manual cloud uploads.
MSPs deploy this skill inside client environments to automate file movement to Google Drive as part of broader workflow automation retainers. It replaces brittle custom scripts with a standardized CLI-based node that is easy to audit and maintain. Revenue comes from monthly managed service contracts and per-automation setup fees.
A no-code automation platform bundles this skill as a Google Drive connector, letting non-technical users add cloud upload steps to their workflows. The platform handles authentication, retries, and logging around the atomic upload command. Revenue is generated through tiered subscription plans based on workflow execution volume.
A vertical SaaS product for regulated industries uses this skill to enforce immutable archival of documents to Google Drive with audit trails. Customers pay for guaranteed retention, access controls, and compliance reporting layered on top of simple uploads. Revenue comes from per-seat licenses and storage-based pricing.
💬 Integration Tip
Ensure the `gog` CLI is installed and authenticated (OAuth) in every environment where the agent runs, and always parse the returned JSON to capture the Drive file ID for downstream steps.
Scored Oct 5, 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).