Skip to main content
command

gws-events-subscribe — Claude Code command: events and setup

Subscribe to Google Workspace events and receive them as an NDJSON stream. Use it to pull Chat events or save each event in its own JSON file.

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command google-workspace/gws-events-subscribe
Open on GitHub

What gws-events-subscribe does

The command runs gws events +subscribe with options for a Workspace resource, event types, and a GCP project. It pulls messages from Pub/Sub. Use --once for a single pull, --no-ack to leave messages unacknowledged, or --output-dir to write events to separate files.

Install the Google Workspace CLI (gws) and configure authentication first; check it with gws auth status. The command also requires ../gws-shared/SKILL.md; if that file is missing, gws generate-skills can create it. This is a write command, so confirm with the user before running it. Without gws, the subscription cannot run.

What it helps with

  • subscribe to events from a Workspace resource
  • pull events through Pub/Sub
  • fetch one batch and exit
  • write each event to a separate JSON file
  • keep Pub/Sub resources for reconnection

Example prompts for the agent

  • Subscribe to Chat space //chat.googleapis.com/spaces/SPACE for google.workspace.chat.message.v1.created events in project my-project.
  • Pull messages once from projects/p/subscriptions/my-sub, then exit.
  • Save events to ./events and remove the Pub/Sub resources created by the command when it exits.

How to install gws-events-subscribe

1claude-code-templates

npx claude-code-templates@latest --command google-workspace/gws-events-subscribe

2Manually: put the files in place

.claude/commands/gws-events-subscribe.md

Call it with /gws-events-subscribe. For all projects use ~/.claude/commands/

Questions about gws-events-subscribe

How do I install gws-events-subscribe in Claude Code?

Run npx claude-code-templates@latest --command google-workspace/gws-events-subscribe. The command file is .claude/commands/gws-events-subscribe.md.

What does gws-events-subscribe do?

It subscribes to Google Workspace events and streams them as NDJSON. You can read from an existing Pub/Sub subscription or write each event to a separate JSON file.

What do I need before running gws-events-subscribe?

Install the Google Workspace CLI (gws), configure authentication, and have ../gws-shared/SKILL.md available. Check authentication with gws auth status.

Source text

gws-events-subscribe.md · MIT
---
allowed-tools: Bash, Read, Write, Edit
argument-hint: "[resource] [method] [flags]"
description: "Google Workspace Events: Subscribe to Workspace events and stream them as NDJSON."
---

# Google Workspace Events Subscribe

Execute Google Workspace Events Subscribe operations: $ARGUMENTS

## Prerequisites

- Google Workspace CLI (`gws`) must be installed
- Authentication configured: Run `gws auth status` to verify
- Review `gws events-subscribe --help` for all available commands

## Available Resources and Methods

# events +subscribe

> **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it.

Subscribe to Workspace events and stream them as NDJSON

## Usage

```bash
gws events +subscribe
```

## Flags

| Flag | Required | Default | Description |
|------|----------|---------|-------------|
| `--target` | — | — | Workspace resource URI (e.g., //chat.googleapis.com/spaces/SPACE_ID) |
| `--event-types` | — | — | Comma-separated CloudEvents types to subscribe to |
| `--project` | — | — | GCP project ID for Pub/Sub resources |
| `--subscription` | — | — | Existing Pub/Sub subscription name (skip setup) |
| `--max-messages` | — | 10 | Max messages per pull batch (default: 10) |
| `--poll-interval` | — | 5 | Seconds between pulls (default: 5) |
| `--once` | — | — | Pull once and exit |
| `--cleanup` | — | — | Delete created Pub/Sub resources on exit |
| `--no-ack` | — | — | Don't auto-acknowledge messages |
| `--output-dir` | — | — | Write each event to a separate JSON file in this directory |

## Examples

```bash
gws events +subscribe --target '//chat.googleapis.com/spaces/SPACE' --event-types 'google.workspace.chat.message.v1.created' --project my-project
gws events +subscribe --subscription projects/p/subscriptions/my-sub --once
gws events +subscribe ... --cleanup --output-dir ./events
```

## Tips

- Without --cleanup, Pub/Sub resources persist for reconnection.
- Press Ctrl-C to stop gracefully.

> [!CAUTION]
> This is a **write** command — confirm with the user before executing.

## 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

## Usage

```bash
# List available resources and methods
gws events-subscribe --help

# Inspect method schema before calling
gws schema events-subscribe.<resource>.<method>

# Execute command with arguments
gws events-subscribe $ARGUMENTS
```

## Task

Execute the requested Events Subscribe operation: $ARGUMENTS

1. **Verify Prerequisites**
   - Check `gws` is installed: `gws --version`
   - Verify authentication: `gws auth status`
   - Review available commands: `gws events-subscribe --help`

2. **Inspect Method Schema**
   - Before calling any method, inspect its parameters
   - Use `gws schema` to understand required fields
   - Review parameter types and constraints

3. **Execute Operation**
   - Build command with appropriate flags
   - Use `--params` for query/path parameters
   - Use `--json` for request body
   - Handle pagination with `--max-results` or `--page-token`

4. **Error Handling**
   - Check command output for errors
   - Review API quotas and rate limits
   - Handle authentication issues
   - Retry transient failures

---

**License**: Apache License 2.0
**Source**: [Google Workspace CLI](https://github.com/googleworkspace/cli)
**Original Skill**: `gws-events-subscribe`

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

All slash commands for Cloud: AWS, Azure, GCP →

From the same set804

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor