Google Drive provides a cloud-based storage solution for
Google Workspace files and other
user data. Managing data in Drive can be a time-consuming task.
You can save time and effort for your users by extending Google Drive with
Google Workspace add-ons. When you build a Google Workspace add-on, you can define custom
interfaces that are inserted directly into Google Drive, exactly where the
user needs them. These interfaces help automate Drive tasks, present
additional information to the user, or let the user interact with a third-party
system without having to switch to a new browser tab.
Google Workspace add-ons can define the following kinds of extensions within Google Drive:
Contextual interfaces that appear when users select items in the Google Drive
interface.
See what you can make
Google Workspace add-ons are built using
Apps Script, and their interfaces defined using the Apps Script
Card service. See
Building Google Workspace add-ons
for an overview. Google Workspace add-on behavior is
configured using a manifest, which includes
Drive-specific sections.
When configuring your Google Workspace add-on to extend
Google Drive, you must
decide what interfaces to create for your add-on and what actions it can take.
See the following guides for more information:
[null,null,["Last updated 2025-02-13 UTC."],[[["Google Workspace add-ons extend Google Drive functionality by letting you build custom interfaces directly within the Drive interface."],["These add-ons, built using Apps Script, automate tasks, provide extra information, and enable interactions with other systems without leaving Drive."],["Add-ons can have non-contextual homepages or contextual interfaces that appear based on user selections, but mobile support is not yet available."],["To build add-ons, you need to define the interfaces and actions using Apps Script's Card service and configure behavior with a manifest."]]],["Google Workspace add-ons enhance Google Drive by providing custom interfaces directly within the platform. These interfaces automate tasks, show additional information, and enable interaction with third-party systems. Add-ons can have non-contextual homepages and contextual interfaces triggered by item selection. Built using Apps Script and the Card service, add-ons' behavior is configured through a manifest, including Drive-specific sections. Key actions include building Drive interfaces and defining the add-on's functionalities. Currently, mobile client extensions are not supported.\n"]]
