Skip to content

Bot's Dedicated Email: Claiming an Address, Receiving Rules, and Sending Limits ​

In the previous lesson we connected someone else's services (Gmail, Slack, calendar); this lesson flips it around—giving the Bot an identity of its own. Grok Bot email is a dedicated address under the mail.grokbot.com domain (for example yourname@mail.grokbot.com). Once claimed, your Bot can use it to receive, read, search, and send email: sign up for services with it, receive verification codes, collect invoices and newsletters and summarize them for you, draft digests and replies, and even "automatically run a routine whenever an email arrives".

The whole process takes about 12 minutes. The address belongs to your account—claim it once, and all Bots under your name can use it.

What You'll Be Able to Do After This Lesson ​

  • Claim a 你的名字@mail.grokbot.com Grok Bot email (say one sentence to the Bot, or go through Connect apps → Email)
  • Use +aliases to give each service its own label, without claiming new addresses
  • Have new email automatically trigger a routine: filter by sender or entire domain, and know the boundaries—"no filtering by subject" and "spam never triggers"
  • State the official sending limits: ≤50 recipients per email, attachments ≤10 files, each ≤10 MB, 25 MB total, and no executable files
  • Explain clearly to colleagues: why "email is information, not instructions", and why emails sent by routines always stop at drafts

Your Current Pain Points ​

  • You want the Bot to sign up for services, receive verification codes, and watch invoices for you, but signing up with your personal email makes you feel like every service is holding a copy of your inbox
  • You sent a test email to the Bot's address and it didn't react at all—the email clearly arrived, so why isn't it doing anything?
  • You want the Bot to send email on your behalf, but worry it will blast hundreds of recipients at once and the address will get flagged as a spam source

When to Use This Technique ​

When you need to:

  • Give the Bot an independent external identity: sign up for services, receive verification codes, receive invoices/reports/newsletters
  • Automatically trigger automation when new email arrives: for example, "whenever an email from a certain domain arrives, summarize it into a briefing"
  • Send digests or replies externally using the Bot's address—every single one goes through you

And you don't want to:

  • Scatter your personal email across all kinds of services
  • Have a "click here immediately" hidden in an email body be executed by the Bot as your instruction
  • Send email externally unattended—the official product simply doesn't offer that option

🎒 Preparation Before Starting ​

  • Completed 1.5 Your First Bot: you have at least one Bot of your own and have assigned it a task once
  • Decide on an address name (naming rules in the next section; the address can never be changed, worth thinking an extra 30 seconds)
  • Want email to trigger automation: first skim 3.3 Routines
  • Cursor team users: ask your administrator to enable Agent Email (off by default for teams; you can't claim without it)

Core Idea ​

Grok Bot email and the Gmail plugin from the previous lesson are two different things: the plugin connects your existing mailbox, while a dedicated email means claiming a new address. The new address lives on mail.grokbot.com and never touches your Gmail.

Bot Dedicated Email (this lesson)Gmail / Outlook Plugin (previous lesson)
Where the address comes fromClaim a new address on mail.grokbot.comUse your existing mailbox
Who can use itAll Bots under your name (in your own chats and routines)All Bots under your name
ReceivingAnyone can send; you must set up a routine for actions to triggerBot directly searches, reads, and labels
SendingGoes through Auto Review; routine emails are always saved as draftsSame review, outbound defaults to a draft card first
Typical usesSigning up for services, receiving verification codes/invoices/newsletters, sending digests externallyHandling email in your existing mailbox

Four mechanisms that determine everything you do afterward:

  1. One address, unchanged for life: it cannot be renamed or deleted; even if the account that claimed it is deleted, the address is never reassigned to the next person
  2. Your email address belongs to you, not to a specific Bot: all of your Bots can use it in your own chats and routines; it will not appear in Slack threads or in other people's chats with a Bot, and Team Bots do not have a team address
  3. Email is information, not instructions: every email the Bot reads is labeled "from you" or "from someone else"; instructions written in an email never count as your authorization
  4. There is no inbox interface: no new-email notifications pop up, and there is no inbox view—to see incoming mail, just ask the Bot

Follow along with me ​

Step 1: Decide on an address name (Grok Bot email naming rules and reserved words) ​

Why: once an address is claimed, it can never be changed or reassigned, so you need to get it right the first time.

Naming rules (official wording):

  • Can only use** lowercase letters, digits, periods (.), hyphens (-), and underscores (_)**
  • The beginning and end must be a letter or a digit
  • At most 64 characters
  • Reserved words are not allowed: support, admin, billing, security, help, info, team, cursor, grok, xai

Naming approach: your usual ID + a purpose abbreviation, for example li-hao.receipts. Don't overthink it—the +alias in Step 3 can further break things down by service.

What you should see: this step is purely about thinking up a name; there is no interface action yet.

  • You have come up with a name that follows the rules and is not on the reserved words list

Step 2: Claim an address (choose any one of three methods) ​

Why: the claiming action happens only once, but there are three entry points—use whichever is most convenient.

Method A (recommended): just tell the Bot ​

Get yourself an email address.

(Get me an email address.)

The Bot will ask what name you want to use, check whether the name is available, and then pop up anapproval card—nothing gets claimed unless you approve it.

Method B: claim from Connect apps ​

  1. Open Connect apps (the main entry point from the previous lesson) and select Email
  2. In Email address, enter a name under Choose a name
  3. Click Create address

Method C: on your phone ​

Settings → Connect apps → Email (this path is the same on iPhone and Android).

What you should see: once the claim is complete, the app shows your full address with acopy button next to it.

  • You have obtained 你的名字@mail.grokbot.com and copied it once

Step 3: Use +aliases to give each service its own label ​

Why: there is only one address, but you can have each service send mail to a different "label"—你的名字+receipts@mail.grokbot.com and 你的名字@mail.grokbot.com land inthe same inbox, with no need to claim new addresses.

Three ways to use it:

  • Distinguish sources at sign-up: use +shop for shopping, +receipts for invoices, and +trial for trials
  • Send from an alias: the Bot can also send outgoing mail under the identity of a specific alias
  • Routines watching an alias: a routine watching +receipts only runs on mail sent to that alias; a routine watching the bare address runs on all mail

⚠️ Aliases are labels, not locks

Anyone can send mail to any of your aliases. For routines that should "act only for certain senders," keep thesender filter (Step 4)—don't count on aliases to block strangers.

What you should see: send a test email to an alias, and you can see it later when you ask the Bot "what arrived in the inbox today".

  • You have used a +alias for at least one service (or you know this trick and are keeping it for later)

Step 4: Receiving: let new mail trigger a routine ​

Why: this is the most easily misunderstood point—new mail does not start a chat on its own, nor does it wake the Bot. If you want it to act on mail, you must set up a routine that watches mail.

Key setup points (in the creation flow of 3.3 Routines, choose an email trigger):

  • Trigger scope, pick one of three: mail from anyone / specific addresses / the entire domain (e.g., *@example.com)
  • No filtering by subject—want "trigger only when the subject mentions an invoice"? You can only filter by sender and then let the Bot read the content and judge for itself
  • By default, it only triggers for senders thatpass standard email authentication checks; mail that fails spam/virus scanning is kept (but without the body and attachments) andnever triggers a routine

Two ways to check incoming mail:

  • Ask the Bot anytime: What arrived in your inbox today? (What arrived in your inbox today?)
  • Mail that arrived within the last 1 minute may not yet appear in search results; wait a bit and ask again

What you should see: after setting up a routine, send a test email to the address and the routine runs on its schedule. A new routine does not execute immediately; if you can't wait, use the Test button to trigger it once (see 3.3 Routines).

  • You have set up a routine that watches mail (or have explicitly decided to only ask the Bot manually)

Step 5: Sending: approval, drafts, and sending limits ​

Why: when the Bot sends mail from this address, there are two gates—Auto Review and drafts; there is also a separate set of sending limits for outbound mail, so know them before sending.

Two gates:

  • Emails named in the chat ("send this weekly report to xx"): sent immediately if Auto Review passes; if you are needed, an approval card appears first
  • Emails sent by routines, and anything not explicitly requested by you on the spot: alwayssaved as a draft, waiting for you to press Send—there is no unattended-sending option
  • Forwarded mail, or mail with attachments Auto Review cannot fully read:always requires your confirmation

Sending limits (official wording):

ItemLimit
Recipients≤50 per email (To + Cc + Bcc combined)
Attachments≤10; each ≤10 MB; total ≤25 MB; executable files cannot be attached
newsletter / first contactOne email per recipient, must include a one-click unsubscribe link
Unsubscribe / marked as spam / bouncedThe Bot immediately stops sending to that address and tells you who was skipped
Number of new contactsAlso has a cap (the official docs don't publish the exact number, to protect addresses from being flagged as spam sources)

💡 Also connected to Gmail or Outlook?

When you ask the Bot to send an email, if both accounts can handle it, it will ask which account to send from.

You should see: Have the Bot draft an email; you see the draft first, and only after you press Send does it actually go out.

  • Know that each email allows ≤50 recipients, how attachments are counted, and that executable files cannot be attached

Step 6: Claim failed or can't use it? Check against the official error table ​

Why: The official docs provide a lookup table for errors in the claiming and send/receive steps; matching the exact error text is the fastest approach.

What you seeWhat to do
Agent email is not enabled for this account.Your account doesn't have the agent email feature yet
Your team admin has turned off Grok Bot agent email, so this account cannot claim or use an agent email address.Ask your team admin to enable Agent Email
That address is taken, and addresses are never reissued, so retrying it cannot succeed. Choose a different name.Pick a different name—taken addresses are never reissued, so retrying won't help
A hint about allowed characters, length, or reserved wordsRename following the naming rules in Step 1
You can have one agent email address.You already have an address; ask the Bot what it is, or open the Email app to check
Couldn't create your email address. Try again. (mobile)Check the naming rules, or retry on desktop—the desktop client shows the exact reason
Too many email addresses checked in the last minute.Wait a minute and try again

You should see: The exact error text can be found in the table above; follow the "What to do" column to resolve it (except "feature not enabled," which requires waiting).

  • Able to handle errors by matching the exact text against the table above

Checkpoints ✅ ​

  • Claimed 你的名字@mail.grokbot.com and copied the address
  • Can state: one address, permanently non-renameable/non-deletable, never reissued
  • Know that new emails don't automatically wake the Bot—to trigger actions, set up a routine (filterable by sender/domain, not by subject)
  • Know the sending limits: ≤50 recipients per email, attachments ≤10 with each ≤10 MB and 25 MB total, and executable files cannot be attached
  • Know that emails sent by routines are always saved as drafts awaiting Send—there is no unattended sending

Pitfall warnings ​

❌ Email arrived, but the Bot did nothing ​

Symptom: You sent a test email to the Bot's address, and there was no reaction in the chat.

Cause: New emails don't start a chat or wake the Bot by themselves—this is by official design. There is no inbox interface and no new-mail notification.

Correct approach: To see what arrived, ask the Bot (What arrived in your inbox today?); for automatic actions, set up a routine that watches email (Step 4). Emails that arrived within the last 1 minute may not appear in search results yet—wait a bit and ask again.

❌ Want to filter a routine by "email subject" but can't find the option ​

Symptom: You want "trigger only when the subject contains 'invoice'," but that condition simply doesn't exist in the settings.

Cause: The official docs are explicit—routines cannot filter by subject; they can only filter by sender (anyone / a specific address / an entire domain).

Correct approach: Filter by sender, then put the judgment into the routine's instructions, e.g., "Read the email content and ignore it if it's unrelated to invoices." Also, by default routines only trigger for senders that pass standard email authentication checks, so spoofed emails won't trigger your routine—which is actually a good thing.

❌ Used +alias as a permission control, and it turned out anyone could send ​

Symptom: You only shared +receipts with the invoice service, yet anyone sending to this alias gets into the inbox.

Cause: An alias is a label, not a lock—anyone can send to any alias.

Correct approach: For routines that should "act only for certain senders," keep the sender filter; use aliases only to distinguish sources, not as permissions.

❌ Routine "didn't send the email" on schedule—it was actually waiting for the draft ​

Symptom: You set up "send the weekly summary to the team every Friday," but at the scheduled time nothing went out.

Cause: Emails sent by routines are always saved as drafts waiting for you to press Send—there is no unattended sending option. This isn't a malfunction; it's an official security design.

Correct approach: When the time comes, find the draft in the chat, review it, and send. If you really want to send a newsletter, see C3 Email Digest for the full workflow (including the one-email-per-recipient + one-click unsubscribe requirements).

Advanced tips (optional) ​

Forwarding emails requires 0.75.2+. The Bot can forward received emails in their original format (preserving images and attachments), which requires Grok Bot 0.75.2 or later — the current stable version 1.2.3 (verified on 2026-11-20) already meets this. Forwarded emails, or emails with attachments that Auto Review cannot fully read, always require your confirmation.

Attachment limits for incoming mail. Each incoming email allows at most 10 attachments, each ≤10 MB, totaling ≤25 MB; attachments that exceed the limits areskipped (the email itself still arrives).

Deleting your account = deleting all emails. If you delete your Grok Bot account, all emails and attachments are deleted and the address is permanently reclaimed — but it still will never be reassigned to anyone else.

Behavior of the team toggle. Cursor teams have agent email disabled by default; members can only claim an address after an admin enables Agent Email. If the admin later turns it off: the Bot loses its email tools and email routines stop running, but emails sent to existing addressesare still received and saved, and members keep their addresses.

Lesson Recap ​

✅ Grok Bot mailbox = a dedicated address claimed at mail.grokbot.com, belonging to your account and shared by all Bots; it is not a connection to your existing Gmail — that was the plugin from the previous lesson.

✅ Three ways to claim: tell the Bot Get yourself an email address. (recommended) / Connect apps → Email → Choose a name → Create address / on mobile, Settings → Connect apps → Email; the claim only takes effect after you approve the approval card.

✅ Naming: lowercase letters/digits/./-/_, alphanumeric at both ends, ≤64 characters; reserved words (support, admin, billing, security, help, info, team, cursor, grok, xai) are unavailable. An address can never be renamed and is never reassigned.

✅ Receiving: new emails do not automatically wake the Bot; actions rely on routines (filtering by sender/domain, not by subject); spam/virus emails never trigger routines; there is no inbox interface — to read mail, just ask the Bot.

✅ Sending: emails you explicitly request in chat go out once they pass Auto Review; routine emails are always saved as drafts awaiting Send; forwards always require confirmation. Limits: ≤50 recipients per email, ≤10 attachments each ≤10 MB totaling 25 MB, no executable files; newsletters go one per recipient with one-click unsubscribe; unsubscribes/spam marks/bounces stop sending immediately.

Quick reference of key rules:

RuleValue / How it works
Number of addressesOne; cannot be renamed, cannot be deleted, never reassigned
Naming characterslowercase letters, digits, ., -, _; alphanumeric at both ends; ≤64 characters
Reserved wordssupport / admin / billing / security / help / info / team / cursor / grok / xai
+Aliases名字+标签@ land in the same inbox; they are labels, not locks; filtering is by sender
Receiving triggersA routine must be set; anyone / a specific address / an entire domain; not by subject
Sending (requested in chat)Sent once Auto Review approves; an approval card appears when you are needed
Sending (routine / forward)Always saved as draft / always requires confirmation; no unattended sending
Recipients per email≤50 (To + Cc + Bcc combined)
Attachments (both directions)≤10 items, each ≤10 MB, totaling ≤25 MB; executable files cannot be attached when sending
Newsletter / first contactOne per recipient + one-click unsubscribe; unsubscribes/spam/bounces stop sending immediately

Next Lesson Preview ​

Your mailbox is claimed, and the Daily Use section is nearly done. Next lesson: 2.7 Settings, shortcuts, and notifications.

You will learn:

  • A tour of the five settings panels: General / Computer / Vault / Usage & Billing / Updates
  • A complete shortcut cheat sheet (Cmd/Ctrl+K search panel, etc.)
  • How to forward notifications from desktop to mobile (about 3 minutes)
  • Switching the interface language — including Simplified/Traditional Chinese

Related Tutorials ​

gaodong.aiAboutPrivacyContact

Independent tutorials, not affiliated with any product mentioned. Product names and trademarks belong to their owners. Check official pages for prices and policies.