Alternate Runtimes for Google Workspace Add-ons is coming soon. Learn more.

Extending Google Workspace with Add-ons

8еа39680ц8 5138ц2ц823 800е90953а 1685бдфб67

Add-ons are customized applications that integrate with productivity applications such as Gmail, Google Sheets, and Google Docs.

Add-ons are built using Apps Script, a rapid application development platform based on JavaScript that lets you create business and productivity applications quickly and easily.

Add new capabilities to

Add-ons can help automate tasks or make third-party services or information available in . With add-ons, you can do the following:

  • Create customized user interfaces that are directly integrated into applications. These interfaces can display information to the user and provide user controls.
  • Boost workflow efficiency when working with by automating or streamlining tasks.
  • Easily control and move data between Google applications with Apps Script services.
  • Remove the need for browser switching by providing the user everything they need within .
  • Connect to non-Google services within applications, allowing you to retrieve or upload data from those services into and from .

Types of add-ons

There are two types of add-ons you can build: Add-ons and Editor Add-ons. For more information about each, see Add-on types.

The add-on development lifecycle

Add-ons go through different stages as they are developed, tested, and published:

  • Building. To create an add-on, you must create an Apps Script project and write code that defines the add-on's appearence and behavior. Depending on the problems the add-on is attempting to solve, you might need to write code that interacts with one or more of the Apps Script services or else use various Apps Script features such as triggers.
  • Testing. In order to provide the best experience for your users, you must thoroughly test your add-on prior to publishing it. You can install and test unpublished add-ons provided you have access to the add-on's script project. When testing your add-on, make sure the add-on UI appearance and behavior is what you intended. Try to anticipate how users interact with your add-on and provide a solid user experience.
  • Publishing. When your add-on is finished you can publish it to the Marketplace for others to find and use. You can publish an app publicly for everyone to find, or publish only to your domain.
  • Updating. After an add-on is published, at times you might want to update its code or how it appears in the Marketplace. You might also want to unpublish an add-on if it's no longer useful.

Get started

Here are some ways to start developing your add-on: