ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified productivity Safety 4/5

domain-email-forwarding

Set up email forwarding for custom domains to receive verification codes, password resets, and other emails at a domain you own but don't actively use for email. Covers GoDaddy, Namecheap, Cloudflare Email Routing, and ImprovMX. Use when recovering accounts linked to inactive domain emails, setting up catch-all forwarding, or routing domain email to Gmail/Outlook without paying for email hosting.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/brandonwadepackard-cell/domain-email-forwarding
Or

What This Skill Does

The domain-email-forwarding skill allows users to configure professional email routing for custom domains directly through their OpenClaw AI agent. It acts as an orchestrator for managing DNS records and registrar settings for popular platforms like GoDaddy, Cloudflare, and Namecheap. By automating the creation of forwarding rules, this skill ensures that incoming mail—such as account verification codes, password resets, or general inquiries—is successfully routed to a primary, active inbox like Gmail or Outlook without the need to pay for full email hosting services. It bridges the gap between owning a domain and having a functional communication channel for it.

Installation

You can install this skill by running the following command in your terminal or via the OpenClaw agent console: clawhub install openclaw/skills/skills/brandonwadepackard-cell/domain-email-forwarding

Use Cases

  • Account Recovery: You need to receive a password reset link for a legacy service registered to an email address on a domain you own but currently don't host email for.
  • Cost-Effective Professionalism: You want to use a professional domain address (e.g., [email protected]) but don't want to pay monthly per-user fees for a dedicated email provider.
  • Catch-All Routing: You want to capture all traffic sent to any address on your domain (e.g., info@, support@, admin@) and consolidate it into a single monitoring inbox to ensure you never miss a lead.
  • Temporary Verification: You need to pass an email verification check during a signup process and want to use your custom domain for a branded experience.

Example Prompts

  1. "OpenClaw, help me set up email forwarding for my domain on Cloudflare to send all mail to my personal gmail address."
  2. "I need to receive a verification code for my GoDaddy-managed domain. Please guide me through setting up the forwarding rules so it lands in my inbox."
  3. "Configure a catch-all email forward for my domain on Namecheap to my main inbox, ensuring I don't miss any incoming verification emails."

Tips & Limitations

  • DNS Propagation: While forwarding setup is fast, remember that changing DNS settings or MX records can occasionally take a few minutes to propagate across global DNS servers. If it doesn't work immediately, wait 5-10 minutes.
  • Verification Steps: Always check your destination inbox for a confirmation email. Services like Cloudflare and ImprovMX will not start forwarding traffic until you click the confirmation link sent to your destination address.
  • Cloudflare Requirement: The Cloudflare integration requires that your domain's nameservers are pointed to Cloudflare. If your DNS is hosted elsewhere, consider using ImprovMX as a registrar-agnostic alternative.
  • GoDaddy Toggle: If using GoDaddy, ensure the 'Forwarding Status' is toggled to ON; merely setting a forward destination is often insufficient in their admin panel.

Metadata

Stars4190
Views0
Updated2026-04-18
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-brandonwadepackard-cell-domain-email-forwarding": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#email#dns#automation#registrar#domains
Safety Score: 4/5

Flags: external-api

Related Skills

platform-api-connector

Connect to social media and content platform APIs by navigating developer portals, creating apps, obtaining OAuth tokens, and storing credentials. Covers Facebook Graph API, Instagram Business API, YouTube Data API, Twitter/X API v2, and TikTok Content Posting API. Use when setting up API access for any social platform, refreshing expired OAuth tokens, or debugging authentication flows.

brandonwadepackard-cell 4190

multi-agent-parallel-build

Orchestrate multiple coding agents (Claude Code, Codex, etc.) in parallel waves to build UI pages, API endpoints, or features simultaneously. Use when building dashboards with 5+ pages, microservices, or any project where independent components can be built concurrently. Covers wave planning, shared shell/component libraries, agent spawning, merge conflict avoidance, and post-wave integration fixes.

brandonwadepackard-cell 1865

supabase-dashboard-builder

Build admin dashboards and command centers backed by Supabase REST API with D3.js force graphs, Chart.js visualizations, and vanilla JS. Use when creating data exploration UIs, admin panels, mission control dashboards, or any visualization that reads from Supabase tables. No React/Vue required — pure HTML + JS + CSS with a shared dark-theme shell.

brandonwadepackard-cell 1865

hume-evi-langgraph

Integrate Hume EVI voice AI with LangGraph using interrupt/resume patterns. Use when building voice-based AI agents that need Twilio call handling, Hume EVI persona creation, transcript fetching with emotion extraction, and LangGraph state management across the call lifecycle. Covers dynamic Hume config creation, TwiML generation, webhook handling, chat_group event fetching, and emotion timeline extraction.

brandonwadepackard-cell 1865

supabase-checkpointer

Durable LangGraph checkpointing via Supabase REST API (PostgREST) — no direct Postgres connection needed. Use when deploying LangGraph graphs to ephemeral platforms (Railway, Fly, Cloud Run) where in-memory state is lost on redeploy, and you need interrupt/resume to survive process death. Works with any Supabase project using the existing service role key.

brandonwadepackard-cell 1865