At the top, if a different project is already open, select the project name
of your app's project to switch projects.
Click APIs & Services.
Select Google Workspace Marketplace SDK to view the details page.
Create your deployment
You can create your deployment directly in Google Cloud console by creating an
HTTP deployment (recommended), or by using
Google Apps Script.
HTTP deployment
Click the HTTP deployments tab.
Click Create new deployment and enter the
add-on's deployment ID.
The deployment ID is an arbitrary string that helps the
add-on developer identify the deployment
containing the add-on manifest. Deployment
IDs are required and can have at most 100 characters.
Click Next.
A side panel opens for you to submit the specification of the
add-on manifest in JSON format. This is also
called DEPLOYMENT.JSON.
The add-on manifest
file is the
central configuration for a Google Meet add-on. The
following code sample shows the available Meet fields
for web in the add-on manifest file.
NAME: String. The name of your
Google Meet add-on.
LOGO_URL: String. The URL of the logo for the
Google Workspace add-on. This is used for the add-on
across Google Workspace products.
SIDE_PANEL_URI: String. The URL to the entry
point of your add-on app. This is displayed
in an iframe within the
side panel. The
origin of this URL must be
part of the origins specified in the
ADD_ON_ORIGINS field.
ADD_ON_ORIGINS: List of strings. A list of
origins where your
add-on is hosted. Two URLs have the same
origin when they share the same scheme, host, and port. Sub origins
are also permitted, as are wildcard subdomains. For more information,
see
Add-on security.
DARK_MODE_LOGO_URL: String. A dark
mode specific URL of the logo for the add-on.
Supplying a dark mode logo makes sure your add-on
will look best in any Meet theme. For logo design
guidelines, see Best practices.
MEET_WEB_LOGO_URL: Optional. String. A
Meet-specific URL of the logo for the add-on.
This logo is used throughout Meet. If not present, the
logoUrl from the common section is used. For logo design guidelines
see Best practices.
SUPPORTS_SCREENSHARING: Optional. Boolean. If
set to false, users must use the add-on to
see what's happening in a collaborative
add-on session. If set to true, the initiator
of the collaborative add-on session can
screen share their view of the add-on.
In the App configuration tab, under App integration, select
Google Workspace add-on. Select
Deploy using cloud deployment resource and then choose the correct
HTTP deployment.
Google Apps Script
Click the App configuration tab.
Under App integration, select Google Workspace add-on.
Select Deploy using Google Apps Script
deployment ID and enter your script's deployment ID.
Click Save.
For details on how to create an Apps Script project, see
Apps Script documentation. The
Meet add-on relies solely on the
appsscript.json manifest file, also called the
Apps Script project manifest. Make sure the manifest
file in your Apps Script project contains an addOns
and a meet section. The addOns and meet sections follow the same
structure as described in the HTTP deployment tab.
Unlike other Google Workspace add-ons, Meet add-ons
cannot be built entirely in Apps Script. You must,
instead, build a full web app by
creating a side panel and main stage.
The side panel URL of your web app then must be specified under the
SIDE_PANEL_URI of the appsscript.json manifest file.
Install and test the add-on in Meet
To test your add-on in Meet, you must
first install it for the signed-in user:
You should now be able to use your add-on in a meeting.
To try it, start a meeting at meet.google.com. The
installed add-on is now visible in the Activities
panel.
In addition to installing your add-on for the
individual signed-in user, you can also publish it.
When you publish your Google Workspace add-on, you make it available for
others to find, install, and use.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-04 UTC."],[],[],null,["Google Meet add-ons are created and configured as part of a Google Cloud project.\n| **Note:** Before following this deployment guide, you first must [create a web app](/workspace/meet/add-ons/guides/quickstart) that uses the Meet add-ons SDK, and then deploy that web app to a website that you own.\n\nCreate a Google Cloud project\n\nTo generate a Google Cloud project, see [Create a Google Cloud\nproject](/workspace/guides/create-project).\n\nEnable the Google Workspace Marketplace SDK and Google Workspace add-ons API\n\nThe Google Workspace Marketplace SDK and Google Workspace add-ons API are required to develop\nMeet add-ons. To enable them:\n\n1. Open the [Google Cloud\n console](https://console.cloud.google.com/).\n2. At the top, if a different project is already open, select the project name of your app's project to switch projects.\n3. At the top, in the search bar, type `Google Workspace Marketplace SDK` and press enter.\n4. Open the `Google Workspace Marketplace SDK` page, click **Enable**.\n\n | **Warning:** Make sure you enable the `Google Workspace Marketplace SDK`, not the API. The `Google Workspace Marketplace API` is a different tool used to integrate with Google's licensing and billing services.\n5. Repeat these steps to find and enable the `Google Workspace add-ons API`.\n\nCreate a deployment\n\nTo use an add-on in Meet, you need a\ndeployment and an [add-on manifest\nfile](/apps-script/add-ons/concepts/workspace-manifests).\n\nNavigate to the Google Workspace Marketplace SDK for your project in Google Cloud console\n\n1. Open the [Google Cloud\n console](https://console.cloud.google.com/).\n2. At the top, if a different project is already open, select the project name of your app's project to switch projects.\n3. Click **APIs \\& Services**.\n4. Select `Google Workspace Marketplace SDK` to view the details page.\n\nCreate your deployment\n\nYou can create your deployment directly in Google Cloud console by creating an\nHTTP deployment (recommended), or by using\nGoogle Apps Script. \n\nHTTP deployment\n\n1. Click the **HTTP deployments** tab.\n2. Click **Create new deployment** and enter the\n add-on's deployment ID.\n\n The deployment ID is an arbitrary string that helps the\n add-on developer identify the deployment\n containing the add-on manifest. Deployment\n IDs are required and can have at most 100 characters.\n3. Click **Next**.\n\n A side panel opens for you to submit the specification of the\n add-on manifest in JSON format. This is also\n called DEPLOYMENT.JSON.\n\n The [add-on manifest\n file](/apps-script/add-ons/concepts/workspace-manifests) is the\n central configuration for a Google Meet add-on. The\n following code sample shows the available Meet fields\n for web in the add-on manifest file. \n\n {\n \"addOns\": {\n \"common\": {\n \"name\": \"\u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e\",\n \"logoUrl\": \"\u003cvar translate=\"no\"\u003eLOGO_URL\u003c/var\u003e\"\n },\n \"meet\": {\n \"web\": {\n \"sidePanelUri\": \"\u003cvar translate=\"no\"\u003eSIDE_PANEL_URI\u003c/var\u003e\",\n \"addOnOrigins\": [\"\u003cvar translate=\"no\"\u003eADD_ON_ORIGINS\u003c/var\u003e\"],\n \"darkModeLogoUrl\": \"\u003cvar translate=\"no\"\u003eDARK_MODE_LOGO_URL\u003c/var\u003e\",\n \"logoUrl\": \"\u003cvar translate=\"no\"\u003eMEET_WEB_LOGO_URL\u003c/var\u003e\",\n \"supportsScreenSharing\": \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-err\"\u003eSUPPORTS_SCREENSHARING\u003c/span\u003e\u003c/var\u003e\n }\n }\n }\n }\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: String. The name of your Google Meet add-on.\n - \u003cvar translate=\"no\"\u003eLOGO_URL\u003c/var\u003e: String. The URL of the logo for the Google Workspace add-on. This is used for the add-on across Google Workspace products.\n - \u003cvar translate=\"no\"\u003eSIDE_PANEL_URI\u003c/var\u003e: String. The URL to the entry point of your add-on app. This is displayed in an iframe within the [side panel](/workspace/meet/add-ons/guides/overview#side-panel). The [origin](/workspace/meet/add-ons/guides/overview#origin) of this URL must be part of the origins specified in the \u003cvar translate=\"no\"\u003eADD_ON_ORIGINS\u003c/var\u003e field.\n - \u003cvar translate=\"no\"\u003eADD_ON_ORIGINS\u003c/var\u003e: List of strings. A list of [origins](/workspace/meet/add-ons/guides/overview#origin) where your add-on is hosted. Two URLs have the same origin when they share the same scheme, host, and port. Sub origins are also permitted, as are wildcard subdomains. For more information, see [Add-on security](/workspace/meet/add-ons/guides/add-on-security).\n - \u003cvar translate=\"no\"\u003eDARK_MODE_LOGO_URL\u003c/var\u003e: String. A dark mode specific URL of the logo for the add-on. Supplying a dark mode logo makes sure your add-on will look best in any Meet theme. For logo design guidelines, see [Best practices](/workspace/meet/add-ons/guides/best-practices#logo-design).\n - \u003cvar translate=\"no\"\u003eMEET_WEB_LOGO_URL\u003c/var\u003e: Optional. String. A Meet-specific URL of the logo for the add-on. This logo is used throughout Meet. If not present, the `logoUrl` from the common section is used. For logo design guidelines see [Best practices](/workspace/meet/add-ons/guides/best-practices#logo-design).\n - \u003cvar translate=\"no\"\u003eSUPPORTS_SCREENSHARING\u003c/var\u003e: Optional. Boolean. If set to false, users must use the add-on to see what's happening in a collaborative add-on session. If set to true, the initiator of the collaborative add-on session can screen share their view of the add-on.\n4. Click **Submit**.\n\n For more information on deployments, see [Create a\n deployment resource](/workspace/add-ons/guides/alternate-runtimes#create_a_deployment_resource).\n5. In the **App configuration** tab, under **App integration** , select\n **Google Workspace add-on** . Select\n **Deploy using cloud deployment resource** and then choose the correct\n HTTP deployment.\n\nGoogle Apps Script\n\n1. Click the **App configuration** tab.\n\n2. Under **App integration** , select **Google Workspace add-on** .\n Select **Deploy using Google Apps Script\n deployment ID** and enter your script's deployment ID.\n\n3. Click **Save**.\n\n For details on how to create an Apps Script project, see\n [Apps Script documentation](/apps-script/overview). The\n Meet add-on relies solely on the\n appsscript.json manifest file, also called the\n [Apps Script project manifest](/apps-script/concepts/manifests). Make sure the manifest\n file in your Apps Script project contains an `addOns`\n and a `meet` section. The `addOns` and `meet` sections follow the same\n structure as described in the HTTP deployment tab.\n\n Unlike other Google Workspace add-ons, Meet add-ons\n cannot be built entirely in Apps Script. You must,\n instead, build a full web app by\n [creating a side panel and main stage](/workspace/meet/add-ons/guides/quickstart).\n The side panel URL of your web app then must be specified under the\n \u003cvar translate=\"no\"\u003eSIDE_PANEL_URI\u003c/var\u003e of the appsscript.json manifest file.\n\nInstall and test the add-on in Meet\n\nTo test your add-on in Meet, you must\nfirst install it for the signed-in user: \n\nHTTP deployment\n\n1. [Navigate to the Google Workspace Marketplace SDK for your project in Google Cloud console](#navigate-to-marketplace_sdk).\n2. Click the **HTTP deployments** tab.\n3. Click **Install** under the **Actions** column.\n\nGoogle Apps Script\n\n1. Follow the Google Workspace add-on documentation to [Install an unpublished add-on](/workspace/add-ons/how-tos/testing-workspace-addons#install_an_unpublished).\n\nYou should now be able to use your add-on in a meeting.\nTo try it, start a meeting at [meet.google.com](https://meet.google.com). The\ninstalled add-on is now visible in the Activities\npanel.\n\nIn addition to installing your add-on for the\nindividual signed-in user, you can also [publish it](/workspace/meet/add-ons/guides/publish).\nWhen you publish your Google Workspace add-on, you make it available for\nothers to find, install, and use."]]