Stuck Publishing Google App Script? A Complete Guide to the Process and OAuth Setup

Introduction#

If you’ve written a Google App Script and want to turn it into an Add-on for the Google Workspace Marketplace, the biggest hurdles aren’t the code itself, but rather OAuth, deployment IDs, and the review process.

These settings are scattered and complex, and a single oversight can lead to rejection.

This post compiles the complete Google App Script publishing process and OAuth setup, guiding you through it all so you won’t get stuck again.

🎯 Objectives#

This post will guide you through:

Creating an App Script project
Configuring the OAuth consent screen
Testing the Add-on
Publishing to the Google Workspace Marketplace

Core Process (Step-by-Step Breakdown)#

Step One: Create and Deploy App Script#

Create App Script
Open appscript.json & Specify GCP Project Number
Deploy → New deployment
Deploy → Test deployments (Development testing)

Step Two: Configure OAuth Permissions#

Required fields:

App Name: Must match the Add-On package
App domain: Requires a promotional website containing privacy policy and terms of service (can use your own domain / host on github.io)
Authorized domains: The domain used by the App domain

Underlying Principle

Google verifies application trustworthiness via the OAuth screen
This is where the review focuses

Step Three: Marketplace Publishing Settings#

Enable the “Google Workspace Marketplace SDK” service
Both tabs require filling in: App Script’s Deployment ID, developer information, and product information
Store Listing → Browse MARKETPLACE: Pre-publishing test. Fill in the “Draft testers” email on this page.
To test, you also need to configure OAuth testing: OAuth consent screen → Users → Test users + Add
After testing, return to “Store Listing”: Submit for review
Switch OAuth to Production
Finally, just await Google’s review results.