What xAI launched
- Each Grok Bot can claim an address like yourname@mail.grokbot.com.
- Grok Bot uses it to sign up for services, read verification codes, contact businesses and schedule time with people.
- To claim one, ask Grok Bot, or tag @bot on X. On a team account, an admin has to turn it on first.
A day after launch, xAI's support and early users filled in the limits. You get one address per account, and all your bots share it. You pick the name once and cannot rename or delete it later. Addresses with a plus or an underscore suffix do not arrive. There is no screen to read the inbox. You ask the bot what came in.Sources[5]Grok Bot support email on agent email limits, shared on X[6]Dave Gambrill on X: notes after setting up a Grok Bot address[7]Nun0x on X: no way to open the Grok Bot inbox
Which plans include it, how long mail is kept and how much Grok Bot can send are still not documented.Sources[2]TeslaNorth: Grok Bot starts handing out its own email inboxes[3]AlphaSignal: xAI gives Grok Bot its own email inbox
Where a mail.grokbot.com address falls short
For sign-ups, trials and verification codes, the built-in inbox is enough. It keeps that mail out of your own inbox, which is the point. The problems start when the address talks to people who matter to your business.
- It is not your domain. A supplier or a customer sees an email from mail.grokbot.com, not from your company. xAI has not announced own-domain support.
- It shares a reputation. Every Grok Bot sends from the same new domain, so one bot that spams can hurt delivery for everyone else's.
- It stays with xAI. If you move to another agent next year, the address and the replies people send to it stay behind.
- One address for all your bots. A bot that handles support and a bot that handles invoices end up sharing the same inbox.
- You cannot open it. To check what your bot sent a customer, you have to ask the bot.
There is also the risk every agent inbox has. Anyone who knows the address can email it, and a message can contain text written to look like an instruction. Keep what the agent is allowed to do small, whichever inbox it uses.[3]
Three ways to give Grok Bot email
Give Grok Bot an address on your domain
Create a mailbox such as bot@yourcompany.com in Shipmail and connect Grok Bot to only that mailbox. Its mail then goes out from your domain, replies land in a mailbox you own, and you or a teammate can open it any time.
- Step 1 - Create the mailbox- Add bot@yourcompany.com in Shipmail. Solo is $4/month and includes 2 mailboxes, one for you and one for Grok Bot.
- Step 2 - Add the connector on grok.com- Open Connectors, choose New Connector, then Custom, and enter https://shipmail.to/api/mcp. Grok Bot uses the connectors on your Grok account.
- Step 3 - Sign in as the bot's mailbox- On the Shipmail sign-in page, use the bot mailbox's address and password. The connection then reaches that one mailbox and nothing else.
- Step 4 - Pick the permissions- Start with Read and draft. Grok Bot writes drafts, and you send them. Move to sending once you trust what it writes.
Start Grok when new mail arrives
A connector lets Grok read the mailbox when it is working. To have it start on its own when an email lands, use a Grok automation with a Webhook trigger. Each trigger has its own URL and signing secret, and Grok only runs requests signed with that secret.[4]
- Step 1 - Create the automation in Grok- On grok.com, open Automations and create one. Add a Webhook trigger, check that the Shipmail connector is on, and write the instructions, for example: "When this fires, the body has the sender, subject and message ID of a new email. Open that email in bot@yourcompany.com with the Shipmail connector. Answer it as a draft if it is a simple question, otherwise send me a summary." Save it, then copy the endpoint and the signing secret. Grok shows the secret only once.
- Step 2 - Add a webhook in Shipmail- Under Developer, then Webhooks, create a webhook with the automation's endpoint, the message.received event and only the bot's mailbox. Paste Grok's secret, which starts with whsec_, into Standard Webhooks signing secret.
- Step 3 - Send a test- Use Send test event on the webhook, then email the bot's address from your own. Grok accepts the event right away and queues a run. In our test, the run showed up under Executions a few minutes later.
Keep it safe
- Connect only the bot's mailbox, by signing in with its own password. Your inbox stays out of reach.
- Keep Read and draft until you have read a few weeks of its drafts.
- Scope the webhook to the bot's mailbox, so nothing else starts the automation.
- Revoke the connection under Developer, then Connections, if something looks wrong. No password change needed.
Start a 14-day trial
Create a mailbox for Grok Bot on your own domain.
Sources
- Grok Bot: Grok Bot now has its own emailxAI's announcement that Grok Bot can claim its own address on mail.grokbot.com to sign up for services, contact businesses and schedule time, rolling out on October 9, 2026. Verified 2026-10-09
- TeslaNorth: Grok Bot starts handing out its own email inboxesLaunch coverage: claim an inbox by asking Bot, team admins must enable it, and plans, send caps, send approval and own-domain support are not documented. Verified 2026-10-10
- AlphaSignal: xAI gives Grok Bot its own email inboxLaunch analysis: no xAI documentation on sending limits, retention or send approval, sending reputation shared across mail.grokbot.com, and addresses tied to xAI's product. Verified 2026-10-09
- xAI docs: Grok automation webhooksxAI's reference for Grok automation Webhook triggers: each trigger has an endpoint and a whsec_ signing secret, requests must carry Standard Webhooks webhook-id, webhook-timestamp and webhook-signature headers within five minutes, bodies are capped at 1 MiB, and an accepted request returns 202. Verified 2026-10-10
- Grok Bot support email on agent email limits, shared on XA Grok Bot support reply posted by a user: one address per user shared across their bots, addresses cannot be renamed or deleted, allowed characters, and reserved names. Verified 2026-10-10
- Dave Gambrill on X: notes after setting up a Grok Bot addressHands-on notes: one permanent address, plus and underscore aliases did not arrive, new mail does not wake the bot without a routine, and inbound mail took a few minutes at first. Verified 2026-10-10
- Nun0x on X: no way to open the Grok Bot inboxUser report that the Grok Bot inbox has no webmail or login, so the only way to see what came in or went out is to ask the agent. Verified 2026-10-10
- AgentMail: give your Grok Bot its own email addressAgentMail's guide to adding its native plugin to Grok Bot. Verified 2026-10-09
- AgentMail pricingAgentMail plan prices and limits for inboxes, domains, storage, and email. Verified 2026-10-06
- Shipmail MCP server docsOfficial Shipmail MCP server tools, resources, prompts, and install steps. Verified 2026-07-29
- Shipmail MCP permissions and securityHow Shipmail limits an MCP connection: Read and draft, Mail assistant, Full access or Custom permissions, mailbox-password sign-in limited to one mailbox, and revoking under Developer, Connections. Verified 2026-10-01
- Shipmail webhooks documentationShipmail webhook events such as message.received, mailbox and domain scoping, signing, retries, and the optional Authorization header sent with each delivery. Verified 2026-10-09
- Shipmail pricingShipmail plan prices, mailbox limits, team access, and send limits. Verified 2026-07-29
Questions worth answering
Common questions about Grok Bot email.
How do I get a Grok Bot email address?
Ask Grok Bot to claim an inbox, or tag @bot on X. The address ends in @mail.grokbot.com. On a team account, an admin has to enable the feature first.Sources[1]Grok Bot: Grok Bot now has its own email[2]TeslaNorth: Grok Bot starts handing out its own email inboxes
Can Grok Bot use my own domain?
xAI has not announced own-domain support for the built-in inbox. To use your domain today, connect a mailbox on your domain through Shipmail's MCP connector instead, and Grok Bot reads and sends from that address.Sources[2]TeslaNorth: Grok Bot starts handing out its own email inboxes[10]Shipmail MCP server docs
Can I see what Grok Bot received and sent?
With a Shipmail mailbox, yes. It is a normal mailbox: open it in the Shipmail app or any mail client, and a teammate can take over a thread.[10]
Can Grok Bot react as soon as an email arrives?
Yes. Point a Shipmail webhook for message.received at the Webhook trigger of a Grok automation, and paste the trigger's signing secret into the Shipmail webhook. The event carries the sender, subject and message ID, and the automation opens the email through the Shipmail connector.Sources[12]Shipmail webhooks documentation[4]xAI docs: Grok automation webhooks
Related guides
More on Shipmail pricing, comparisons, and team workflows.