Google Workspace Events API

Name: Google Workspace Events API API
Brand: Google Workspace Events API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationoauth26 EndpointsREST

For 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.

Quickstart

Get started with Google Workspace Events API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"subscribe to google workspace events"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google Workspace Events API API.

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

GET STARTED

Start building with Google Workspace Events API API

Explore with Jentic

View OpenAPI Document

Use for: Subscribe to messages posted in a Google Chat space, List all event subscriptions for a Drive resource, Update the event types on an existing Workspace subscription, Reactivate a suspended Workspace event subscription

Not supported: 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.

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.

Use Cases

Patterns agents use Google Workspace Events API API for, with concrete tasks.

★ 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.

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.

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.

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 the Jentic vault.

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

Key Endpoints

6 endpoints — 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.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OAuth 2.0 client credentials with Workspace scopes are stored encrypted in the Jentic vault. Agents receive scoped access tokens; refresh tokens never enter the model context.

Intent-based discovery

Agents query Jentic with intents like subscribe to chat events or list workspace subscriptions and Jentic returns the subscriptions create or list operation with its input schema.

Time to first call

Direct integration: 1 day to set up OAuth, Pub/Sub topic, IAM, and subscription. Through Jentic: under an hour once the Pub/Sub topic exists.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Chat API

Domain API for Chat spaces, messages, and memberships

Use Workspace Events to subscribe and Chat to act on the events delivered.

Complementary

Google Drive API

Read and write file metadata and content for events delivered by Workspace Events

Subscribe through Workspace Events; resolve the affected file through Drive when an event arrives.

Complementary

Pub/Sub API

Required event delivery target for Workspace Events subscriptions

Provision a Pub/Sub topic before creating a Workspace Events subscription so events have somewhere to go.

FAQs

Specific to using Google Workspace Events API API through Jentic.

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.