Grok Bot 如何绑定自有域名邮箱:Shipmail MCP 连接器与 Webhook 自动化指南
Grok Bot has its own email now. How to put it on your own domain
xAI 于 10 月 9 日让 Grok Bot 拥有自己的邮箱,地址统一以 @mail.grokbot.com 结尾,可用于注册、试用和验证码。
Blog
Short answer
Ask Grok Bot to claim an inbox and it gets an address ending in @mail.grokbot.com. That is fine for sign-ups and tests. For mail that goes to customers or partners, give Grok Bot a mailbox on your own domain instead: connect it through Shipmail's MCP connector, and add a Shipmail webhook that starts a Grok automation when new mail arrives.
On October 9, xAI gave Grok Bot its own email address. Grok Bot can now sign up for services, contact businesses and schedule meetings from an inbox that is not yours. It is a good idea, and we have been telling people to give their agent its own address for a while. The catch is the domain. Every address ends in @mail.grokbot.com, and for anything a customer sees, you want it on yours.
By Julien CoulaudPublished October 10, 2026
- AI agents
- Grok Bot
- Business email
Founder of Shipmail. Building business email hosting for solo founders and small teams.
On this page
- 01What xAI launched
- 02Where a mail.grokbot.com address falls short
- 03Give Grok Bot an address on your domain
- 04Start Grok when new mail arrives
- 05Keep it safe
What xAI launched
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.
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
| Option | Address | Your own domain | Best for |
|---|---|---|---|
| Grok Bot's own inboxSources[1]Grok Bot: Grok Bot now has its own email[2]TeslaNorth: Grok Bot starts handing out its own email inboxes | name@mail.grokbot.com | Not announced | Sign-ups, trials and verification codes |
| AgentMail pluginSources[8]AgentMail: give your Grok Bot its own email address[9]AgentMail pricing | An AgentMail address, or your domain from $20/month | On paid plans | Developers building inboxes for many agents |
| ShipmailSources[13]Shipmail pricing[10]Shipmail MCP server docs | bot@yourcompany.com, from $4/month | Yes | A business that wants the bot's mail on its domain, in a mailbox people can open too |
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.
Sources[10]Shipmail MCP server docs[11]Shipmail MCP permissions and security[13]Shipmail pricing
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.
Sources[12]Shipmail webhooks documentation[4]xAI docs: Grok automation webhooks
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.
Sources[11]Shipmail MCP permissions and security[12]Shipmail webhooks documentation
Next step
Start a 14-day trial
Create a mailbox for Grok Bot on your own domain.
Sources
- Grok Bot: Grok Bot now has its own email
xAI'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 inboxes
Launch 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 inbox
Launch 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 webhooks
xAI'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 X
A 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 address
Hands-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 inbox
User 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 address
AgentMail's guide to adding its native plugin to Grok Bot.
Verified 2026-10-09
- AgentMail pricing
AgentMail plan prices and limits for inboxes, domains, storage, and email.
Verified 2026-10-06
- Shipmail MCP server docs
Official Shipmail MCP server tools, resources, prompts, and install steps.
Verified 2026-07-29
- Shipmail MCP permissions and security
How 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 documentation
Shipmail 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 pricing
Shipmail plan prices, mailbox limits, team access, and send limits.
Verified 2026-07-29
FAQ
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
Can Grok Bot send email without asking me?
Not if you connect with Read and draft. Grok Bot can then only leave drafts, and you send them.[11]
Related guides
More on Shipmail pricing, comparisons, and team workflows.
来源:Hacker News · shipmail.to