google-drive-download-fileAtomic node skill to download a file from Google Drive using the gog CLI.
Install via ClawdBot CLI:
clawdbot install zvirb/google-drive-download-fileGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 5, 2026
A sales operations team uses this skill to automatically fetch daily CSV exports from a shared Google Drive folder and load them into their CRM or analytics dashboard. This eliminates manual downloading and ensures up-to-date data for morning meetings.
A law firm employs the skill to download client contracts and legal filings from Google Drive to a secure local server for long-term retention and compliance auditing. It integrates with a document management system to trigger workflows upon download.
An online learning platform uses the skill to download video lectures and PDFs from Google Drive to a content delivery network. This automates the publishing process when instructors upload new materials.
A clinic uses the skill to securely download patient reports and imaging files from Google Drive to their electronic health record (EHR) system. It ensures timely access to medical data while maintaining HIPAA compliance through controlled local storage.
A media production company uses the skill to download raw footage, graphics, and audio files from Google Drive to editing workstations. This streamlines post-production workflows by automating asset retrieval.
Offer this skill as an add-on feature within a SaaS platform that manages cloud storage. Users can automate file downloads to their local systems or other cloud services, enhancing the platform's integration capabilities.
Provide a service where businesses outsource their file transfer and synchronization needs. The skill is used as a building block to create custom automation pipelines, reducing manual effort and errors.
License the skill as a pre-built component for developers building AI agents or automation tools. It saves development time and ensures reliable Google Drive integration.
💬 Integration Tip
Ensure the gog CLI is installed and authenticated with proper Google Drive API credentials. Handle errors gracefully by checking the CLI exit code and logging failures for debugging.
Scored Apr 27, 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).