Guides xAI

Grok Bot Email: Set Up an Inbox and Draft Replies

Set up Grok Bot Agent Email, check received project updates, reconcile changed deadlines, and review an editable reply before sending.

Grok Bot Email: Set Up an Inbox and Draft Replies
Background and context

What is Grok Bot's new email feature?

Agent Email supplies a separate address for your account. All your Bots can use it in your own chats and routines. Connecting Gmail or Outlook gives access to an existing mailbox. This exercise uses the separate address and leaves personal inbox connections unused. For the broader app workflow, see our Grok Bot setup guide.

Your goalRoute to consider
Send selected project updates to an address the Bot can use.Its new email inbox, when your account has access.
Search mail already in your Gmail or Outlook account.The matching connection, with permissions you review.
Send a message from your work identity.An approved connection to that account. Do not assume the new inbox uses your company domain.

An extra inbox does not remove access you granted earlier. Review existing connections and signed-in websites before the test. As the Grok Bot privacy controls explain, Bots on one account share a cloud computer, so creating another Bot does not isolate its files or logins.

Who can use Grok Bot email?

Check Agent Email availability in your selected account. Cursor team admins enable it under Cursor dashboard → Grok Bot → Bot Capabilities → Agent Email. It is off by default for teams. A rollout or team restriction can still block address creation.

General Bot access comes with paid individual Cursor plans and Cursor Teams, or a linked individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription. Self-serve Grok Business seats have a separate Grok sign-in route. Check the current access and billing requirements before paying for this feature.

Use the Grok Bot desktop app for this walkthrough and a sender account you control. Keep the exercise in a one-to-one Bot conversation. Grok's general chat app and a public reply to @grok are different surfaces.

Check Settings → Usage & Billing before starting. The plans and billing documentation says paid Bot access includes weekly usage and that enabled on-demand usage can add charges after that allowance runs out. We have not verified a separate mailbox price.

Where this inbox could help next

TaskA small first version
Project updatesSend approved status notes to Bot and request a summary of changes and open questions.
Newsletters and reportsSend a few approved sources to the new address and ask for a source-linked digest. Review any subscription or forwarding rule yourself.
Vendor repliesCollect replies for one request and draft the next question. Keep quotes, commitments, and sends under review.

These are suggested workflows to test. An inbox does not by itself grant calendar access, approve a purchase, or turn email processing into a reliable routine. Grok Bot's workflow guidance recommends starting with preparation and review.

Common Grok Bot email problems

ProblemWhat to check
Bot cannot claim an address.Confirm the account, rollout, and team setting. Do not treat general Bot access as proof of inbox access.
An email is missing.Check the exact address, sender's Sent folder, bounce messages, and the mailbox results. Pause the summary until coverage is clear.
Bot uses your Gmail address.Stop. Check which mailbox and sending tool it selected. Keep personal-mail access outside this test.
The summary contains an old deadline.Reopen the original and replacement messages. Ask for the evidence behind the chosen date.
A draft includes extra recipients.Remove them and review the final recipient list before any send.
It claims to monitor new mail.Check for an actual enabled trigger or routine and its run history. A chat promise is not proof of a running setup.

Use the official Agent Email troubleshooting table to distinguish a rollout block, disabled team capability, taken name, or account that already has an address.

Build an email workflow you can trust

Before expanding the task, test a missing message, a changed date, an unclear request, and a draft that must remain unsent.

Questions people ask

Is this the same as connecting Gmail to Grok?

Agent Email creates a separate account-level address. A Gmail connection accesses a mailbox you already own. This walkthrough leaves that connection unused.

Can it reply to emails on its own?

Sending needs a user request in chat or an authorized routine. Replying counts as sending. For this walkthrough, keep an Ask first rule and review the complete draft. A received email's instructions do not authorize an action.

Can I use my own domain or create several addresses?

Each account gets one address at @mail.grokbot.com, shared by its Bots in that user's chats and routines. It cannot be renamed or deleted. The documented claim flow does not offer a custom company domain. A Team Bot has no shared team address.

Is it safe to send client emails there?

Check your organization's policy and the provider's terms first. Forwarding can include old thread content and attachments as well as the latest reply. Start with fictional text and disclose only what the task needs.

Grok Bot requires cloud storage. Its security documentation also warns that outside content can try to redirect a Bot. Keep private data and consequential actions out of a first test, and do not treat a separate Bot as an isolated workspace.

Does this guide need another paid resource?

You need an eligible Grok Bot plan and the inbox rollout. The fictional messages and prompts for the walkthrough appear in the steps above.

Resources 1

Start from the exact file used in this guide instead of rebuilding it from scratch.

Unlock with Pro