Choose theme
AI Resources
Google Workspace CLI
Google Workspace CLI, or gws, provides commands for Google Workspace APIs, including Drive, Gmail, Calendar, Sheets, Docs, and Chat. Scripts and AI agents can use its structured JSON responses.
The repository notes that this is not an officially supported Google product and remains under development toward v1.0. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
Workspace APIs in the terminal
The repository demonstrates listing Drive files, creating a spreadsheet, and preparing a Chat message through gws.
Why it stands out
Commands built from API descriptions
gws reads Google's Discovery documents to build commands from service resources and methods.
Availability
Binaries and source
Prebuilt releases, an npm installation path, and source-build instructions are available in the repository.
Why it matters
What makes it useful
A script can list Drive files or create a spreadsheet without assembling the HTTP request itself. The README gives command examples for those tasks and returns JSON that another program can read.
What to know
Where it fits
The command hierarchy follows Workspace API services, resources, and methods. Authentication connects it to a Google account or other configured credentials; a script or agent decides which operations to request.
Notable points
What stands out
gws schema shows a method's request and response shape, while --dry-run previews a request. The README demonstrates preparing a Chat message with --dry-run, so the request can be inspected before sending.
Before using
What to review
OAuth setup and service permissions are part of the workflow; installing the binary does not grant Workspace access.
gws auth setup requires gcloud; the repository also documents manual OAuth configuration.
For an unverified OAuth app, the README recommends selecting individual services rather than its broad recommended scope preset.
The project warns that commands may change before v1.0.
Reader fit
Who may find it relevant
People who already use scripts or agents to work with Google services.
Developers who want command help, schemas, and JSON around Workspace API operations.
It assumes comfort with terminal commands and authentication setup.
Editorial note
Why LifeHubber lists it
A Drive listing can span several API pages. With --page-all, gws emits one JSON line per page rather than one combined JSON document. That detail matters when feeding a file inventory into another script: its input parser needs to handle the page stream.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
What to explore next
Decide how much Workspace access the automation should receive.
Google Workspace CLI exposes Workspace operations to people and AI agents through structured commands and bundled skills. These next steps cover a broader integration layer, skill inspection, and the human controls around actions that can change files, messages, or calendars.
More in Ecosystem
Keep browsing this category
Explore more AI ecosystem resources.
Laya
NandhaKishorM/laya
An early Apache-2.0 model family and Python runtime for bounded choice, score, and yes-or-no decisions, with English, multilingual, and task-specialized checkpoints plus a router that selects between them.
CLM
Contrastive-LM/CLM
An Apache-2.0 contrastive model and local server for typed decisions and candidate ranking, with separate state and action embeddings, reusable candidate caches, a browser playground, public reference heads, and fine-tuning tools.
liteparse
run-llama/liteparse
A local parser for PDFs, Office files, and images with Markdown, JSON, and text output, complexity detection, several runtimes, bounding boxes, OCR flexibility, and screenshots.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.