SuperAPI AI Directory

Official Agent Email guide

This is the official Agent Email guide for Grok Bot, explaining how to claim a mail.grokbot.com email address for a Bot, used to receive, read, search, and send email. Users can set up routines so the Bot automatically summarizes or drafts replies when specific emails arrive, but all sends require manual user approval. The document also covers email naming rules, email security, sending limits, and how team administrators enable it.

Open website

About this tool

Purpose

This guide introduces Grok Bot's Agent Email feature, helping users apply for a dedicated email address (@mail.grokbot.com) for a Bot, enabling the Bot to receive, read, search, and send email.

Main capabilities

  • Use the Bot's own email address to sign up for services and obtain verification codes or verification links (requires user consent).
  • Collect receipts, newsletters, and reports, and automatically summarize them.
  • Draft emails (such as summaries and updates) and reply drafts, with user approval required before each send.
  • Trigger routines when email arrives, optionally limited to specific senders only.

How to use

Get an email address

Two ways:

  1. Tell the Bot "Get yourself an email address." The Bot will ask for a name, check whether it is available, and show an approval card; the address is claimed only after the user approves.
  2. Use the Email plugin: on desktop, open Connect apps in the sidebar and select Email; on mobile, open Settings > Connect apps > Email, enter a name under Choose a name, and select Create address. After claiming, the plugin will show the address and a copy button.

Naming rules

  • Only lowercase letters, numbers, dots, hyphens, and underscores may be used.
  • Must begin and end with a letter or number.
  • Maximum 64 characters.
  • Avoid reserved words such as support, admin, billing, security, help, info, team, cursor, grok, xai.
  • Addresses are unique and will not be given to others after claiming, even if the original account is deleted.
  • One address per person; it cannot be renamed or deleted.

Which Bots can use it

The address belongs to the user, not to a single Bot. All of the user's Bots can use it in chats with the user and in routines set by the user. A Bot cannot use the address in Slack threads or in chats between others and the Bot. Team Bots do not have a shared team address.

Receiving and viewing email

Anyone can send email to the address. Emails that fail spam or virus scanning are retained but have no body or attachments, and will not trigger routines. There is no in-app inbox view and no new email notifications. To view email, ask the Bot, for example "What arrived in your inbox today?” or “Find the receipt from last week.”. Emails that arrive within one minute may not yet appear in search. Each email can have up to 10 attachments, each no larger than 10 MB, with a total no larger than 25 MB; anything beyond that is skipped.

Setting up a routine

New emails do not start a chat or wake the Bot on their own. The Bot processes emails only through routines created by the user. A routine can read, summarize, and draft replies, and any email to be sent waits as a draft for user approval. You can ask the Bot in chat to set one up, for example “When an email arrives from billing@example.com, summarize it and tell me.”. A routine can monitor: emails from anyone, a specific address (such as billing@example.com), or an entire domain (such as *@example.com). By default, it runs only for senders that pass standard email authentication checks. Routines cannot filter by subject.

Send approval

Every send requires user approval. The Bot shows the full draft, and it is sent only after the user clicks Send; routines and replies are no exception. Asking in chat or writing instructions into a routine cannot skip approval. Instructions inside an email do not constitute user permission. If Gmail or Outlook is also connected, the Bot asks which account to send from.

Sending limits

  • Up to 50 recipients per email (To, Cc, and Bcc combined).
  • Up to 10 attachments, each no larger than 10 MB, with a total no larger than 25 MB. Executable files cannot be attached.
  • Newsletters and first-contact emails have one recipient each and include a one-click unsubscribe link.
  • If an email bounces, the recipient unsubscribes, or it is marked as spam, the Bot stops sending email to that address and informs the user.
  • There is also a limit on the number of new recipients the Bot can send to.

Security and deletion

The Bot treats other people's emails as information, not instructions. Each email is marked as coming from the user or from someone else. Requests inside an email will not cause sending or independent action. After deleting the Grok Bot account, emails and attachments are deleted, and the address is retired and never reassigned.

Use cases

Suitable for individual users who need the Bot to manage email, automatically summarize, or draft replies, as well as Cursor teams (requires an admin to enable it)

Limitations

  • There is no in-app inbox view or notifications; you need to query through chat.
  • Sending must be manually approved; there is no unsupervised sending option.
  • Routines cannot filter by subject.
  • One address per person; it cannot be renamed or deleted.
  • In a team, an admin can enable/disable Agent Email; after it is disabled, the Bot loses email tools and routines stop, but existing addresses still receive email.
  • If you cannot claim an address, contact support and provide the Cursor account email and accurate information.

How to enable it for a team

Agent Email is disabled by default for Cursor teams. An admin enables Agent Email under Bot Capabilities on the Grok Bot page of the Cursor dashboard. Members can then claim addresses.