Meet Add-on concepts

Google Meet Add-ons are used to build experiences directly into Google Meet. To create add-ons, you must understand how a Google Workspace Add-on is developed and eventually published in add-ons.

Google Workspace Add-ons in the Marketplace

Google Workspace Add-ons are customized apps that integrate with Google Workspace applications, such as Gmail, Google Docs, and Google Sheets. They allow developers to create customized user interfaces that are directly integrated into Google Workspace. Add-ons help users work more efficiently with less context switching.

The Google Workspace Marketplace offers users and administrators a way to find and install third-party enterprise apps that are integrated with Google Workspace. The Marketplace is also the central place for managing published Google Workspace Add-ons. Users can install and uninstall published add-ons, and admins can restrict the add-ons users can install.

Types of add-ons

In general, there are two types of add-ons you can build: Google Workspace Add-ons and Editor Add-ons.

For the Meet Add-ons SDK, you must build your add-ons using Google Workspace Add-ons.

With a Google Workspace Add-on, you can extend multiple Google Workspace apps such as Gmail, Google Calendar, and Google Drive. You specify which app the add-on is targeting, along with other details, in the add-on manifest file. For the Meet Add-ons SDK, you must declare a meet object within the addOns section of the manifest file. For more information, see Create a deployment.

A Google Workspace Add-on can be developed in two different ways: either in Google Apps Script, or as a self-hosted add-on using your preferred tech stack. Each of these add-ons contains a manifest, which is made up of different sections. The Meet section of the manifest contains information specific to how your add-on is loaded from Google Meet and is unrelated to whether the rest of your add-on is self-hosted or uses Apps Script. Add-ons for Meet are loaded in an iframe and must reference web pages rather than Card-based interfaces.

For example, a manifest for a Google Workspace Add-on might have a section for Gmail that uses ComposeTrigger and ContextualTrigger objects to return card interfaces, and a section for Meet that uses web, iOS, and Android objects to point to your web page and mobile app.

An example manifest with Meet and Gmail sections.
Figure 1. An example manifest with Meet and Gmail sections.

Publish an add-on

When you publish your Google Workspace Add-on, you make it available for others to find, install, and use.

You can choose to publish your add-on either publicly or privately. When you publish publicly, your add-on is listed on the Google Workspace Marketplace for any user to find and install. When you publish privately, your add-on is limited to users within your Google Workspace organization. It's also listed in the Internal Apps section of the Marketplace.

When you're ready to publish your add-on to the Marketplace, follow the steps in Publish apps to the Google Workspace Marketplace.