zapmail-domain-setup-public

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

Updated May 28, 2025
One-click install
npx skills add https://github.com/meloShaya/insteltech --skill zapmail-domain-setup-public-meloshaya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zapmail-domain-setup-public
Source: https://github.com/meloShaya/insteltech/tree/main/crm/library/skills/zapmail-domain-setup-public
Command: npx skills add https://github.com/meloShaya/insteltech --skill zapmail-domain-setup-public-meloshaya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv.

What problem does it solve? Setting up cold email infrastructure manually—finding available domains, registering them, configuring nameservers, and provisioning inboxes—is slow, error-prone, and full of API quirks. This Skill provides a complete end-to-end workflow that handles every step with the correct batch sizes, rate limits, and wait times. ## Core Features & Use Cases - Domain Generation & Availability Checking: Generates short brand-based domain candidates using prefix/suffix tiers and checks availability in batches of 100 via the Dynadot search API. - Automated Purchase & DNS Configuration: Registers domains on Dynadot and switches nameservers to Zapmail's DNS, including the fix for Dynadot's comma-encoding bug in batch requests. - Inbox Provisioning & Platform Export: Creates mailboxes on Zapmail, polls for assignable status, and exports ACTIVE inboxes to sending platforms like Smartlead, Instantly, and Lemlist. - Use Case: A growth team needs 30 sending domains with 2 inboxes each for a new cold outreach campaign. This Skill walks through generating candidates, buying them, connecting to Zapmail, waiting through provisioning, and exporting to Smartlead—flagging the 4-6 hour inbox wait and 2-week warmup requirement. ## Quick Start Ask the AI to set up cold email domains end-to-end for your brand using your Dynadot and Zapmail API keys, starting with generating available domain candidates.

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, then create inboxes. The full process includes a 15-20 minute DNS wait and 4-6 hours of inbox provisioning.

How do I export Zapmail inboxes to Smartlead or Instantly?

Use the Zapmail exports API at /api/v2/exports/mailboxes with the target app name such as SMARTLEAD or INSTANTLY. Always filter by status ACTIVE, since exporting inboxes still in progress fails silently, and link your platform account first via the third-party accounts endpoint.

Why does the Dynadot batch nameserver request fail?

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

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

If any single mailbox in a batch already exists, the entire batch request fails with a 400 error. Retry the failed domains one at a time to isolate the conflicting mailbox and complete the rest.

How long does Zapmail inbox provisioning take?

Zapmail returns 200 immediately after mailbox creation, but inboxes remain in In Progress status for 4-6 hours. Do not export until inboxes show ACTIVE status, and plan a 2-week warmup period before sending real campaigns.

What TLDs should I avoid for cold email domains?

Avoid .info, .xyz, .click, .top, .buzz, and .loan because recipients pattern-match these TLDs as spam, hurting deliverability. Prefer .com as the primary choice and .co as a secondary option.