Grok email signature
Grok and Grok Bot send email from your Gmail or Outlook account. Signatoro gives them your real signature, the same one your team uses.
How Grok sends email
In a Grok chat, the Gmail and Outlook connectors read, draft and send email. xAI says the Gmail connector starts read-only and drafts, sends, replies and forwards once write and send permissions are enabled. The Outlook connector drafts and sends from a Microsoft work or school account.
Grok Bot, an always-on agent xAI launched in beta on August 11, 2026, sends through the Gmail or Outlook account you connect. Since version 0.64.0 of September 30, 2026, a draft card offers "Disable drafts for this Bot", and that Bot then sends without showing you the email first.
Grok for Outlook, an add-in, writes drafts in Outlook's own compose window and you send them. On the xAI API, email goes through a function your code defines.
Why emails Grok sends have no signature
Gmail and Outlook add your saved signature in their own compose windows. Google's Gmail API reference says the Gmail signature is included in messages composed in the Gmail web interface. A connector or a Bot sends through the mail provider's API, outside that window, so the email ends wherever Grok's text ends: no title, no phone number, no company line and no legal footer.
Pictures are the second gap. Signatoro has found that the Gmail tool built into chat assistants drops every image from the HTML it is given, so for these emails the text signature is the one that arrives intact.
How Signatoro gives Grok your signature
You keep one signature on Signatoro, and Grok, Grok Bot and your own code all read it.
- Agentic sending: click "Copy as text" on Signatoro and tell Grok or your Bot "End every email you send with this signature, exactly as written." Keep drafts on until one test email in your Sent folder ends with it, once.
- API fetch and sync: your code calls the Signatoro signature API before each send and appends the HTML or text it returns, so every email carries the current version.
- MCP: xAI lets you add your own MCP server by URL under Grok's connectors, and Signatoro's is https://signatoro.com/mcp. Sign in once, and Grok can fetch your saved signature with get_signature.
- Grok for Outlook: set your signature in Outlook for new messages and for replies, and Outlook adds it to every draft.
- Company signatures: an owner sets the name, logo, layout and, on the Up to 15 plan or larger, one footnote line for everyone, and every fetch through the API or MCP carries them.
When an email from Grok should say AI sent it
A Bot with drafts off sends from your address with nobody reading first. Whether that email should say an AI wrote or sent it generally depends on where you are and what the email does. The disclosure guide covers what the rules typically ask, and a footnote line on Signatoro can carry the wording on every email.
Grok email signature questions
Can Grok send emails from my Gmail?
Yes, once send permission is granted. The Gmail connector starts read-only, and xAI says drafts, sending, replying and forwarding come with write and send permissions. Grok Bot sends through the Gmail account you connect to its plugin.
Why don't emails from my Grok Bot include my signature?
Gmail and Outlook add your signature in their own compose windows, and a Bot sends outside them. Give the Bot your signature as text, ask it to end every email with it, and check one sent email before you turn drafts off.
Can Grok use my Gmail signature?
Gmail adds it only to email written in its own compose window, so a Grok for Outlook draft or a Gmail draft you send yourself gets it. Email a connector or a Bot sends needs the signature in the text Grok writes.
Does Grok Bot have its own email address?
As of October 7, 2026, a Bot sends from the Gmail or Outlook account you connect. A Bot-owned address comes from AgentMail, an independent company whose plugin gives a Bot an address of its own.
How do I keep my signature current in every email Grok sends?
Have Grok or your code fetch it from Signatoro at send time, through the API or the MCP server. Each fetch returns the version saved on Signatoro, so an edit there reaches the next email.
Sources
Checked against xAI, Google and Microsoft documentation on October 7, 2026.