Gws Events Renew
Renew or bulk-reactivate Google Workspace Events subscriptions with the gws CLI before webhooks silently stop firing.
Overview
gws-events-renew is an agent skill for the Operate phase that renews or reactivates Google Workspace Events subscriptions using the gws events +renew CLI.
Install
npx skills add https://github.com/googleworkspace/cli --skill gws-events-renewWhat is this skill?
- Renews a single subscription via --name subscriptions/SUB_ID
- Bulk renew with --all and a --within window (default 1h, supports 30m, 2d, etc.)
- Documents pairing --all with cron for keep-alive automation
- Requires gws-shared SKILL.md for auth and global security rules
- CLI help entry point: gws events +renew --help
- Default --within window is 1h when using --all
- Skill metadata version 0.22.5 in frontmatter
Adoption & trust: 15.8k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Workspace Events subscriptions are near expiry or already inactive, so downstream automations will miss events without a manual or scheduled renew step.
Who is it for?
Builders already on the gws CLI who maintain Workspace webhook or event subscriptions and need a documented renew command for agents or cron.
Skip if: Teams not using Google Workspace Events, or anyone who has not yet installed gws and configured auth via gws-shared.
When should I use this skill?
User needs to renew or reactivate Google Workspace Events subscriptions with gws events +renew.
What do I get? / Deliverables
Subscriptions are reactivated for a named ID or for all IDs expiring within the chosen --within window, ready for cron-driven keep-alive runs.
- Executed gws events +renew command for one or all expiring subscriptions
- Cron-ready renewal command snippet with --all and --within
Recommended Skills
Journey fit
Subscription renewal is ongoing production hygiene—subscriptions expire without periodic renew—so the canonical shelf is operate/infra. Workspace Events subscriptions are infrastructure contracts tied to automation and monitoring pipelines, not feature build work.
How it compares
CLI integration skill for subscription TTL maintenance—not an MCP server and not the initial gws-events subscribe flow.
Common Questions / FAQ
Who is gws-events-renew for?
Solo builders and ops-minded indies running Google Workspace automations with the gws command-line tool.
When should I use gws-events-renew?
During operate/infra when subscriptions approach expiration, after deploys that touch event pipelines, or when setting up cron jobs that call gws events +renew --all.
Is gws-events-renew safe to install?
It instructs agents to run authenticated gws commands; review the Security Audits panel on this page and follow gws-shared auth rules before granting network or secret access.
Workflow Chain
Requires first: gws shared
Then invoke: gws events
SKILL.md
READMESKILL.md - Gws Events Renew
# events +renew > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. Renew/reactivate Workspace Events subscriptions ## Usage ```bash gws events +renew ``` ## Flags | Flag | Required | Default | Description | |------|----------|---------|-------------| | `--name` | — | — | Subscription name to reactivate (e.g., subscriptions/SUB_ID) | | `--all` | — | — | Renew all subscriptions expiring within --within window | | `--within` | — | 1h | Time window for --all (e.g., 1h, 30m, 2d) | ## Examples ```bash gws events +renew --name subscriptions/SUB_ID gws events +renew --all --within 2d ``` ## Tips - Subscriptions expire if not renewed periodically. - Use --all with a cron job to keep subscriptions alive. ## See Also - [gws-shared](../gws-shared/SKILL.md) — Global flags and auth - [gws-events](../gws-events/SKILL.md) — All subscribe to google workspace events commands