Skip to content
threada Docs

Google Workspace Marketplace

This guide defines the Google Workspace Marketplace path after Slack Marketplace, the Zapier public integration scaffold, and Microsoft Teams Store scoping. It is a design and launch-control document, not evidence that a Google Workspace Marketplace app has been built or approved.

Current Status

Google Workspace Marketplace is planned as a public store follow-on, while the Google Chat-to-WorkItem runtime intake path is implemented as a tenant-bound integration. Threada already has an email WorkItem source channel, Gmail runtime intake and reply sync code, a governed gmail_create_draft action payload, Google Chat notification plumbing, and a Google Chat webhook path for creating governed WorkItems. A private Google Workspace Marketplace configuration scaffold now lives at packages/google-workspace-marketplace-app for the v1 Google Chat-to-WorkItem surface. Do not treat that scaffold as a public Marketplace app: no Google Cloud project, Chat API configuration, OAuth consent review evidence, or Marketplace SDK listing has been validated from this repository yet. Public setup and support documentation now lives at Google Workspace setup and support. Studio exposes https://studio.threada.ai/integrations/google-workspace/install to preload the Google Workspace runtime integration kind and connector preset for a pack.

Do not submit or market a public Google Workspace Marketplace listing until the chosen Google app integration is built, installed in a reviewer-safe test tenant, validated end to end, configured in the Marketplace SDK, and accepted by Google review.

The existing Gmail and Google Chat runtime paths remain tenant-specific integration work. They should not be described as the public Google Workspace Marketplace app until Google approves the public listing.

The enterprise-safe first package should be a Google Chat-to-WorkItem app. It is closest to the Slack and Teams review paths: capture a user request from a chat surface, route it through Threada tenant mapping, and create a governed WorkItem without requesting broad Gmail or Drive data access.

A Gmail or broader Workspace add-on can follow only after the add-on UI, OAuth scopes, domain-wide install behavior, reviewer account path, and any sensitive or restricted-scope review evidence are ready. The live gmail_create_draft payload is useful implementation evidence, but it is not by itself a Marketplace add-on.

Positioning

Threada for Google Workspace should let Workspace users capture requests into governed Threada WorkItems without bypassing Threada policy, approval, idempotency, and audit controls.

The narrow v1 app should stay focused:

  • Create a governed WorkItem from a Google Chat message, slash command, card action, or other Google-supported chat entrypoint.
  • Bind the installed Google Workspace domain, Chat space, or user context to a Threada tenant, pack, queue, or workspace mapping.
  • Show clear success or setup-required feedback inside Google Chat.
  • Provide public setup/support documentation that explains least-privilege scopes, data handling, uninstall, and disconnect behavior. Use https://docs.threada.ai/integrations/google-workspace-setup/ for reviewer setup/support URL fields.

The v1 app must not claim that Google Workspace can execute third-party actions through Threada. Direct external execution remains inside Threada’s governed Work, Studio, MCP, A2A, or first-party runtime paths.

Source Of Truth

Do not duplicate request or response schemas in this document. Public WorkItem shape and accepted channel labels are documented in Threada Public API and its generated OpenAPI artifact at /openapi/public-api.openapi.yaml.

Runtime source truth for current Gmail and Google Chat support lives in the domain runtime catalog, runtime automation service, BFF webhook route, and notifications service. The private configuration scaffold is the source of truth for the current Google Chat app configuration, Marketplace listing draft inputs, least-privilege OAuth scope posture, and local submission-readiness checks. Public user setup/support copy lives in Google Workspace setup and support. The Google Cloud project, OAuth consent screen, Marketplace SDK configuration, Google Chat app configuration, review output, and reviewer setup notes must become the source of truth for the public listing once they exist.

App Surface

Create WorkItem From Google Chat

The first reviewable capability should create a Threada WorkItem from Google Chat context. The implementation can use a slash command, app command, card action, message interaction, or another Google-supported Chat entrypoint, but the reviewer journey must be testable without customer data.

Inputs should map to the live WorkItem fields for subject, channel, channel ID, thread/source metadata, contact details where allowed, tags, and initial message. Use an existing accepted channel label such as custom or api until the public API contract includes a dedicated Google Chat label. Preserve Google Chat provenance in channel IDs, tags, or source metadata rather than inventing a new public API enum value in docs.

Outputs must give the Google Chat user a clear success or setup-required state and a safe Threada Work URL when one can be generated. Do not return only a generic success message; Marketplace reviewers need to see the actual user journey.

Google Chat-specific review behavior must be implemented before submission:

  • The Chat app can be added to direct messages and spaces, and is discoverable through the Chat app install surfaces required by Google review.
  • The app sends a welcome message when a user starts a direct message or the app is added to a space.
  • The app supports a Help command that is distinct from the welcome message and explains how to create a WorkItem, complete setup, and get support.
  • The app always responds when addressed in a direct message or mentioned in a space, including setup-required and failure states.
  • Space interactions require an @mention so the app does not respond to every message in a space.
  • If a response takes more than two seconds, the app sends a delay message and later completes the visible user journey.
  • Any notification behavior includes a user-visible way to turn notifications off.
  • Add/remove behavior in spaces is testable, and external URLs are production URLs rather than staging or development URLs.
  • Cards and messages follow Google Chat formatting requirements and use clear, concise copy.

Setup And Tenant Mapping

The app must bind an installed Google Workspace domain, Google Chat space, or user context to a Threada tenant, pack, queue, or workspace mapping before claiming production readiness. If setup is incomplete, the app should show a clear setup-required response instead of silently dropping the request.

Reviewer setup notes must include the exact test domain, users, Chat spaces, and Threada workspace or pack mapping needed to exercise the app. Credentials, tokens, cookies, raw event payloads, and customer data must stay out of repo evidence and screenshots.

Gmail Or Workspace Add-On Follow-On

A Gmail or Workspace add-on can expose create-WorkItem and governed-draft surfaces after the add-on is real. The add-on must use least-privilege OAuth scopes, explain every scope in the consent/review materials, and avoid broad mailbox, Drive, or Calendar access unless the v1 surface truly needs it.

If the add-on uses sensitive or restricted scopes, complete OAuth verification and any required security assessment before claiming Marketplace readiness.

Marketplace Package Requirements

Google’s publishing guide says public Marketplace apps require Google review and that publication involves a Google Cloud project, OAuth configuration, testing, the Marketplace SDK, and a store listing. Google’s Marketplace SDK guide says the SDK manages app configuration and availability, including app integrations, visibility, installation settings, and OAuth scopes. Google’s OAuth guidance says public apps using sensitive or restricted scopes require OAuth verification, and restricted scopes may require additional security assessment.

Required package work before submission:

  • Google Cloud project with the correct APIs enabled.
  • Google Workspace Marketplace SDK configuration for the chosen app integration.
  • Google Chat app or Workspace add-on configuration, manifest, icons, and production endpoints.
  • Google Chat direct-message and space behavior, welcome message, Help command, @mention handling, delay response, notification controls, add/remove handling, and production URL evidence when Chat is the v1 surface.
  • OAuth consent screen, OAuth clients where required, and the complete least-privilege scope list.
  • Tenant/domain/space install mapping, setup-required behavior, WorkItem creation, success response, and uninstall or disconnect handling.
  • Public support, privacy, terms, security/data-handling, and setup documentation, including https://docs.threada.ai/integrations/google-workspace-setup/.
  • Store listing copy, screenshots, test instructions, setup notes, and reviewer account or test-domain access.
  • OAuth verification and security assessment evidence when scopes require it.
  • Google Marketplace review approval before public-readiness claims.

Explicit Non-Goals

  • No public Google Workspace Marketplace readiness claim until the configuration scaffold is runtime-bound, configured in Google Cloud and Marketplace SDK, validated with real Google values, and accepted by Google review.
  • No broad Gmail, Drive, Calendar, Admin SDK, or domain-wide scopes unless the exact v1 capability requires them and the implementation is validated end to end.
  • No direct side-effecting external action execution from Google Chat or Gmail.
  • No customer-data screenshots, raw Google event exports, or private tenant payloads in Marketplace screenshots or review evidence.
  • No positioning as a generic “AI agent executes any Google Workspace action” app. Public copy must stay anchored to WorkItem intake, setup, and governed review.

Review Gates

Implemented:

  • Public API and runtime models include an email WorkItem source channel.
  • Runtime automation includes Gmail intake/reply sync and governed Gmail draft action wiring.
  • Notifications include Google Chat delivery plumbing for operational messages.
  • Public API docs and generated OpenAPI are published.
  • Public setup/support documentation covers install, mapping, command use, setup-required behavior, disconnect, uninstall, data handling, and support.
  • Studio exposes the public setup handoff at https://studio.threada.ai/integrations/google-workspace/install, which preloads the Google Workspace runtime integration kind and connector preset before the reviewer or tenant admin completes Google Chat app/domain/space mapping.
  • Private Google Workspace Marketplace configuration scaffold exists at packages/google-workspace-marketplace-app.
  • The scaffold generates local Google Chat API config, Marketplace listing inputs, source config, and submission-readiness output from committed source.
  • Package tests cover least-privilege Google Chat v1 scope, placeholder injection, broad-scope rejection, generated-file drift, and submission-readiness blockers.

Missing:

  • Real Google Cloud project ID, Chat endpoint URL, Chat avatar URL, and Marketplace listing ID wired through private environment variables for Google Cloud console configuration.
  • Google Cloud project/Marketplace SDK configuration for the public app.
  • Google Chat app configuration in Google Cloud, hosted icons/avatar, and production endpoint validation.
  • Google Chat review behavior: direct message and space installation, welcome message, Help command, reliable responses, @mention handling, delay messages, notification controls, add/remove behavior, cards/messages, and production URLs.
  • OAuth consent screen, least-privilege scopes, OAuth clients, and verification evidence where required.
  • Real Google Chat app tenant/domain/space install mapping, setup-required, success, and uninstall or disconnect behavior beyond the Threada-side runtime setup handoff.
  • Store listing copy, screenshots, test instructions, setup notes, and reviewer access.
  • Public setup/support URL reachability evidence from the deployed docs site.
  • Google Marketplace review evidence and approval report.

Blocked:

  • Public Google Workspace Marketplace submission is blocked until the configuration scaffold is rebuilt with real Google values, runtime behavior is implemented and testable, Google Cloud/Marketplace SDK configuration exists, OAuth/app review gates pass, and reviewer setup is complete.

Launch Checklist

  1. Keep the v1 Google surface to the committed Google Chat-to-WorkItem configuration scaffold.
  2. Rebuild the local config bundle with real Google Cloud project ID, Chat endpoint URL, Chat avatar URL, and Marketplace listing ID.
  3. Create the Google Cloud project and enable the required APIs, including the Marketplace SDK.
  4. Configure the Google Chat app and Marketplace SDK with least-privilege scopes, hosted icons/avatar, and production endpoints.
  5. Implement tenant/domain/space installation mapping, setup-required behavior, WorkItem creation, success response, and uninstall or disconnect handling.
  6. Implement Google Chat review behavior for direct messages, spaces, welcome, Help, @mention handling, delay responses, notification controls, add/remove flows, cards/messages, and production URLs.
  7. Configure OAuth consent, OAuth clients, and Marketplace SDK app configuration with the exact scopes required by the package.
  8. Use the public setup/support guide at https://docs.threada.ai/integrations/google-workspace-setup/ and add Store listing copy.
  9. Create sanitized screenshots and demo material for the key user flow.
  10. Complete OAuth verification and any required security assessment for sensitive or restricted scopes.
  11. Submit through Google Workspace Marketplace review and resolve all review issues before claiming Marketplace readiness.

References