Google Workspace Events API
Browse all Google APIs39
AI ReadinessNon-Ready (F)39/100
Official vendor OpenAPI document · agent-readyProductivityCollaborationoauth26 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.
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.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fworkspaceevents" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fworkspaceevents" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Reactivate a subscription that has expired or entered a suspended state
Delete a subscription cleanly when the integration is decommissioned
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
/v1/{+name}:reactivate
Reactivate an expired or suspended subscription
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
Google Workspace Events API
- Non-Ready (F)39/100
72
Foundational Compliance56
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability63
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
88%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
67%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 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.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED