Deploy your whole team's signatures without touching a single workstation
WeLink centralises the design, deployment and tracking of email signatures across Google Workspace — pushed into Gmail through the Gmail API, from a single console. Outlook and Gmail. Hosted in Switzerland.
Deploy signatures
Template: Signature 2026
One centralised push, every Gmail mailbox
Google Workspace does not deploy through a per-workstation add-in: WeLink pushes signatures straight into Gmail via the Gmail API, organisation-wide.
Gmail API push
Server-side, organisation-wide
The signature is written to Gmail through the Gmail API for every targeted user. No install on workstations, applied to the whole organisation or a selection.
WeLink editor
Centralised design
Design the signature once in the WeLink editor, with a real-time preview. Content updates everywhere on the next push, with nothing for team members to do.
Directory mapping
Auto & manual
Mapping links Google Workspace directory users to team members — automatically or by hand — so the right person gets the right signature.
Multilingual content
Per team member
Signature content (position, department, notices) can be translated per team member, then pushed in the right language.
| Platform | Method | Install | Per-user choice | Clients covered |
|---|---|---|---|---|
| Google Workspace · GmailThis page | Gmail API push | None | No — centralised signature | Gmail (web & mobile) |
| Microsoft 365 · Outlook | Add-in, transport, mailbox or EWS | None (add-in deployed centrally) | Yes — with the Outlook add-in | Outlook Win / Mac / New, web, mobile |
Gmail's add-in equivalent: a signature designed centrally
Gmail has no per-user add-in like Outlook. With WeLink you design the signature in the editor and push it into Gmail — everyone gets the right signature, with nothing to do.
Centralised design
A visual editor with a real-time preview. The signature is designed once and applied to the whole team.
Templates & variants
Multiple templates per organisation, with per-team or per-entity variants, assigned to the right team members.
Language per team member
When content is translated, each team member gets their signature in the language they picked.
Trackable buttons & QR
Add buttons, links and QR codes. Visits, scans and clicks are measured in WeLink.
Every mapped user
Each Google Workspace user you map gets their signature pushed straight to Gmail — no per-person setup.
Signature preview
From connection to deployment in four steps
Connect your Google Workspace, let WeLink match your users, then push at scale with real-time tracking.
Connect Google Workspace
An admin authorises WeLink via OAuth. Tokens are encrypted and bound to your organisation.
Map the directory
Mapping links Google Workspace directory users to team members, automatically or by hand.
Push through Gmail
WeLink writes signatures to Gmail through the Gmail API — the whole organisation or a selection.
Track & measure
Follow real-time progress, the deployment history, and visits, scans and clicks.
Also on Microsoft 365 and Outlook
On Microsoft 365? WeLink also deploys your signatures through the Outlook add-in, transport rules, mailbox configuration or EWS.
Built for IT, hosted in Switzerland
Signature deployment touches every mailbox. WeLink does it with least privilege and full traceability.
Hosted in Switzerland / EU
Data and assets hosted in Switzerland and the EU. Encrypted at rest (AES-256) and in transit (TLS 1.3).
Encrypted OAuth tokens
Google OAuth tokens are encrypted at rest and decrypted only when used, bound to your organisation.
Per-organisation isolation
Row-Level Security on every table and Owner / Admin / Member roles for least-privilege access.
Audit & GDPR/nDSG
Audit log of sensitive actions, plus data export and deletion on request.
Deployment questions, answered
Do I need to install anything on each workstation?
No. Signatures are written to Gmail through the Gmail API, server-side. There is nothing to install on team members’ workstations.
Is there a Gmail add-in like the one for Outlook?
No — that's the difference from Outlook. Gmail has no per-user signature add-in. WeLink does the equivalent differently: you design the signature in the WeLink editor and WeLink pushes it into Gmail through the Gmail API.
Which Google permissions are required?
An admin authorises WeLink via OAuth, with the scopes needed to manage Gmail signatures. Tokens are encrypted and bound to your organisation.
Do you handle shared mailboxes and aliases?
Gmail signatures are set per user, on each person's primary address, so WeLink pushes a signature to every mapped Google Workspace user's Gmail. Gmail has no shared-mailbox concept, and signatures aren't applied per alias. (On Microsoft 365, the Outlook add-in does cover shared mailboxes and delegations.)
Can signatures be multilingual?
Yes. Content (position, department, notices) can be translated per team member, and each person gets their signature in the right language.
Ready to deploy signatures across Google Workspace?
Connect your Google Workspace and push your first signature campaign in minutes.
No credit card — free plan available.