instantly-prod-checklist

0
0
Source

Execute Instantly production deployment checklist and rollback procedures. Use when deploying Instantly integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "instantly production", "deploy instantly", "instantly go-live", "instantly launch checklist".

Install

mkdir -p .claude/skills/instantly-prod-checklist && curl -L -o skill.zip "https://mcp.directory/api/skills/download/8662" && unzip -o skill.zip -d .claude/skills/instantly-prod-checklist && rm skill.zip

Installs to .claude/skills/instantly-prod-checklist

About this skill

Instantly Production Checklist

Overview

Pre-flight checklist for launching Instantly cold email campaigns in production. Covers account warmup verification, deliverability testing, lead list hygiene, campaign configuration, webhook setup, and monitoring. Skip any step that doesn't apply to your use case.

Prerequisites

  • Completed instantly-install-auth setup
  • Email accounts connected and warmed up (minimum 14 days recommended)
  • Lead list prepared with verified emails

Production Launch Checklist

Phase 1: Account Health (2-4 weeks before launch)

import { instantly } from "./src/instantly";

async function phase1AccountHealth() {
  console.log("=== Phase 1: Account Health ===\n");

  // 1. Verify all accounts have healthy SMTP/IMAP
  const accounts = await instantly<Array<{ email: string }>>(
    "/accounts?limit=100"
  );
  const vitals = await instantly("/accounts/test/vitals", {
    method: "POST",
    body: JSON.stringify({ accounts: accounts.map((a) => a.email) }),
  }) as Array<{ email: string; smtp_status: string; imap_status: string }>;

  const broken = vitals.filter((v) => v.smtp_status !== "ok" || v.imap_status !== "ok");
  console.log(`Accounts: ${accounts.length} total, ${broken.length} broken`);
  if (broken.length > 0) {
    console.log("FIX THESE FIRST:");
    broken.forEach((v) => console.log(`  ${v.email}: SMTP=${v.smtp_status} IMAP=${v.imap_status}`));
    return false;
  }

  // 2. Verify warmup is active and healthy
  const warmup = await instantly("/accounts/warmup-analytics", {
    method: "POST",
    body: JSON.stringify({ emails: accounts.map((a) => a.email) }),
  }) as Array<{ email: string; warmup_emails_landed_inbox: number; warmup_emails_sent: number }>;

  for (const w of warmup) {
    const inboxRate = (w.warmup_emails_landed_inbox / (w.warmup_emails_sent || 1)) * 100;
    const healthy = inboxRate >= 80;
    console.log(`  ${w.email}: inbox rate ${inboxRate.toFixed(1)}% ${healthy ? "OK" : "LOW — extend warmup"}`);
  }

  // 3. Check daily limits are set
  const acctDetails = await instantly<Array<{ email: string; daily_limit: number | null }>>(
    "/accounts?limit=100"
  );
  const noLimit = acctDetails.filter((a) => !a.daily_limit);
  if (noLimit.length > 0) {
    console.log(`\nWARNING: ${noLimit.length} accounts have no daily limit set`);
  }

  return broken.length === 0;
}

Phase 2: Campaign Configuration (1 week before)

async function phase2CampaignConfig(campaignId: string) {
  console.log("\n=== Phase 2: Campaign Configuration ===\n");
  const campaign = await instantly<{
    name: string;
    sequences: Array<{ steps: Array<{ variants: Array<{ subject: string; body: string }> }> }>;
    campaign_schedule: { schedules: any[] };
    daily_limit: number | null;
    stop_on_reply: boolean;
    link_tracking: boolean;
    open_tracking: boolean;
    stop_on_auto_reply: boolean;
    email_gap: number;
  }>(`/campaigns/${campaignId}`);

  const checks = [
    { label: "Has sequences", pass: campaign.sequences?.length > 0 },
    { label: "Has email steps", pass: campaign.sequences?.[0]?.steps?.length > 0 },
    { label: "Has schedule", pass: campaign.campaign_schedule?.schedules?.length > 0 },
    { label: "Stop on reply enabled", pass: campaign.stop_on_reply === true },
    { label: "Link tracking disabled", pass: campaign.link_tracking === false },
    { label: "Open tracking enabled", pass: campaign.open_tracking === true },
    { label: "Daily limit set", pass: (campaign.daily_limit ?? 0) > 0 },
    { label: "Email gap >= 60s", pass: (campaign.email_gap ?? 0) >= 60 },
  ];

  let allPass = true;
  for (const check of checks) {
    console.log(`  ${check.pass ? "PASS" : "FAIL"}: ${check.label}`);
    if (!check.pass) allPass = false;
  }

  // Check A/B variants
  const step1 = campaign.sequences?.[0]?.steps?.[0];
  if (step1) {
    console.log(`  INFO: Step 1 has ${step1.variants.length} variant(s)`);
  }

  return allPass;
}

Phase 3: Lead List Hygiene

async function phase3LeadHygiene(campaignId: string) {
  console.log("\n=== Phase 3: Lead List Hygiene ===\n");

  // Check lead count
  const analytics = await instantly<{ total_leads: number }>(
    `/campaigns/analytics?id=${campaignId}`
  );
  console.log(`Total leads: ${analytics.total_leads}`);

  // Check block list
  const blocklist = await instantly<Array<{ bl_value: string }>>(
    "/block-lists-entries?limit=10"
  );
  console.log(`Block list entries: ${blocklist.length}+`);

  // Verify no internal domains are in lead list
  console.log("\nChecklist:");
  console.log("  [ ] Leads verified with email verification service");
  console.log("  [ ] Company domains in block list (your own + competitors)");
  console.log("  [ ] No role-based emails (info@, admin@, support@)");
  console.log("  [ ] Personalization variables populated (firstName, companyName)");
  console.log("  [ ] Test lead (your own email) included for QA");
}

Phase 4: Test Email & Webhook Verification

async function phase4TestAndWebhooks(campaignId: string) {
  console.log("\n=== Phase 4: Test & Webhooks ===\n");

  // Send test email
  const accounts = await instantly<Array<{ email: string }>>(
    "/accounts?limit=1"
  );
  if (accounts.length > 0) {
    await instantly("/emails/test", {
      method: "POST",
      body: JSON.stringify({
        eaccount: accounts[0].email,
        to_address_email_list: [process.env.TEST_EMAIL || "test@yourdomain.com"],
        subject: "Production Test — Instantly Integration",
        body: "This is a test email from the Instantly integration. If you received this, the setup is working correctly.",
      }),
    });
    console.log("Test email sent from:", accounts[0].email);
  }

  // Verify webhooks are registered
  const webhooks = await instantly<Array<{
    name: string; event_type: string; target_hook_url: string;
  }>>("/webhooks?limit=50");
  console.log(`\nWebhooks registered: ${webhooks.length}`);
  for (const w of webhooks) {
    console.log(`  ${w.name}: ${w.event_type} -> ${w.target_hook_url}`);
  }

  // Test webhook delivery
  if (webhooks.length > 0) {
    for (const w of webhooks.slice(0, 2) as Array<{ id: string; name: string }>) {
      try {
        await instantly(`/webhooks/${w.id}/test`, { method: "POST" });
        console.log(`  Tested: ${w.name} — check your endpoint`);
      } catch (e: any) {
        console.log(`  FAILED: ${w.name} — ${e.message}`);
      }
    }
  }
}

Phase 5: Launch & Monitor

async function phase5Launch(campaignId: string) {
  console.log("\n=== Phase 5: Launch ===\n");

  // Final confirmation
  const campaign = await instantly<{ name: string; status: number }>(
    `/campaigns/${campaignId}`
  );
  console.log(`Campaign: ${campaign.name} (status: ${campaign.status})`);

  // Activate
  await instantly(`/campaigns/${campaignId}/activate`, { method: "POST" });
  console.log("Campaign ACTIVATED");

  // Verify sending status
  const status = await instantly(`/campaigns/${campaignId}/sending-status`);
  console.log("Sending status:", JSON.stringify(status));

  // Monitor for first hour
  console.log("\nPost-launch monitoring:");
  console.log("  [ ] Check analytics after 1 hour for send activity");
  console.log("  [ ] Monitor bounce rate (should be <3%)");
  console.log("  [ ] Verify webhook events are arriving");
  console.log("  [ ] Check Unibox for replies");
}

// Run full checklist
async function main() {
  const campaignId = process.env.CAMPAIGN_ID!;
  const accountsOk = await phase1AccountHealth();
  if (!accountsOk) { console.log("\nFix account issues before proceeding."); return; }
  const configOk = await phase2CampaignConfig(campaignId);
  await phase3LeadHygiene(campaignId);
  await phase4TestAndWebhooks(campaignId);
  if (configOk) await phase5Launch(campaignId);
}

main().catch(console.error);

Error Handling

ErrorCauseSolution
Campaign won't activateMissing sequences/accounts/leadsRun Phase 2 checks
Test email not receivedAccount SMTP brokenRun vitals test
Webhook test failsTarget URL unreachableVerify endpoint is public HTTPS
High bounce rate post-launchUnverified leadsPause campaign, clean list

Resources

Next Steps

For version migration, see instantly-upgrade-migration.

svg-icon-generator

jeremylongshore

Svg Icon Generator - Auto-activating skill for Visual Content. Triggers on: svg icon generator, svg icon generator Part of the Visual Content skill category.

8227

d2-diagram-creator

jeremylongshore

D2 Diagram Creator - Auto-activating skill for Visual Content. Triggers on: d2 diagram creator, d2 diagram creator Part of the Visual Content skill category.

4926

automating-mobile-app-testing

jeremylongshore

This skill enables automated testing of mobile applications on iOS and Android platforms using frameworks like Appium, Detox, XCUITest, and Espresso. It generates end-to-end tests, sets up page object models, and handles platform-specific elements. Use this skill when the user requests mobile app testing, test automation for iOS or Android, or needs assistance with setting up device farms and simulators. The skill is triggered by terms like "mobile testing", "appium", "detox", "xcuitest", "espresso", "android test", "ios test".

14218

performing-penetration-testing

jeremylongshore

This skill enables automated penetration testing of web applications. It uses the penetration-tester plugin to identify vulnerabilities, including OWASP Top 10 threats, and suggests exploitation techniques. Use this skill when the user requests a "penetration test", "pentest", "vulnerability assessment", or asks to "exploit" a web application. It provides comprehensive reporting on identified security flaws.

4615

designing-database-schemas

jeremylongshore

Design and visualize efficient database schemas, normalize data, map relationships, and generate ERD diagrams and SQL statements.

11514

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

11410

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,1421,171

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

969933

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

683829

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

691549

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

797540

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

697374

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.