Google Workspace is not one destination. Chat apps, Docs and Gmail add-ons, 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.
Available, with a named limit
Google Chat ships. The Docs and Gmail add-on, Drive and Gemini surfaces are declared by the adapter and refused at deploy time rather than failing later.
What a forward deployed engineer does by hand today.
The vendor configures a Chat app in a Google Cloud project, publishes it to their domain or to the Marketplace, and the customer installs it into their own Workspace domain. Marketplace review is a separate calendar.
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 reports a personal Google account rather than silently accepting it, because a deployment that works for one person is not a deployment.
Whose identity the product acts as, and where that grant lives.
Ordinary three-legged OAuth against the installing user. Domain-wide delegation is deliberately not used: it would let Meetext act as any user in the customer's domain, which is more access than any capability needs and the single hardest thing to get through a security review.
The repeatable half, turned into software.
The Chat surface end to end, recording the Workspace domain so two customers are never confused, and refusing surfaces that are declared but not implemented rather than quietly behaving like Chat.
The half that is theirs and should stay theirs.
Domain installation and the admin console policies around it. Uninstalling revokes the grant at Google, not just Meetext's copy of it.
How capabilities map onto what the platform will let you do.
Chat scopes only. A capability that would need Drive or Gmail access is refused at deploy time, because an installation that quietly targets the wrong surface is worse than one that will not start.
What has to execute before anyone is told it works.
Authentication, domain identification, capability listing and a real execution, the same as everywhere else. The Workspace domain is part of what gets validated, not an assumption.
Rotation, expiry, revocation, and who notices first.
Google refresh tokens, held per environment. Revocation at Google disconnects the environment and asks the customer to reinstall, which is the only thing that can fix it.
What happens to this customer when you ship version four.
Frozen package per customer, as everywhere. Marketplace listing versions are a separate axis and are the vendor's to manage.
What actually goes wrong, named rather than generalised.
A personal Gmail account used where a Workspace domain was expected. A surface that is not Chat, which is refused rather than attempted. Marketplace review delays, which are nobody's fault and still your go-live date.
How you learn it broke without the customer telling you.
The same three layers, with the Workspace domain recorded on the environment so an incident names which customer domain it belongs to.
The adapter is real and something is incomplete, either a part of the destination or real-provider proof for part of the lifecycle. The gap is stated on the page rather than discovered during an evaluation.
The adapter ships with a named gap. Not yet exercised with real provider credentials: authorization, installation, execution, refresh and reconnect, validation, failure handling. Google Chat ships. The Docs and Gmail add-on, Drive and Gemini surfaces are declared by the adapter and refused at deploy time rather than failing later.
Google Chat ships. The Docs and Gmail add-on, Drive and Gemini surfaces are declared by the adapter and refused at deploy time rather than failing later.
Lifecycle coverage
This label is generated from a proof registry in the deployment code, not written on this page. A destination cannot read Available until every lifecycle path above has actually run against the real provider, and a test refuses the claim without dated evidence.
Connect a source, publish, and send one link. Your next enterprise customer installs itself.
2 customer environments free, forever. No card required.
