This guide will walk you through creating a public Google Workspace Add-on, and launching it in the Google Workspace Marketplace for as free as possible. …
I’d never developed or published an add-on before. As I was looking into it, I realized that, while it is not super complicated, it is not readily obvious — especially for anyone just getting into add-on development. Google does have a guide on developing and publishing an add-on but it leaves a lot of unanswered questions.
So I thought I would put together what I learned in this guide — a playbook for anyone else who wants to develop their own add-on.
Following on from a recent Pulse post on How to publish to the Google Workspace Marketplace published by the Google Workspace team, here’s a developer’s take on the process from start to finish. As mentioned in the post the official support resources should be your start point, but these notes spotlight some of the nuances required to publish an add-on and the appendix includes some tips on naming your add-on and where/how to host required documentation including your add-on privacy policy.
If your organization is using G-Suite (now known as Google Workspaces) then you’re hopefully using Google Apps Script to automate your email communication. (If you aren’t, why not? It’s a brilliant way to manage your communications.) You probably have different types of emails — for different purposes.
Do all of your emails have the same look-and-feel? Do they all match your organization’s branding requirements? How easy is it to update the format for all of them if you need to change a core/base element? Maybe the company tagline and color theme changed — how quickly can you get all of your emails updated?
I am going to show you how to create templated emails so that all of the emails you send have the same look-and-feel and are easy to maintain/update.
