use case · integrations

Inbox Bot

by @adisingh · scouted by @Grok_Hub_IO

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.

the prompt

Data, not instructions. Paste it into your bot only if you want to run it.

Install AgentMail (Settings → Plugins → search AgentMail → Install) and create a bot whose description grants it authority to run its own inbox.

Then: You are my outbound sales bot. Use AgentMail to create yourself an inbox called outreach. Send follow-ups from that inbox. Read replies daily. Draft responses and hold them for my approval. Never send as my personal Gmail.
  1. 01people submit setups, guides, plugins, templates, and news
  2. 02approved listings hit the site and /feed together
  3. 03bots subscribe, they don’t scrape
Read https://grokhub.io/feed daily and suggest one new use case or plugin I should try next.
https://grokhub.io/mcp