Google Workspace Marketplace

Workspace

Google LLC · Productivity & collaboration suites

Best for: Add-ons and SaaS integrations that extend Gmail, Drive, Docs, or Sheets for organizations.

Overview

Google Workspace Marketplace distributes editor add-ons (Docs/Sheets/Slides), Gmail add-ons, and Chat apps built with Apps Script or standard web technologies. Apps authenticate via Google OAuth 2.0 with granular, sensitive-scope review for anything touching user data.

How to build & ship

  1. 1Build a Google Workspace Add-on (Apps Script or HTTP/Alternate runtime) or a web/SSO app
  2. 2Enable required APIs in a Google Cloud project and integrate the relevant Workspace/Google APIs
  3. 3Configure the OAuth consent screen and create OAuth 2.0 credentials with least-privilege scopes
  4. 4Set up the Google Workspace Marketplace SDK listing (store details, scopes, visibility)
  5. 5Submit for OAuth verification (sensitive/restricted scopes) and then for Marketplace app review

Key APIs & SDKs

Google Workspace Add-ons framework (Apps Script / CardService)
Google Workspace Marketplace SDK
OAuth 2.0 with Google identity
Workspace REST APIs (Drive, Gmail, Calendar, Sheets)
Admin SDK

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: API key
  • Security review: Required
  • Google's OAuth verification and CASA security assessment required for sensitive/restricted scopes.
  • Listing requires both OAuth verification (consent-screen and data-use review, with a possible demo video and CASA security assessment for sensitive scopes) and a separate Marketplace app review of branding, scopes, and UX — budget roughly 2-3 weeks, longer if a security assessment is triggered.
  • Per-project and per-user quotas across Workspace APIs, managed via Google Cloud Console.

Monetization

Onboarding
$0
Commission
0% direct; billing handled by developer
Merchant of Record
Developer is MoR

Pros & cons for builders

Pros

  • Access to the enormous Google Workspace install base with admin-managed domain-wide install
  • Multiple runtimes (Apps Script or your own backend) lower the build barrier
  • Deep native integration across Drive, Gmail, Calendar, Sheets, and Docs
  • Strong enterprise trust signals via verification

Cons

  • OAuth verification for sensitive/restricted scopes can be slow and require costly third-party security assessments
  • Two parallel review tracks add process overhead
  • Scope changes after launch can trigger re-verification