Instantly Campaign Launcher

Create and launch an Instantly.ai cold email campaign with D0/D3/D8 sequences and bulk-import leads via API, no dashboard needed.

Security Scan

The skill appears to do what it claims (create campaigns and import leads to Instantly.ai) but the package/registry metadata omits the required API credential and a few minor manifest inconsistencies that you should verify before installing.

Purpose & Capability

Name/description match the implementation: the code and SKILL.md call api.instantly.ai to create campaigns, add sequences, and import leads. However the registry metadata lists no required env vars or primary credential while both SKILL.md and the code require an INSTANTLY_KEY (or config.instantlyKey). This metadata omission is an incoherence.

Instruction Scope

Runtime instructions are scoped to Instantly API usage and local files: edit scripts/campaign.config.js, provide leads.json, and set INSTANTLY_KEY. The code only reads those files and the INSTANTLY_KEY and makes HTTPS calls to api.instantly.ai; it does not attempt to read unrelated system files or contact other endpoints.

Install Mechanism

No install spec (instruction-only installation) and no downloads. The package includes two JS scripts bundled in the skill, which is consistent with a run-from-source usage model. No external installers or remote code downloads are used.

Credentials

The skill requires a single API bearer token (INSTANTLY_KEY) which is proportionate to its purpose. The concern is that the registry metadata did not declare this required environment variable or a primary credential, creating a mismatch in the manifest that could mislead users or automated reviewers.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and does not persist credentials itself. It only reads local config and leads files and posts to the Instantly API, which is appropriate for its stated function.

What to consider before installing

This skill's code and instructions match the stated purpose, but the registry metadata failing to declare the required INSTANTLY_KEY is a red flag (likely an oversight, but confirm before trusting). Before installing/running: 1) Verify INSTANTLY_KEY is an Instantly API key from app.instantly.ai and keep it secret (do not paste into public repos). 2) Inspect the included scripts (they are provided) and test with a non-production Instantly account and dummy leads to confirm behavior. 3) Ensure you have the right to email the leads and that your campaign complies with anti-spam laws and your organization’s policies. 4) If you plan automation, consider rotating the API key after testing and store it in a secure secret manager rather than plain env vars. If you need absolute assurance, ask the publisher to update the registry metadata to declare INSTANTLY_KEY as a required credential (primaryEnv) before installing.

skill-instantly-campaign-launcher

Programmatically create an Instantly.ai cold email campaign with D0/D3/D8 sequences and bulk-import leads — all via Instantly API v2. One script, zero dashboard clicking.

What it does

1. Creates a new Instantly campaign (or finds an existing one by name)
2. Adds a 3-step D0/D3/D8 email sequence to the campaign
3. Imports leads from a JSON file (with dedup/skip for existing leads)
4. Reports imported/skipped/failed counts

Use cases

• Launching any cold email campaign via code (no UI required)
• B2B agency or service business outreach
• Quickly adapting a campaign template for new ICPs or industries

Inputs

• INSTANTLY_KEY — Instantly API v2 Bearer token (set as env var)
• scripts/campaign.config.js — campaign name, schedule, D0/D3/D8 email bodies
• leads.json — array of lead objects: {email, firstName, lastName, companyName, website}

Outputs

• Instantly campaign created (or found) with sequences attached
• Leads imported; console report: total / imported / skipped / failed

Scripts

• scripts/campaign-launcher.js — main entry point
• scripts/campaign.config.js — config template (edit before running)

Usage

# 1. Get your Instantly API v2 token from app.instantly.ai → Settings → API Keys
export INSTANTLY_KEY=your_token_here

# 2. Edit scripts/campaign.config.js — set campaign name, schedule, email copy
# 3. Create leads.json (array of lead objects)
# 4. Run:
node scripts/campaign-launcher.js --config scripts/campaign.config.js --leads leads.json

leads.json format

[
  { "email": "[e-mail]", "firstName": "John", "lastName": "Smith", "companyName": "Acme Inc", "website": "acme.com" },
  { "email": "[e-mail]", "firstName": "Jane", "companyName": "Corp IO" }
]

campaign.config.js format

module.exports = {
  campaignName: 'My Outreach Campaign',
  schedule: {
    name: 'Business Hours',
    timing: { from: '09:00', to: '17:00' },
    days: { monday: true, tuesday: true, wednesday: true, thursday: true, friday: true, saturday: false, sunday: false },
    timezone: 'America/New_York', // or Asia/Dubai, Europe/London, etc.
  },
  sequences: [
    { step: 1, delay: 0, subject: 'Your subject', body: 'Hi {{firstName}}, ...' },
    { step: 2, delay: 3, subject: 'Re: Your subject', body: 'Follow-up body...' },
    { step: 3, delay: 8, subject: 'Last note, {{firstName}}', body: 'Closing body...' },
  ],
};

Notes

• Instantly API v2 — sequences endpoint: POST /campaigns/:id/sequences
• Dedup: 409 responses = lead already in campaign (counted as skipped, not error)
• Rate limit: 200ms sleep between lead imports to avoid 429s
• Known issue: Instantly API v2 /sequences endpoint occasionally returns 404 → add sequences manually in dashboard if this occurs
• Instantly free plan supports unlimited campaigns; warming up inboxes recommended before launch