zapmail-domain-setup-public

Automates cold email domain purchase, DNS setup, and inbox provisioning via Dynadot and Zapmail APIs.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/Pinkycherry/newbusinessideas3 --skill zapmail-domain-setup-public-pinkycherry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zapmail-domain-setup-public
Source: https://github.com/Pinkycherry/newbusinessideas3/tree/main/.claude/skills/zapmail-domain-setup-public
Command: npx skills add https://github.com/Pinkycherry/newbusinessideas3 --skill zapmail-domain-setup-public-pinkycherry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv.

What problem does it solve? Setting up cold email infrastructure manually—buying domains, switching nameservers, provisioning inboxes, and exporting to sending platforms—is slow, error-prone, and full of timing pitfalls like DNS propagation delays and multi-hour inbox provisioning waits. ## Core Features & Use Cases - Domain Generation & Availability Checking: Generates short brand-based domain candidates from prefix/suffix lists and batch-checks availability and pricing through the Dynadot search API. - End-to-End Provisioning Workflow: Purchases domains on Dynadot, switches nameservers to Zapmail, connects domains, creates inboxes, and exports them to sending platforms like Smartlead or Instantly. - Timing & Rate-Limit Guidance: Encodes real-world wait times (15-20 min DNS propagation, 4-6 hour inbox provisioning) and batch limits with retry strategies for known API failure modes. - Use Case: A growth team needs 30 sending domains with 2 inboxes each for a new cold outreach campaign; this workflow runs the full pipeline unattended and exports active inboxes directly to Smartlead. ## Quick Start Set your DYNADOT_API_KEY and ZAPMAIL_API_KEY environment variables, then ask the assistant to set up 30 cold email domains for your brand end-to-end and export the inboxes to Smartlead.

Frequently Asked Questions about zapmail-domain-setup-public

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up cold email domains with Zapmail and Dynadot?

Generate short brand-based domain candidates, check availability via the Dynadot search API, register them, switch nameservers to Zapmail's DNS, connect the domains on Zapmail, create inboxes, and export them to your sending platform after provisioning completes.

How long does Zapmail inbox provisioning take?

Zapmail returns 200 immediately after inbox creation, but inboxes show In Progress status for 4-6 hours. Do not export until inboxes reach ACTIVE status, since exporting In Progress mailboxes fails silently.

Why does the Dynadot batch nameserver request fail?

Python's urllib.parse.urlencode encodes commas as %2C, which breaks the comma-separated domain list in the set_ns batch request. Pass safe=',' to urlencode so commas remain unencoded.

Which TLDs should I use for cold email domains?

Use .com as the primary choice for best inbox trust, with .co as a secondary option. Avoid .info, .xyz, .click, .top, .buzz, and .loan because recipients pattern-match on these TLDs and deliverability suffers.

Why did my Zapmail batch mailbox creation return a 400 error?

If any single mailbox in a batch already exists, the entire batch request fails with a 400 error. Handle this by retrying the failed domains one at a time to isolate the conflicting mailbox.