Cloudflare + Gmail: The Clean Operator's Guide to Inbound & Outbound Support
You want an operator's checklist, not an architecture lecture. Here is how to wire professional domain email into your personal inbox without paying for redundant enterprise subscriptions.
When you launch a new enterprise application or digital platform, the amateur move is paying $6 per user per month for three separate Google Workspace inboxes just so you can receive mail at support@ and billing@. The professional move is leveraging Cloudflare's lightning-fast Email Routing to ingest, filter, and forward inbound mail directly to your primary Gmail account — while setting up custom sending identities so you can reply as whoever you need to be.
Below is the exact, zero-fluff operator's playbook we use across Whyire and our client deployments. Follow it step by step.
1. Cloudflare — Turn on Email Routing
Log into your Cloudflare Dashboard, select your domain, and navigate to Email → Email Routing. Click Get started and add your destination Gmail address (e.g., yourgmail@gmail.com). Accept the verification email Cloudflare dispatches to your inbox.
2. Create support@ and billing@ Routing Rules
Under Routing rules, create custom addresses:
support@yourdomain.com→ forwards toyourgmail@gmail.combilling@yourdomain.com→ forwards toyourgmail@gmail.com
3. Gmail — Send FROM Custom Aliases
In Gmail, go to ⚙️ Settings → See all settings → Accounts and Import → Send mail as. Click Add another email address. Enter your custom support or billing name and address. Gmail will send a confirmation code through Cloudflare's routing rule back to your inbox. Confirm it, and you are ready to compose and reply using your domain identity.
4. Inbox Triage: Automatic Labeling & Smart Replies
Set up Gmail filters for incoming messages sent to support@yourdomain.com and billing@yourdomain.com to apply distinct labels (Support and Billing). Under Send mail as, configure Gmail to automatically reply from the same address to which the incoming message was sent.
5. Website Contact Forms
Never hardcode Gmail app passwords or SMTP credentials in your frontend code or serverless worker. Configure your backend Worker (such as Whyire's contact worker using Resend or direct mail bindings) to post submissions straight to support@yourdomain.com or billing@yourdomain.com. Cloudflare handles the transit securely, leaving your credentials pristine and unexposed.