Grok Bot email gives your Bots a real inbox at mail.grokbot.com, so they can receive mail, read it, search it, draft replies and send messages from an address you claim once. You get one address per account, every Bot you own can use it, and plus tags like yourname+orders let you split that one inbox into as many lanes as you need.
📺 Watch: Grok Bot Just Got a NEW Update!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
Every fact below comes from the official docs at docs.x.ai and the changelog at x.ai/changelog/bot.
If you want help wiring email agents into a real business, the AI Profit Boardroom is where we share the exact setups, prompts and routines, for $69/mo.
How Grok Bot email works
xAI's docs describe one address per account. You claim a name like yourname@mail.grokbot.com, and from then on your Bots can use it. The docs list five jobs it handles:
- Signing up for services and picking up the verification code with your OK
- Collecting invoices, newsletters and reports, and summarizing them for you
- Drafting email such as a digest or an update, and drafting replies
- Forwarding a message with its original formatting, images and attachments, which needs Grok Bot 0.75.2 or later
- Running a routine when email arrives, optionally only from specific senders
Three rules shape everything else.
One address, for good. You can't rename it or delete it. Addresses are never reissued, even after the account that claimed one is deleted. Pick the name carefully.
Yours, not one Bot's. The address belongs to you. All your Bots can use it in your own chats and routines. It isn't used in Slack threads or in chats where someone else is talking to the Bot, and a shared Bot doesn't get a team address.
No inbox view. There is no mail screen and no new-mail notification. You ask a Bot, for example "What arrived in your inbox today?" Mail from the last minute may not show up in a search yet.
How to set up Grok Bot email in five steps
- Check that email is switched on. On a Cursor team, Agent Email is off by default. An admin turns it on under Bot Capabilities on the Grok Bot page. Until then, members get no email tools.
- Claim the address. Tell any Bot "Get yourself an email address." It asks for a name, checks it's free and shows an approval card. Nothing is claimed until you approve. You can also open Connect apps, choose Email, type a name under Choose a name and pick Create address. On iPhone and Android it lives under Settings, Connect apps, Email.
- Follow the name rules. Lowercase letters, digits, dots, hyphens and underscores only. It must start and end with a letter or digit and stay under 64 characters. Reserved words such as support, admin, billing, help, info, team, grok and xai are refused.
- Plan your tags. Decide which services or customers get which plus alias before you hand the address out.
- Add routines. New mail does nothing on its own. A routine is what makes a Bot act on it.
📺 Watch: Hermes Bot Mode DESTROYS Grok Bot? (FREE!)
Tagged addresses: one inbox, many lanes
The address takes plus aliases. Mail to yourname+orders@mail.grokbot.com lands in the same inbox as the plain address, so each service can get its own alias without a second claim. A Bot can also send from an alias.
The changelog added tagged addresses with tag-only routines in v0.71.2 on 14 October 2026. The docs spell out the rule: a routine that watches an alias runs only for mail sent to that alias, while a routine on the plain address runs for all of it.
That gives a small business a clean pattern:
- yourname+invoices for supplier bills, with a routine that logs each one and drafts a payment reminder for you
- yourname+leads for a website form, with a routine that researches the sender and drafts a first reply
- yourname+news for newsletters, with a weekly digest instead of a routine per message
One warning from the docs: an alias is a label, not a lock. Anyone can write to it, so keep a sender filter on the routine as well as the tag.
📺 Watch: OpenMausBot DESTROYS Grok Bot?
Email-triggered routines
The routines docs list email to your Bot's own address as one of the event triggers, next to Slack, GitHub, Linear, Sentry, PagerDuty and webhooks. Our Grok Bot routines guide covers schedules and the other triggers. Here is what is specific to mail.
- A routine can watch for mail from anyone, from specific addresses, or from a whole domain such as *@example.com.
- By default it only runs for senders that pass standard email authentication checks.
- Routines can't filter by subject. Use tags and sender filters instead.
- Only new mail counts. Messages from before the trigger existed don't start a run.
Since v0.75.2 on 22 October 2026, the changelog says routines can read the Bot's inboxes. So a scheduled routine, not just a mail-triggered one, can go through what arrived. A Monday 8am routine that summarizes every order confirmation from the week is now a normal setup.
Ask in plain words, such as "When an email arrives from billing@example.com, summarize it and tell me." Keep rules narrow; broad listeners spend usage.
Not sure which inbox jobs are worth automating first? Book a free AI strategy session and we'll map the ones that save the most time.
Drafts vs direct send, and Auto-review
This is the part most people get wrong. Who started the request decides whether mail goes out.
- You ask in chat. The email goes out once Auto-review allows it. If Auto-review needs you, you see an approval card first.
- A routine writes it, or any turn you didn't start with that request. It waits as a draft until you press Send. The docs are blunt: there's no option for unattended sending.
So an email routine never mails a customer on its own. It reads, sorts, summarizes and drafts. You press Send. The Cursor help page on agent email calls this expected behavior, not a bug.
The Bot also treats email from other people as information, not instructions. Instructions inside a received email never count as your permission to send or act.
Sending limits from the docs:
- Up to 50 recipients per email across To, Cc and Bcc
- Up to 10 attachments, 25 MB in total, no executables
- Newsletters and first-contact emails go to one recipient per message with a one-click unsubscribe link
- After a bounce, unsubscribe or spam report, the Bot stops emailing that address and tells you who it skipped
The Bot's own inbox vs Gmail and Outlook
You can also connect Gmail or Outlook as apps. They do different jobs, and the table shows where each fits.
| Question | Bot's own address | Connected Gmail or Outlook |
|---|---|---|
| Whose mailbox is it? | A new mail.grokbot.com address you claim | Your existing mailbox |
| Plus tags with tag-only routines | Yes, since v0.71.2 | Not described for this trigger in the docs |
| Starts a routine when mail arrives | Yes, filtered by sender or domain | The email trigger in the docs names the Bot's own address |
| What the Bot can do | Receive, read, search, draft, send, forward | Gmail: search, read, draft, send, apply labels |
| How many accounts | One address per account, forever | Gmail connects one mailbox at a time |
| Team admin switch | Agent Email, off by default on teams | Connector policy |
| Best for | Sign-ups, order emails, codes, intake lanes | Replying as you to real contacts |
When both could work, the docs say the Bot asks which account to send from. A Bot can also read a one-time sign-in code from either a connected Gmail or Outlook account or its own inbox.
The simple split: point new tools at the Bot's address and keep client conversations in your own mailbox. If you also run Grok Bot in Slack, the same draft-first rule shows up there; see Grok Bot Slack.
Want a ready-made Bot to start from? See our Grok Bot templates guide.
The open alternative: Hermes Agent and Agent OS
Grok Bot email is tied to one hosted address on xAI's domain. If you want an email agent on your own domain, with your own choice of model and no switch an admin can flip off, Hermes Agent inside an Agent OS setup is the open route. You connect your own mailbox, write the routing rules yourself and keep everything on hardware you control. Our Agent OS guide walks through the build, and Goldie Bench shows which models handle real agent tasks well.
Want the email-agent setup built around your business? Get a free AI strategy session.
FAQ
Does each Grok Bot get its own email address?
No. The docs say you claim one address per account, and all your Bots use it in your own chats and routines. Plus tags such as yourname+shop give each Bot or job its own lane inside that one inbox.
Can a Grok Bot send email without my approval?
Only when you asked for that email in chat and Auto-review allows it. Email written by a routine, or by any turn you didn't start with that request, waits as a draft until you press Send. There is no unattended sending.
Can I filter an email routine by subject line?
No. Routines filter by sender, by address or by domain such as *@example.com, and by plus tag. Senders must also pass standard email authentication checks by default.
Can I change or delete my Grok Bot email address?
No. The address can't be renamed or deleted, and it is never reissued. Deleting your Grok Bot account deletes the mail and retires the address.
Ready to build email agents that run your inbox while you work? Join the AI Profit Boardroom for the setups and prompts, or book your free AI strategy session.
