How to route domain email to different bots with Grok Bot
ManaEngineer describes a custom-domain email setup using Cloudflare's free forwarding addresses. Mail lands in their Grok Bot email and is routed by recipient address so different bots handle support and personal mail without manual sorting.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Help me set up [owned domain] on Cloudflare with free forwarding addresses delivering to [Grok Bot email]. Route incoming mail by its recipient address: [support address] to [support bot] and [personal address] to [personal bot]. Confirm my permitted setup changes before acting and do not assume permission to send replies.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @ManaEngineer
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- ManaEngineer reports routing forwarded domain email by recipient address so different bots handle different work, including support and personal mail, without manual sorting.
- Human involvement
- They own the domain and choose to delegate the setup. The account does not describe setup permissions, human review of messages or approval of outgoing replies.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Have Grok Bot set up their existing domain on Cloudflare.
- Create free forwarding addresses that all deliver to their Grok Bot email.
- Route incoming mail by the recipient address so different bots handle support and personal mail.
ManaEngineer describes using a domain they own to give different bots distinct email responsibilities. They have Grok Bot set the domain up on Cloudflare and create free forwarding addresses, all of which deliver to their Grok Bot email.
The receiving address determines where a message goes next. Rather than manually sorting the incoming mail, they route it by the address it was sent to. Support mail can go to a support bot, while personal mail goes to a different bot. The addresses therefore distinguish the work even though the forwarded messages land in the same Grok Bot email.
The reported outcome is address-based routing between bots without manual sorting. The account does not establish response quality, how replies are approved, or the technical implementation of the routing. It also does not describe the permissions granted during the Cloudflare setup. Those details should not be inferred from the forwarding arrangement.
Who it's for: Domain owners who want separate email addresses to direct support and personal work to different bots.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @ManaEngineer
Frequently asked questions
Where do the forwarding addresses deliver mail?
They all deliver to ManaEngineer's Grok Bot email. The recipient address is then used to route the message to the appropriate bot.
What kinds of mail go to different bots?
The account gives support mail and personal mail as examples of work handled by different bots, without manual sorting.
Does the account describe automatic replies?
It describes forwarding and routing incoming mail, not how replies are written, approved or sent.
More details
About this account
Grok Bot is tasked with the Cloudflare domain and forwarding setup; incoming mail is then routed by recipient address to bots with different responsibilities.
Source: https://x.com/ManaEngineer/status/2112481479158587884 by ManaEngineer (@ManaEngineer), posted 20 Oct 2026 at 10:50 UK, as supplied by the submitter. X's public embed confirms the author, date and opening forwarding description but truncates the routing detail; the complete account used here was supplied by the submitter. Prompt: Suggested, written by Agents In Use, not the author's original prompt. No quantified savings or response outcomes are claimed.
Credit: ManaEngineer (@ManaEngineer) on X
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot · Cloudflare
Email routing · Custom domain · Multi-agent workflows
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.