use case · integrations
Inbox Bot
Gives each bot its own email so they do not share your inbox and codes.
Grok Bot ships with a Gmail plugin, but it points at your inbox. So your outreach bot, support bot, and ops bot all write as you from one address, and giving them your inbox means letting them read sensitive threads, password resets, and verification codes. One malformed email can prompt-inject a bot into leaking information or taking the wrong action.
A separate inbox contains that: forward it only what matters, CC it on relevant threads, and let it create its own accounts. Install is Settings → Plugins → search AgentMail → Install, approve OAuth (it says Cursor wants to access AgentMail because Bot uses Cursor's plugin plumbing), 24 tools appear.
Four things the built-in Gmail plugin can't do: sign the bot up for its own accounts (2FA lands in its inbox), run an outreach loop with its own sending reputation, own a support inbox that escalates to a human, and sit in a group thread as a colleague.