Let the bot email customers from your own domain
As described in the source, the poster located Grok Bot’s assembled-in mail too limited for customer-facing use, so they stood up a mailbox on their own domain and connected it to Grok as a custom MCP connector. Because incoming mail does not wake the bot automatically, they also added a webhook that starts a Grok automation on each new message; they note the webhook had to use Grok’s signed whsec_ secret format, not a bearer token. It gave them a customer-facing address on their own domain and an inbox they could open themselves, while still letting the bot react to mail as it arrived.
- Agent or tool
- Grok Bot
- Topic
- Email & Inbox
- Reported on
- Added
- 2026-10-15
Why it matters
Email is where a lot of admin quietly piles up. An agent that can read, sort, draft and follow up turns an inbox from a to-do list into something closer to a summary. It is one of 106 sightings filed under Email & Inbox on Agent Sightings (number 106 by interest), and one of 85 involving Grok Bot.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Grok Bot or any similar agent and adjust the details to your situation.
Go through my mail for this goal: let the bot email customers from your own domain. Propose labels, drafts, and unsubscribes as a checklist; change nothing until I approve.
Tip: Start with read-only access or 'draft, don't send', and check a few drafts before trusting it to send anything.
Source
Read the original first-hand account on Reddit: https://www.reddit.com/r/GrokBot/comments/1x2iafb/grokbot_email_after_a_day_the…. Our summary is a paraphrase; details are in the source.