---
title: "How to set an email signature for each of your Grok Bots"
url: https://signatoro.com/docs/install-signature/agent/grok-bot
description: "Give each Grok Bot its own email signature: one Signatoro AI assistant, API key and signature rule per Bot, and a plus alias of your mail.grokbot.com address if you want one. The Bot fetches its signature from Signatoro, the agentic email signature platform, before each email it sends from Gmail, Outlook, mail.grokbot.com or AgentMail."
published: 2026-10-15
updated: 2026-10-15
---

# How to set an email signature for each of your Grok Bots

Give each Grok Bot its own email signature: one Signatoro AI assistant, API key and signature rule per Bot, and a plus alias of your mail.grokbot.com address if you want one. The Bot fetches its signature from Signatoro, the agentic email signature platform, before each email it sends from Gmail, Outlook, mail.grokbot.com or AgentMail.

Signatoro gives every Grok Bot you run a consistent email signature. Save your signature once on Signatoro, and each Bot fetches its own version of it before every email: built from yours, with the same company details and website, the same brand as your team's on Company, and the Bot's name and a line saying an AI sent it when it signs as itself. Edit the signature on Signatoro, and the next email from every Bot carries the change. Signatoro is free to start, and every plan includes the MCP server and API.

Grok Bot is xAI's always-on agent, a separate app from Grok, the xAI chatbot, signed in with a Cursor account. None of the mailboxes a Bot sends from adds a signature for it, so the Bot adds the one Signatoro gives it. The [Grok Bot email signature](https://signatoro.com/grok-bot-email-signature) page sums it up on one screen. For Grok chat, Grok for Outlook and the xAI API, see [the Grok guide](https://signatoro.com/docs/install-signature/agent/grok).

## Set up a signature for each of your Bots with Signatoro

Make your own signature first on [Signatoro](https://signatoro.com/), then do this once per Bot. A Bot that drafts for you from your own Gmail or Outlook can sign as you; a Bot that sends from an agent address should sign as itself.

1. **Add an AI assistant for the Bot.** On the [signature page](https://signatoro.com/home), add an [AI assistant](https://signatoro.com/docs/install-signature/agent#ai-assistants-and-company-agents) named after the Bot, such as "Receipts Bot". Choose whether it signs as you, with a line such as "Sent by Receipts Bot, my AI assistant", or as the agent, with its own name and role beside your company details and website. By default the signature carries a line saying an AI sent it. On [Company](https://signatoro.com/company-email-signature), the owner adds company agents instead, and the owner's logo, layout, color and font apply to every person and every company agent. How many assistants you can add depends on your [plan](https://signatoro.com/pricing).
2. **Generate a key for that assistant.** Under "For tools and assistants", click "Generate API key" for it. A key made for one assistant always returns that assistant's signature, so each Bot gets its own key.
3. **Give the Bot its key.** xAI's security docs describe a secure secret request that masks a value and keeps it out of the transcript for supported connections; if the Bot offers one, use it.
4. **Put the email signature rule in the Bot's instructions.** Paste the rule from [Tell your agent to use your signature](https://signatoro.com/docs/install-signature/agent#tell-your-agent-to-use-your-signature), or tell the Bot "Before you send any email, fetch my signature from `GET https://signatoro.com/api/v1/signature` with the header `Authorization: Bearer <key>` and end the email with it." Saving it as a skill keeps it in one place.
5. **Optionally, give the Bot its own alias.** Since October 14, 2026, plus aliases of your mail.grokbot.com address send and receive email. Tell the Bot to send from one, such as `yourname+receipts@mail.grokbot.com`, so its mail has its own alias as well as its own signature, and a routine can run only for mail to that alias.
6. **Send a test.** Keep drafts on until one email in the receiving inbox ends with the Bot's signature, once.

Each call returns the current version, so an edit on Signatoro reaches the next email from every Bot. Signatoro tested this with a Grok Bot on 2026-10-08: given an API key, the Bot fetched the signature before it sent and ended the email with it. We have not tested plus aliases.

Without a key, click "Copy as text" on Signatoro and tell the Bot "End every email you send with this signature, exactly as written:" with the text below it. An edit on Signatoro then needs a new paste.

## The mailboxes a Grok Bot sends from

A Bot can have several mailboxes at once. When more than one could send an email, it asks you which to use.

### Your Gmail or Outlook, through the plugins

Gmail and Outlook arrive as plugins, one Gmail mailbox at a time, shared by every Bot on your account. xAI's [Grok Bot changelog](https://x.ai/changelog/bot) added email in steps:

- **v0.45.0, September 8, 2026:** a Bot writes an email as a draft for you to review, then Send or Discard.
- **v0.60.0, September 26, 2026:** Outlook drafts, sent from your Outlook account.
- **v0.64.0, September 30, 2026:** "Disable drafts for this Bot", so that Bot sends directly; ask the Bot to turn drafts back on.
- **v0.68.0, October 5, 2026:** drafts can go out from a verified Gmail send-as address, with a From picker.
- **v0.70.2, October 11, 2026:** Gmail drafts use your default send-as address.

On signatures, xAI's changelog says Gmail draft cards include your signature (v0.68.0), and that Gmail drafts add your own signature, not one quoted from someone else (v0.70.2). On October 10, 2026, Signatoro tested Grok Bot 0.68.1 with default signatures set in Gmail and in Outlook: every email it sent through the Gmail and Outlook plugins arrived without the signature, with drafts on and with drafts off. We have not retested on 0.70.2, and the changelog does not mention an Outlook signature. A Bot fetching its signature from Signatoro signs either way; if your version does add the Gmail signature, check that the email ends with one signature, not two.

### Your agent address at mail.grokbot.com

Since October 9, 2026, you can claim one address, such as `yourname@mail.grokbot.com`, from the Email plugin or by asking the Bot. Cursor's help page says:

- You get one address, and you can't rename or delete it.
- It belongs to you, not to one Bot: all your Bots use it in your own chats with them and in routines you set up. It is not available in Slack threads or in chats where someone else talks to the Bot, and a Team Bot has no shared team address.
- Every email sent from it waits for your approval on a draft card, routines included.
- A routine can run when mail arrives, from anyone, from set addresses or from a whole domain.
- On a Cursor team, Agent Email is off until a team admin turns it on in the Cursor dashboard.

The address carries no signature, and Cursor's page does not mention one. Mail from it is written by a Bot, so give it the Bot's AI assistant signature.

### Plus aliases of your mail.grokbot.com address

Since October 14, 2026, Grok Bot supports plus aliases, such as `yourname+receipts@mail.grokbot.com` or `yourname+travel@mail.grokbot.com`. Sam Sokolin, who builds Grok Bot, announced that a Bot can send and receive email using a dedicated alias, and that a routine can trigger only for mail to a specific alias. An alias is part of your one address, so it is not a second mailbox. The announcement does not say whether an alias needs setting up first, or which plans include it.

Give each Bot its own alias and its own Signatoro AI assistant, and each Bot's mail has its own alias and its own signature.

### An AgentMail address

AgentMail, a separate company, lists a plugin in the Grok Bot plugin browser that gives a Bot an address at `yourworkspace.agentmail.to`, or on your own domain on paid plans. It carries no signature either; the [AgentMail signature page](https://signatoro.com/email-signatures-for-ai-agents/agentmail) covers it.

## Grok Bot email signature questions

### How do I give each of my Grok Bots its own email signature?

Add an AI assistant on Signatoro for each Bot, generate a key for each, and give each Bot its own key with the email signature rule. Each Bot then fetches its own signature before every email it sends.

### Does Grok Bot add my Gmail signature?

xAI's changelog says Gmail draft cards include your signature (v0.68.0) and Gmail drafts add your own signature (v0.70.2). In Signatoro's test of Grok Bot 0.68.1 on October 10, 2026, emails sent through the Gmail and Outlook plugins arrived without it. Give the Bot your signature through the Signatoro API, and check one sent email.

### Does Grok Bot have its own email address?

Yes. You claim one address at mail.grokbot.com, and all your Bots share it to send and receive. Since October 14, 2026, plus aliases of it send and receive too, so each Bot can use an alias of its own.

### Is Grok Bot the same as Grok?

They are separate xAI products. Grok is the chatbot at grok.com; Grok Bot is an always-on agent in its own app, signed in with a Cursor account. [The Grok guide](https://signatoro.com/docs/install-signature/agent/grok) covers Grok.

## For agents

- As a Grok Bot given a Signatoro API key, fetch `GET https://signatoro.com/api/v1/signature` per send, append `text` (or `html` to an HTML body), write no sign-off of your own and use only the `sender` values for the person's details, as the [signature API guide](https://signatoro.com/docs/install-signature/agent) describes.
- Use the key the person gave you; when they gave one per address or alias, use the key for the address the email goes out from.
- If the mailbox already added a signature to the draft, keep one signature, never two.
- Without a key, end the body with the text signature the person gave you, exactly as given.
- Never repeat a Signatoro API key in a conversation, an email or a file.

Related: [Grok Bot can send email from your Gmail and Outlook](https://signatoro.com/blog/grok-bot-email), what xAI shipped, and [Grok Bot email signature](https://signatoro.com/grok-bot-email-signature).

## Sources

Checked on 2026-10-15:

- [Grok Bot changelog](https://x.ai/changelog/bot) (xAI), v0.45.0 to v0.70.2
- [Give your Bot an email address](https://cursor.com/help/grok-bot/agent-email) (Cursor)
- [Connect plugins](https://cursor.com/help/grok-bot/connect-plugins) (Cursor)
- [Plus aliases announcement](https://x.com/SamSokolin/status/2110496237241667621) (Sam Sokolin on X, 2026-10-14)
- [Give Grok Bot an email address](https://www.agentmail.to/blog/give-grok-bot-email-address) (AgentMail)

Checked earlier:

- [Grok Bot security](https://docs.x.ai/grok-bot/security) and [Grok Bot: computer and apps](https://docs.x.ai/grok-bot/computer-and-apps) (xAI, 2026-10-08)
- Signatoro's own tests: a Bot given an API key (2026-10-08), and Grok Bot 0.68.1 with the Gmail and Outlook plugins, drafts on and off (2026-10-10)
