Gmail push

With Gmail push on, signplume writes each active person's signature into their Gmail settings, using the same service account as Directory sync. Nobody has to paste anything, and a change to your brand, a template or someone's details reaches Gmail on the next run.

What it needs

• Google Workspace connected on Directory sync. See Connect Google Workspace.
• The Gmail API enabled in the service account's Google Cloud project.
• One more scope on the same domain-wide delegation, beside the directory scope: https://www.googleapis.com/auth/gmail.settings.basic (gmail.settings.basic). Until it is granted, Gmail refuses every write with a scope error.

To add the scope, open the Google Admin console, go to Security → Access and data control → API controls → Manage domain-wide delegation, find your service account's client ID, choose Edit, and add the scope at the end of the line after a comma.

Turn it on

On Directory sync, under Push signatures into Gmail, press Push signatures into Gmail. From then on signatures are written at the end of each sync, about every six hours, and whenever you press Push now.

What it writes

• The main signature design. Gmail holds one signature per address, so a shorter design for replies and forwards is not pushed.
• Every address the person sends from in Gmail: their main address and any send-as addresses on their mailbox.
• An empty signature for archived people and for people with Signatures off, so an old footer stops going out.
• Only people whose signature has changed since the last push. At most 200 people are written in one run; the rest follow in the next.
• Nothing longer than Gmail allows: a signature over 10,000 characters is not pushed, and shows as failed.

A dated rule or a campaign banner reaches Gmail on the first run after its window opens, and leaves on the first run after it closes. Recipient rules cannot apply: Gmail keeps one fixed signature per address, whoever the message is going to.

Gmail push reads no mail and changes nothing else in Gmail. People can still edit their own signature in Gmail's settings; signplume writes it again the next time their signature changes, or when you press Push now.

Seeing that it worked

The table under Push signatures into Gmail lists each person as Pushed, Failed (with Google's reason) or Pending. On People, a person whose latest push Gmail accepted shows as Gmail push in the Signing column, which counts as signing. A refused push shows as Gmail push failed, with the reason and a link to push again.

To stop, press Stop pushing to Gmail. Signatures already in Gmail stay as they are.