canonical: https://jentic.com/apis/googleapis.com/workspaceevents

# Google Workspace Events API

The Google Workspace Events API lets applications subscribe to change notifications across Google Workspace products such as Chat, Meet, and Drive without polling each domain API individually. Subscriptions register a target Pub/Sub topic that receives events when the configured resource changes, and the API exposes endpoints to create, list, get, update, delete, and reactivate those subscriptions. It is the recommended path for real-time integrations with Workspace and removes the need for legacy push notification channels.

## For AI agents

Subscribe to real-time change events from Google Chat, Meet, and Drive via Pub/Sub. Manage the subscription lifecycle: create, update, reactivate, and delete event streams.

## Scope

Does not handle Chat message sending, Drive content access, Meet conference creation, or event delivery to non-Pub/Sub targets - use for managing Workspace event subscription lifecycles only.

## Capabilities

- Create event subscriptions for Chat, Meet, or Drive resources targeting a Pub/Sub topic
- List subscriptions filtered by event type or target resource
- Update subscription fields such as eventTypes or expireTime
- Reactivate a subscription that has expired or entered a suspended state
- Delete a subscription cleanly when the integration is decommissioned

## Use cases

### Real-time Chat bot or assistant

Build a Chat assistant that reacts the instant a message is posted by subscribing to Chat space events. The Workspace Events API publishes those events to a Pub/Sub topic that the assistant's worker consumes, replacing the older webhook-only model. This decoupling improves reliability - Pub/Sub buffers events even when the worker is briefly down - and gives the bot a single integration surface across spaces.

Example prompt: POST /v1/subscriptions with targetResource=//chat.googleapis.com/spaces/{space} and eventTypes=[google.workspace.chat.message.v1.created], pointing at a Pub/Sub topic, then verify the resulting subscription state is ACTIVE.

### Drive change tracking for compliance

Compliance teams subscribe to Drive change events to feed an audit pipeline that records who created, modified, or shared sensitive documents in near real time. Pub/Sub delivery guarantees and the reactivate endpoint together ensure the pipeline can recover from outages without losing visibility. This replaces the old push-channel based Drive change notifications.

Example prompt: Create a subscription with targetResource set to a Drive resource and eventTypes covering create and update events, then react if the subscription enters SUSPENDED state.

### Meet meeting lifecycle automation

Automate post-meeting workflows by subscribing to Meet conference lifecycle events. When a meeting ends, the subscription publishes an event the worker can use to fetch transcripts, log attendance, or trigger downstream tasks. Centralising this in the Workspace Events API removes the need to glue together separate Calendar and Meet APIs to detect lifecycle changes.

Example prompt: Subscribe to a Meet space with eventTypes covering meeting end, then on each delivered event invoke a downstream task to fetch the meeting transcript.

### Agent-driven event subscription management through Jentic

Workspace administrator agents can manage subscription drift - expired subscriptions, mis-targeted resources - through Jentic without engineers writing client code. The agent searches Jentic for list workspace event subscriptions, reviews the result, and patches or reactivates entries as needed. OAuth tokens stay isolated in your Jentic One instance.

Example prompt: Through Jentic, list subscriptions, identify those in EXPIRED state, and call POST /v1/{+name}:reactivate on each one.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/subscriptions | Create an event subscription |
| GET | /v1/subscriptions | List event subscriptions |
| GET | /v1/{+name} | Get a specific subscription |
| PATCH | /v1/{+name} | Update a subscription |
| DELETE | /v1/{+name} | Delete a subscription |
| POST | /v1/{+name}:reactivate | Reactivate an expired or suspended subscription |

## Key resources

- **subscriptions** — Workspace event subscriptions that route events to a Pub/Sub topic

## Why Jentic

- **Setup:** Wiring the Google Workspace Events API by hand means setting up OAuth 2.0 with Workspace scopes, refreshing access tokens, and matching subscription lifecycle calls against the workspaceevents.googleapis.com host. Through Jentic you install once, import the Google Workspace Events API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** The Google Workspace Events API puts the subscription in the URL path (/v1/{name}), so a rule can pin your agent to one subscription: it can read and reactivate that subscription and nothing else. You choose the operations it may call, so deleting subscriptions is not included unless you add it.
- **Credential handling:** Your Workspace OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. Its refresh token never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'subscribe to chat events' or 'list workspace subscriptions', and Jentic returns the subscriptions create or list operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Google Chat API** — Domain API for Chat spaces, messages, and memberships
- **Google Drive API** — Read and write file metadata and content for events delivered by Workspace Events
- **Pub/Sub API** — Required event delivery target for Workspace Events subscriptions

## FAQ

### What authentication does the Workspace Events API use?

OAuth 2.0 (Oauth2 and Oauth2c schemes) with Workspace-specific scopes such as chat.memberships and drive.metadata.readonly depending on the targetResource. Through Jentic the OAuth credentials are stored encrypted and short-lived access tokens are minted at execution time.

### Which Workspace products can I subscribe to?

The targetResource accepts Chat (spaces and memberships), Drive (files and shared drives), and Meet (spaces and conferences) resources. The supported eventTypes per product are documented in the Workspace Events docs. Other Workspace surfaces such as Calendar use their own native push channels for now.

### What are the rate limits for the Workspace Events API?

Per-project quotas on subscription create, list, and update calls are configured in the Cloud Console under APIs and Services. Event delivery itself is metered separately by Pub/Sub on the receiving topic, so the practical limit is your Pub/Sub publish-side quota in the destination project.

### How do I subscribe to Chat messages through Jentic?

Search Jentic for subscribe to chat space messages, load the schema for POST /v1/subscriptions, and execute it with targetResource pointing at the Chat space and eventTypes including google.workspace.chat.message.v1.created. The endpoint expects a Pub/Sub topic the project can publish to.

### What happens when a subscription expires?

Subscriptions have an expireTime; once reached, the subscription stops delivering events and enters an expired state. Call POST /v1/{+name}:reactivate to bring it back online and update the expireTime, or delete it via DELETE /v1/{+name} if it is no longer needed.

### Can I limit what my agent is allowed to do with the Google Workspace Events API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and this API puts the subscription in the URL path (/v1/{name}), so a rule can pin the agent to a single subscription. You choose which operations it may call, so you can allow it to only get and reactivate a subscription while withholding delete or update. The Workspace OAuth credential stays in your instance and is injected only when a permitted call runs, so the agent never sees the refresh token.