Grok Bot Email: Claim, Tag And Automate Your Bot Inbox (2026)

Grok Bot email gives your Bots one real inbox at mail.grokbot.com, and you can claim it, tag it and wire it to a routine in six moves.

The official computer and apps docs say your Bots can receive, read, search and send mail from that address.

This is the order I would set it up in, so nothing leaves without you and nothing fires off the wrong sender.

If you want my team to look at where an agent inbox fits in your business, book a free SEO strategy session and we will map it with you.

What you actually get when a Bot has an address

You get one address per account, in the shape yourname@mail.grokbot.com.

Every Bot you own can use it, in your own chats and in your own routines.

The docs list five jobs for it: signing up for services, collecting receipts and reports, drafting mail, forwarding mail, and starting a routine when something lands.

It is not a full mail client.

There is no inbox view and there are no new-mail notifications.

You ask a Bot what came in, for example "What arrived in your inbox today?", and it reads the inbox for you.

Grok Bot itself comes with the Premium, Super and Ultra plans, and not with Plus, per the X subscription page.

Step 1: pick a name you can live with forever

This is the step that matters most, because the address is permanent.

You cannot rename it and you cannot delete it.

Used addresses are never reissued either, even after the account that claimed one is deleted.

Names take lowercase letters, digits, dots, hyphens and underscores.

A name must start and end with a letter or a digit, and it maxes out at 64 characters.

Reserved words are refused, including support, admin, billing, security, help, info, team, cursor, grok and xai.

My pick: your business name or your own name with a short suffix, never something tied to one project you might drop next month.

Step 2: claim it through chat or Connect apps

Fastest route: tell any Bot "Get yourself an email address."

It asks which name you want, checks the name is free and shows an approval card.

Nothing is claimed until you approve that card.

Manual route on desktop: open Connect apps, choose Email, type the name in Choose a name under Email address, then press Create address.

On iPhone or Android, go to Settings → Connect apps → Email.

Once it is live, the app shows the address next to a copy button.

The Grok Bot changelog dates the feature to v0.70.2 on October 11, 2026, with sent mail waiting for approval on a draft card from day one.

Fix each claim error in one move

Message you see	What to do
That address is taken, and addresses are never reissued…	Pick a different name. Retrying the same one can never work.
You can have one agent email address.	You already own one. Ask your Bot for it or open the Email app.
Couldn't create your email address. Try again. (phone)	Recheck the name rules, or try on desktop, which shows the exact reason.
Too many email addresses checked in the last minute.	Wait a minute, then try again.
Agent email is not enabled for this account.	It is not available on your account yet.
Your team admin has turned off Grok Bot agent email…	Ask your admin to switch on Agent Email.

A message about characters, length or a reserved word means the name broke a rule from Step 1.

🔥 Want the full agent inbox playbook, not just the settings? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members wiring agents into real email workflows. → Join the AI Profit Boardroom

Step 3: give every service its own plus alias

Plus aliases are the setting I would switch on in practice from day one.

Mail to yourname+receipts@mail.grokbot.com lands in the same inbox as the plain address.

So give each service its own tag: +receipts for billing mail, +news for newsletters, +signup for trial accounts.

You never need a second address for this.

The Bot can send from an alias too, a change that shipped in v0.71.2 on October 14, 2026.

The real payoff shows up in routines: a routine watching an alias fires only for mail sent to that alias.

A routine on the plain address fires for all of it.

Gotcha: an alias keeps nobody out

Treat every alias as a sorting tag, nothing more.

Anyone who learns your +receipts tag can write to it, and a routine on that tag will see their message.

So any routine that should act only for certain senders needs a sender filter on top of the alias.

The docs put it bluntly: keep a sender filter on those routines.

I would add one to every routine that can draft, forward or file anything.

Step 4: wire a routine to incoming mail

New mail never opens a chat or wakes a Bot by itself.

To act on it you need a routine with an email trigger, which the event trigger docs list next to Slack, GitHub, Linear, Sentry, PagerDuty and webhooks.

The trigger can watch mail from anyone, from named addresses, or from a whole domain such as *@example.com.

By default it only runs for senders that pass standard email authentication checks.

It cannot filter by subject line, so build your filters out of senders and aliases.

Only new activity counts: mail that arrived before the trigger existed will not start a run.

Here is the kind of brief I would paste into the chat with the Bot that owns the job:

When an email arrives at yourname+invoices@mail.grokbot.com
from *@yoursupplier.com, read the attached invoice, log the
invoice number and due date in my invoices sheet, and draft a
short confirmation reply. Never send anything without my OK.

After saving, open the routine and check that When to run describes the trigger the way you meant it.

For schedules, tests and the hourly caps, follow my Grok Bot routines setup guide.

Step 5: decide how sending works before the first draft

There are two sending paths, and you should know both.

In chat: when you ask a Bot to send an email, it goes out once Auto Review allows it, and if Auto Review needs you, an approval card shows up first.

Everywhere else: mail from a routine, or from any turn you did not start with that request, waits as a draft until you press Send.

There is no option for unattended sending.

If Gmail or Outlook is connected too, the Bot asks which account to send from whenever either could work.

Since v0.77.0, auto-review approval cards stay open for 30 minutes instead of 10.

Add a standing rule on top: the Bots page gives "Always ask before you send an email" as the kind of rule a Bot keeps in memory.

📞 Want a second pair of eyes on your email automations? Book a free SEO strategy session and my team will look at which inbox jobs are worth handing to an agent first. → Get your free strategy session

Learn the sending and attachment limits now

Up to 50 recipients per email, counted across To, Cc and Bcc.
Outgoing mail carries up to 10 attachments, 10 MB each and 25 MB in total, and executable files are blocked.
Newsletters and first-contact emails go to one recipient per message, with a one-click unsubscribe link.
A bounce, an unsubscribe or a spam mark stops the Bot emailing that address, and it tells you who it skipped.
There is also a cap on how many new people a Bot can email, to protect the address.
Incoming mail keeps up to 10 attachments, 10 MB each and 25 MB in total, and skips anything over that.

Plan reports and exports around the 25 MB ceiling instead of finding it on a deadline.

How the Bot treats mail from strangers

Anyone can send mail to the address.

A message that fails the spam or virus scan is kept without its body or attachments, and it never starts a routine.

Every message the Bot reads is marked as coming from you or from someone else.

Instructions inside an email never count as your permission to send or act.

To the Bot, mail from other people is information, not orders.

One small catch for testing: mail from the last minute may not show up in a search yet, so wait before you ask about it.

Forwarding needs Grok Bot 0.75.2 or later

Forwarding keeps the original formatting, images and attachments.

It needs Grok Bot 0.75.2 or later, and the v0.75.5 release on October 23, 2026 is titled "Vault, email forwarding, and fewer approval cards".

If a forward fails, update the app before you change anything else.

A forward is still a send, so the draft and approval rules from Step 5 apply to it.

Where the address will not work

It is not used in Slack threads.

It is not used in chats where someone else is talking to your Bot.

A shared Bot has no team address.

On a team account, Agent Email is off by default, and an admin switches it on before members can claim an address.

If the admin turns it off later, Bots lose their email tools and email routines stop, but mail to existing addresses is still received and kept, and members keep their addresses.

Delete your Grok Bot account and your mail and attachments are deleted, and the address is retired.

Step 6: run a live test before you trust it

Send one message from an address your filter allows, to the alias the routine watches.

Give it a couple of minutes, because the newest mail can lag behind in search.

Open the owning Bot's chat and check that the routine ran and left the draft you expected.

Next, send one from an address outside the filter and confirm nothing runs.

Then send one to the plain address and confirm the alias routine stays quiet.

If an allowed sender never triggers anything, check that its domain passes standard email authentication, because routines skip senders that fail it by default.

Only after all three tests pass would I point a real supplier or service at the alias.

Repeat the same three tests every time you edit a filter.

My first-week setup checklist

Write down three name options and check them against the rules.
Claim the address through chat and approve the card.
Assign one plus alias to each service you sign up for.
Save the "Always ask before you send an email" rule in your Bot's memory.
Build one email routine with an alias and a sender filter.
Send a test from an allowed sender and read the draft it produces.
Ask the Bot each morning what arrived, until the routine earns your trust.

If you want the trainings and coaching calls that take this further, the AI Profit Boardroom walks through agent workflows step by step.

Also On Our Network

FAQ: Grok Bot Email

How do I claim a Grok Bot email address?

Ask any Bot "Get yourself an email address", pick a name and approve the card. On desktop you can also use Connect apps, Email, Choose a name, then Create address.

Can I change my Grok Bot email name later?

No. The address cannot be renamed or deleted, and used addresses are never reissued, so choose the name carefully.

Can a routine filter Grok Bot email by subject?

No. Email routines filter by sender, by address or by domain, plus the alias the mail was sent to, but not by subject.

Will my Bot send email on its own from a routine?

No. Email from a routine waits as a draft until you press Send, and there is no option for unattended sending.

Why does forwarding fail on my Bot?

Forwarding needs Grok Bot 0.75.2 or later. Update the app first, then try the forward again.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Claim the name once, tag every service, filter every routine by sender and keep sends behind approval, and if you want help choosing what to automate, book a free SEO strategy session to plan your Grok Bot email setup.