Google Workspace
server-side email signatures
The right signature appears on any device or email client, with no user action. Setup takes about 5 minutes.
Google Workspace
Automatically adds signatures to every email sent from Google Workspace, on any device or email client.
How it works
Centralized one-click installation. No teammate action needed.
Users don't see signatures when composing emails
Install once, deploy everywhere. Signatures sync instantly across Web, Desktop, Apple Mail, iOS and Android.
Security & Privacy
Your emails are processed through Scribe's secure servers for signature installation.
SOC 2 Type II Certified. Your data is safe.
Installation guide
Follow the steps below to connect Google Workspace to Scribe.
Add host
To route emails through Scribe's secure servers, create a host in Google Workspace Gmail. In Google Admin, go to Apps → Google Workspace → Gmail, then click 'Hosts'.
Click the "ADD ROUTE" link and fill in the form with the following info:
- Name: Scribe
- Select: "Single host"
- Host name or IP:
smtp.server.scribe-mail.com - Port: 25
- Select: the options like in the screenshot below
smtp.server.scribe-mail.com
Configure the SMTP relay service
To receive emails back from Scribe for routing to recipients, go to Apps → Google Workspace → Gmail in Google Admin, then click 'Routing'.
On the next page, click Configure under "SMTP relay service
Fill in the form with the following information:
- Description: Receive from Scribe
- Authentication:
Check: "Only accept mail from the specified IP addresses"
Add:15.236.243.144and51.44.50.107 - Select: "Require TLS encryption"
- Click: "Save"
15.236.243.144
51.44.50.107
Route your emails through the created Host
In Google Admin, go to Apps → Google Workspace → Gmail, then click 'Compliance'
On the next page, click Configure under "Content compliance
Fill in the form as shown in the screenshot
- Description: Route to Scribe
- Select: "Outbound" and "Internal - sending" in "Email messages to affect"
- In the second configuration item ("Add expressions…"), set the matching to "If ALL of the following match the message", then click ADD and add these two Advanced content match expressions:
- Location: Full headers, Match type: Does not contain text, Content: X-Scribe-Processed — prevents processing your email multiple times.
- Location: Envelope sender, Match type: Does not match regex, Regexp:
.*@google\.com$— excludes system mail such as Google Forms receipts from forms-receipts-noreply@google.com, which Google's SMTP relay rejects if routed through Scribe.
- In the third configuration item, change the route to the host you created in part 1 of this guide.
- Select: "Require secure transport (TLS)"
- Click: "Save"
.*@google\.com$
In the Compliance rule expression modal, add the info as shown in the screenshot
Configure DKIM
Configure DKIM for your sending domains to keep emails out of spam folders and avoid missing assets such as images and links.
Install team signatures
From your signatures list, install all signatures at once for your teammates or install them one by one for a progressive rollout.
Need more details? The full Google Workspace guide, with troubleshooting, is in our help centre.
FAQ
Your Google Workspace integration questions answered
Outgoing Google Workspace mail is routed through Scribe's mail relay, which adds the signature as each email leaves your organisation. Nothing is installed on teammates' devices, and recipients get the signature from every email client and device, including Apple Mail and mobile apps.
No. The signature is added after the email is sent, so it does not show in the compose window or in the Sent folder copy; the recipient always receives the full signature. Combine it with the client-side Google Workspace integration and Scribe defaults to client-side, so teammates see their signature while writing.
Yes. Outgoing emails pass through Scribe's secure servers so the signature can be added. Scribe cannot read or edit your emails: body, subject, recipients and attachments pass through unchanged. Scribe is SOC 2 Type II certified.
Yes, plan it with your IT team. Setup happens in the Google Workspace admin console: a mail routing rule sends outgoing mail through the Scribe relay, and DKIM and ARC signing must be configured so your recipients keep verifying your mail.
About 5 minutes. Follow the installation guide above: most steps happen in Google Workspace, the rest in Scribe.
Yes. Connect the Scribe MCP server to Claude, ChatGPT, Cursor or another AI assistant and it can walk you through this guide, create and assign signatures, and check that the installation went through. Authorising Google Workspace itself (admin consent, OAuth or an API key) has to be done by you, in your browser: an AI agent cannot grant that access on your behalf. See scribe-mail.com/ai-agents.
