IntegrationsGoogle Chat
Google Workspace™ is not one destination. Google Chat™ apps, Google Docs™ and Gmail™ add-ons, Google Drive™ integrations and Gemini™ extensions have different manifests, different reviews and different failure modes. An adapter that treats "Google" as one thing cannot tell you what it actually installed.
Your AI, MCP server or API
Their workspace and approved access
Their entitled capabilities and version
Validation, health and the next action
Available today
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
What a forward deployed engineer does by hand today.
Meetext configures and publishes one Chat app through Google Workspace™ Marketplace. The customer installs that app for their domain or personal account, then presents a single-use code in the Chat space that should belong to this environment.
The person whose calendar decides your go-live date.
A Workspace super admin for domain-wide installation, or an individual user for a personal install. Meetext records which kind occurred so a personal test is never presented as a domain-wide rollout.
Whose identity the product acts as, and where that grant lives.
The app authenticates as itself with Meetext's service account and the chat.bot scope. There is no user OAuth grant, refresh token or consent screen. Domain-wide delegation is deliberately not used because answering as the app does not require impersonating anybody in the customer's domain.
The repeatable half, turned into software.
The Marketplace app, service-account credential, signed-event verification, and the single-use code that binds one Chat space to exactly one customer environment. Events resolve by space, so two personal installs under gmail.com cannot cross customer boundaries.
The half that is theirs and should stay theirs.
Installation and removal of the app, plus the Admin console policies that decide who can use it. Removing one customer installation does not revoke Meetext's shared app credential or interrupt another customer.
How capabilities map onto what the platform will let you do.
Exactly chat.bot, held by the app rather than granted by a customer. User scopes such as chat.messages and chat.spaces are not requested. Add-on, Drive and Gemini surfaces are refused at deploy time instead of silently widening access.
What has to execute before anyone is told it works.
Google's signature and project audience are verified before an event can claim anything. The app token, installed space, capability listing and a real execution are then checked, and the one-time code cannot be replayed.
Rotation, expiry, revocation, and who notices first.
Meetext mints short-lived app tokens from one service-account key. There is no customer refresh token to expire or reconnect. Rotating that key is a platform operation because it affects every Google Chat™ installation.
What happens to this customer when you ship version four.
The capability package is frozen per customer, as everywhere. The shared Marketplace listing and Chat app configuration are a separate platform-wide version that Meetext operates for every customer.
What actually goes wrong, named rather than generalised.
The Marketplace listing is not visible to the customer's domain. Google cannot reach the webhook. The service-account key was rotated without updating Meetext, or the inbound event has the wrong project audience. Non-Chat surfaces are refused before installation.
How you learn it broke without the customer telling you.
Outbound health proves the app token can still read the installed space. Inbound events record the public address Google actually reached, so a stale Cloud console webhook after a cutover is reported instead of being hidden by a healthy outbound probe.
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
Available for customer deployments, with customer-scoped authorization, validation and lifecycle management.
Google Chat™, Google Workspace™, Google Docs™, Gmail™, Google Drive™, and Gemini™ are trademarks of Google LLC.
Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.
