If your Google Workspace Add-ons needs access to non-Google APIs that require OAuth, you You can use data fetched from non-Google services.
Information to display in the add-on cards you build. Note: Failing to call build() after using builder classes in theĬard service results in type errors. Populate each card section with the individual widgets that make up theĪfter you have added all the sections and widgets to your card via its In Apps Script, you create cards using the YourĪdd-on can also create and display new cards in Your manifest must return either a singleĭifferent 'pages' of the add-on interface. You define an add-on user interface by creating Using OAuth, you must configure the OAuth for that Properly formatted JSON for the interface to render as cards.Īdd-on connects to a third-party, non-Google service
Google add ons code#
You must implement a card-based interface for theĬard service or if you're writing in another code language, return Manifest as needed to produce the required add-on
Google add ons how to#
See Manifests for details on how to configure yourĪs you add code and features to your add-on, edit the Information the host application needs to display the For Google Workspace Add-ons, the manifest also provides the basic It specifies a variety of details about the project, such as its libraryĭependencies. In Apps Script projects, the project manifest is a special JSONįile. Refer to the Google Workspace Add-on style guideįor guidelines on how to design your add-on userĮxperience. You can alsoĬonsider contextual cards triggered by a user's action in the host Then add more widgets, cards, navigation, and other behavior. With a simple design to get working first, then add more refinements. Consider what use cases theĪdd-on should attempt to provide solutions for. It should behave before you start building it. Design your add-on appearance and behaviorĭecide what you want your add-on to look like and how To create a Google Cloud project, see Create a Google Cloud project. This helps ensure someone on your team can always access the We recommend that you add collaborators to the To create an Apps Script project, see Script projects. Project, but it doesn't need to be the owner. The publishing account must have edit access to the script When you publish an add-on, a single user account actsĪs the publisher. Script file in a shared drive ensures that multiple collaborators have access to
Otherwise you could lose access to theĪdd-on code and settings entirely. Projects, it's vital that you transfer ownership of them prior to the owner'sĪccount being shut down or removed. Warning: If you don't add collaborators to your add-on The owner of the projects creates and manages the project filesĪnd associated settings, while collaborators can help with coding and testing. User account to own the projects and decide which other accounts areĬollaborators. If you build your add-on in a language other thanĪpps Script, you only need to create a Google Cloud project.īefore starting add-on development, choose a single You create both an Apps Script project and a Google Cloud project. Set up your add-on's projects and choose an owner and collaborators Write code to define the add-on's appearance and.Configure the add-on's project manifest or.Design your add-on's appearance and behavior.
0 kommentar(er)
