mcpField
E
emailbison

emailbison

github.com/cold-iqMarketing & growth347 installsUpdated 2w ago
Repository

About emailbison

emailbison is a migration reference for replacing EmailBison campaign operations with ColdIQ-resold Instantly endpoints, with Lemlist as an alternative. It maps actions and fields while noting differences in merge tags, schedules, sequences, and reply handling.

Key features

  1. 01Map EmailBison actions to Instantly
  2. 02Document Lemlist as an alternative
  3. 03Translate merge tags and campaign fields
  4. 04Map campaign, lead, and analytics operations
  5. 05Describe migration caveats

Use cases

  1. 01Migrate EmailBison campaigns to Instantly
  2. 02Adapt campaign fields and merge tags
  3. 03Choose endpoint mappings for a Lemlist setup

MCP support

It documents ColdIQ endpoints for Instantly and Lemlist campaign operations; it does not state an MCP interface.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cold-iq/coldiq-marketplace-skills --skill emailbison

After installing, type/emailbisonin Claude Code to confirm it loaded.

Bundled filesresources/analytics.md

Details

From the project README

EmailBison → ColdIQ (Instantly/Lemlist)

Note (important): ColdIQ does not resell EmailBison. There is no /v1/emailbison/* group. This skill maps every EmailBison campaign action to the closest ColdIQ-resold sender — Instantly by default (or Lemlist). Semantics differ: EmailBison merge tags are {FIRST_NAME} (caps, single brace) vs Instantly {{firstName}}; schedule/sequence field names differ. Re-map fields when migrating.

ColdIQ Marketplace Endpoints (Instantly substitution)

EmailBison taskMethodPathCreditsEndpoint IDNotes
Create campaignPOST/v1/instantly/campaignsfreeinstantly.campaigns.createwas POST /api/campaigns
Update settingsPATCH/v1/instantly/campaigns/{id}freeinstantly.campaigns.patchwas /update
Add leads (single)POST/v1/instantly/leadsfreeinstantly.leads.createuse campaign, not campaign_id
Add leads (bulk)POST/v1/instantly/leads/addfreeinstantly.leads.addwas /bulk/csv
Campaign statsGET/v1/instantly/campaigns/analyticsfreeinstantly.campaigns.analyticswas POST /stats
Daily chart statsGET/v1/instantly/campaigns/analytics/dailyfreeinstantly.campaigns.analytics.dailywas /line-area-chart-stats
Pause campaignPOST/v1/instantly/campaigns/{id}/pausefreeinstantly.campaigns.pausewas /pause
Activate campaignPOST/v1/instantly/campaigns/{id}/activatefreeinstantly.campaigns.activatewas /resume

Lemlist is the alternative substitution when a client runs Lemlist: lemlist.campaigns.create, lemlist.campaigns.leads.create, lemlist.campaigns.start, lemlist.campaigns.stats.

Migration mapping (EmailBison → Instantly)

EmailBison conceptInstantly equivalent
{FIRST_NAME} merge tag{{firstName}}
{COMPANY}{{companyName}}
POST /api/campaigns (name)POST /v1/instantly/campaigns (name + settings)
POST /api/campaigns/{id}/schedulecampaign_schedule inside campaign create/patch
POST /api/campaigns/{id}/sequence-stepssequences[].steps[] inside campaign create
POST /api/leads/bulk/csvPOST /v1/instantly/leads/add (JSON, not CSV)
GET /api/campaigns/{id}/repliesuse the master-inbox / lead reply views (see resources/analytics.md)
max_emails_per_day: 700, plain_text: true, open_tracking: falseColdIQ Instantly defaults (see instantly-api)

Create a campaign (substituted)

  1. Create with ColdIQ defaults + sequences (re-map merge tags first). → POST /v1/instantly/campaigns · free · instantly.campaigns.create
  2. Load leads (JSON, not CSV upload). → POST /v1/instantly/leads/add · free · instantly.leads.add
  3. Pull stats. → GET /v1/instantly/campaigns/analytics · free · instantly.campaigns.analytics

For reply handling, sentiment marking, and the analytics field reference, see resources/analytics.md.

Caveats

  • No 1:1 reply endpoint parity. EmailBison's per-reply sentiment marking (mark-as-interested / mark-as-automated) maps to Instantly's lead interest-status update (POST /v1/instantly/leads/update-interest-status), not a per-reply call.
  • Schedules/sequences are nested in Instantly's campaign object, not separate endpoints.
  • Confirm the actual target sender before migrating — some teams move to Lemlist instead of Instantly.

Comments

Markdown supported