Google Workspace Events API

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

✓ Official Vendor SpecProductivityCollaborationoauth26 Endpoints

Install Jentic One Beta

Connect the Google Workspace Events API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Workspace Events API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Google Workspace Events 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

GET STARTED

Start building with Google Workspace Events API

Explore with Jentic

View OpenAPI Document

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.

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.

Use Cases

Patterns agents use Google Workspace Events 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 your Jentic One instance.

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 Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Google Workspace Events 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.

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.

Google Workspace Events API

Connect the Google Workspace Events API to your agent

Capabilities

Start building with Google Workspace Events API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs