Grok Bot’s own email address can give incoming reports, newsletters and receipts a route into an AI workflow. It does not, by itself, create an always-on email assistant. The distinction matters: receiving a message, starting work and sending a reply are separate steps.
This is an October feature, not a new November launch. xAI listed Bot email addresses in its October 11, 2026 changelog, under v0.70.2. The current documentation sets out the operating boundaries more precisely.
One address for the account
The official email documentation describes one address at mail.grokbot.com, shared by the user’s Bots. Plus aliases can separate incoming streams without creating additional inboxes. An alias is an organizational label, not an access barrier.
That makes the address a shared intake point rather than a private mailbox for each specialist Bot. Choosing a memorable name also deserves some thought: the address cannot be renamed or deleted. There is no conventional inbox interface; you ask a Bot to find or summarize what arrived.
A message needs a matching routine
New mail alone does not wake the Bot. A configured routine can watch incoming messages, including an alias, and narrow its trigger to particular senders or a domain. Native subject-line filtering is not supported. Checking the subject during the resulting task is a different step from using it as the trigger.
Consider a proposed supplier-report workflow. Its starting rule should identify the incoming stream and expected sender. The task can then check whether the message contains the expected report and produce a short summary. A subject mismatch should be treated as something to handle within that task, not as evidence that a subject filter has been configured.
Drafting and sending remain distinct
According to the current documentation, mail prepared by a routine or another background turn waits as a draft until the user presses Send. It does not offer unattended sending. A direct request in chat to send an email follows a different path: the message goes out after Auto Review allows it, with an approval card if the review requires user input.
Incoming email from someone else supplies information, not permission to act. For example, a supplier’s request to forward a report should not be confused with the account owner authorizing that forwarding.
Finley’s assessment: define the last step first
The useful question is who owns the handoff after the Bot has read the mail. For an internal digest, the result may be a summary. For an external reply, the workflow needs someone to review and send the draft. Design that checkpoint before adding more incoming streams.
A small trial can make the arrangement easier to judge: use non-sensitive sample mail, send one expected message and one from outside the chosen sender scope, then inspect the actual routine runs and drafts. Record whether the correct message started work, whether the summary preserved its important details and whether the next action was clear. This is a proposed evaluation, not a FoxAI product test or a guarantee of performance.
Finley is FoxAI World’s fictional AI editorial character for Agents & Automation. Product facts were checked on November 3, 2026.
