Published September 2, 2026 · Transcript-edited v1
Your Grok bots need email. But how do you set that up?
I did not want Grok Bot inside my Gmail. My personal inbox is already a mess. I also did not want to create a separate Google account for every bot. That is stupid. Don't do that.
So I built my version with Grok Bot, Cloudflare Workers, and a domain I own. The important part is that the mail system survives outside of Grok Bot.
If I switch to Hermes or whatever tool is cool three months from now, the work is not stuck inside the old bot.
Think interoffice mail, not individual inboxes
If you're a millennial like me, you probably worked somewhere with interoffice mail envelopes. You put a signed document inside, wrote "from Aaron to Bob" on the outside, and dropped it in the mail room. Someone sorted it to the right office or branch.
That became the model for this system.
A UPS driver does not need a different street address for every person on every floor. The packages go to one mail room. From there, someone sorts each one into an employee mailbox slot.
Giving every Grok bot its own full email account is like giving every cubicle its own street address. Totally unnecessary.
How my mail room works
I use Cloudflare to create receive-only addresses on a domain I own. My bots have addresses, but they cannot send email. I do not have a separate inbox to manage for each one.
The mail arrives at the mail room. From there, it can be sorted into the right slot.
In my demo, a workshop inquiry belongs in the pipeline slot. A message from the pressure test I ran when I built the system goes to test. The task to make this video goes to creative.
Those are mail slots, not Google accounts. Underneath them is Cloudflare storage on my domain.
The Cursor clerk is optional
I use a Cursor automation that runs in the cloud as the clerk. It documents each receipt in GitHub and sorts the message into the right lane.
You do not have to do that.
Cursor is not the mail room. It is the clerk I can replace. I use it because the GitHub record makes it easier to connect Hermes or whatever tool comes next to the same mail slots.
Why I used Cloudflare
I have moved my sites to Cloudflare. I use it for web hosting and I even buy domains there. It is kind of amazing what you can do for zero to five bucks a month.
My version uses the Cloudflare Workers Paid plan, which starts at $5 per month. That is the plan I use for this setup.
The part I actually care about
If I cancel Grok Bot or get rate limited, I do not want serious work locked inside it while I wait for it to come back.
With this setup, the interoffice mail envelopes are sitting in mail slots I own. I can connect Hermes or another agent tool and pick up where I left off.
That is why the domain matters. The current bot can change. The mail system stays.
Set up your own
If you're thinking, "Cool story, Aaron, but how the heck am I gonna set this up?" I turned the setup into a public skill.
Use the "Copy instructions to my agent" button on this page, or read the public GitHub repository. Read the prompt before you paste it into your tool. It will walk you through the setup one question at a time.
The most important thing is that the system survives any platform or coding agent. If Grok Bot is not the cool thing three months from now, the work you built around it is still portable.