When should you use it?
- Your bot needs to email customers
- You want to read the mailbox yourself
- Signups or login codes should trigger the bot
Not for: Personal notes that never leave the bot; Teams without anyone who can manage DNS
What do you need, and what do you get?
You need
- A domain you control
- A mailbox provider with an MCP connector and signed webhooks
- The bot routine to start on new mail
You get
- Mailbox on your domain the bot can read and send from
- Signed webhook that triggers the bot
- Notes on known limits
How does it work, step by step?
- Check the built-in limitsRead your platform's notes on bot email so you know what it cannot do before you rely on it.
- Set up the mailboxCreate a mailbox on your domain with a provider that exposes it through MCP.
- Connect itAdd the mailbox as a custom connector and confirm the bot can list and send mail.
- Sign the webhookUse the routine's webhook secret to sign requests in the standard webhooks format; plain bearer tokens were rejected.
- Test the wake-upSend a test message and confirm the routine starts and the reply looks right before customers see it.
The prompt
Our own prompt, inspired by u/Jcoulaud on r/GrokBot and written to work in Grok Bot. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Set up mail handling for me. Mailbox: {mailbox_address} on my domain, connected as a custom connector. When the webhook fires with a new message, read it, classify it as {categories}, and draft a reply for anything from a customer. Do not send customer replies until I approve them. Log each message and action in {log_file}.
Inspired by u/Jcoulaud on r/GrokBot: grokbot email after a day: the limits nobody mentions + how i put mine on my own domain. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Unsigned webhook requests fail with a 400; sign them.
- Plus-address aliases may vanish without a bounce; test each address.
- Customer mail should still pass a human check while you test.
Our take
The value here is a field report written after actually using the feature, plus one gotcha that would otherwise eat an afternoon. u/Jcoulaud's limit list makes the decision easy: the built-in address handles account signups and one-time codes well, but customers expect mail from your domain and you need to see the thread yourself. Owning the mailbox solves both. The webhook detail is the part to bookmark. Grok automations reject a plain bearer token and accept only requests signed with the whsec secret in the Standard Webhooks format, so a test that returns a 400 is usually a signing problem, not a routing one. Note the poster discloses building a mail product, so treat the tool choice as one option among several mailbox providers. Whatever you use, start with the bot drafting replies into the mailbox for you to send, then allow it to send routine confirmations on its own once a few weeks of replies have been uneventful. Keep complaints, refunds and anything legal on the human side permanently.
Where the time goes back: Mail-triggered work starts on its own, and you can open the same inbox the bot uses.
FAQ
Who is the poster?
Can I rename the built-in address later?
Source and credit
Inspired by u/Jcoulaud on r/GrokBot. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- grokbot email after a day: the limits nobody mentions + how i put mine on my own domain
- Creator
- u/Jcoulaud on r/GrokBot
- Published on
- Original date
- Oct 10, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.