Yesterday, Elon Musk himself validated the problem we've been working on for years.
Why give Grok Bot its own email address?
Grok Bot ships with a Gmail plugin, but that plugin points at your inbox. Your outreach bot, your support bot, and your ops bot all end up writing as you, from the same address, with no way to separate them. Giving Grok Bot access to your personal inbox means letting it read sensitive conversations, access password resets and verification codes, and send emails as you. One malicious or malformed email could also prompt-inject the bot into exposing information or taking the wrong action.
A separate inbox keeps that access contained. You can forward Grok only what matters, CC it on relevant threads, and let it create its own accounts on GitHub, Reddit, and other services. @agentmail is a startup backed by Y Combinator, and General Catalyst building a purpose-built API that lets your Grok have its own inbox and identity on the internet. and it has a native Grok Bot plugin which takes 2 mins to setup!
How do I install AgentMail on Grok Bot?
You need a Grok Bot account (Cursor Ultra, SuperGrok Heavy, or Cursor Premium Teams) and an AgentMail account. AgentMail's free tier covers everything below.
1. Open Grok Bot. Go to Settings → Plugins. Search for AgentMail. Click Install.
2. Approve the OAuth prompt. Your browser opens an AgentMail authorization screen. It says "Cursor wants to access AgentMail on behalf of you@yourdomain" because Grok Bot uses Cursor's plugin plumbing. Click Allow. No API key to paste.
3. Check the connector card. 24 tools appear.
4. Create a bot with an email job. In the description, give it authority to run its own inbox. Example: "You are my outbound sales bot. Use AgentMail to create yourself an inbox called outreach. Send follow-ups from that inbox. Read replies daily."
5. Try it. Ask the bot to email you at your real address. The mail lands. Reply from your inbox. Ask the bot to check. It reads your reply in the same thread.
What can my Grok Bot do with its own inbox?
Four things you cannot do with the built-in Gmail plugin.
Sign the bot up for its own accounts. Notion, Stripe, Vercel, anything with a signup form. The 2FA code lands in the bot's inbox. The bot reads it, pastes it, finishes signup. Nothing runs under your Google identity.
Run an outreach loop. The bot sends from its own address, tracks each thread, drafts personalized replies. Your inbox stays clean. Deliverability does not compete with your personal mail.
Own a support inbox. help-desk@yourdomain belongs to the bot. It handles first-line replies, forwards the rest to a human. Same pattern as Zendesk AI at a fraction of the cost.
Put the bot in a group email thread. CC assistant@yourdomain on any thread. The bot reads the history, participates like a colleague, replies inside the thread. Atal Upadhyay wrote about this as the chief of staff move.
What are some example prompts?
Drop any of these into a bot after installing.
Sign up for accounts:
Sign up for a free Notion account using
notion-bot@agentmail.to
. When the verification code arrives, read it and finish signup. Report the account details.
Intelligent outreach with reply handling:
From a new inbox called
outreach
, send this pitch to every row in
leads.csv
. Personalize the greeting with the first_name column. When someone replies, draft a response and hold for my approval.
Auto-triage a founder inbox:
Create an inbox called
founder@
. Every 10 minutes, list unread. Reply to anything you can answer. Forward anything about legal, money, or contracts to me. Label the rest as
later
.
Meeting scheduler:
When someone emails
meet@agentmail.to
, read the thread, check my Google Calendar, and reply with three 30-minute slots that work in their timezone.
@binoyperera. AgentMail. Create inboxes via API. Send and receive Emails with 0 complexity. Free to start.
Read the full article written by the wonderful @PereraBinoy here.
