Mcp Clay To Instantly Smartlead Push

com.mambabuiltPublished by mambabuilt.comv1.3.1Updated Nov 7, 2026

Push enriched leads into an Instantly or Smartlead campaign, with ICP gating and dedupe.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Pushes enriched lead rows into an existing Instantly, Smartlead or HeyReach campaign via an Apify actor, with ICP score gating, dedupe and dry run.

What you can do
  • Push lead rows into an existing Instantly, Smartlead or HeyReach campaign, from a supplied array or an Apify dataset ID
  • Map Clay-style column names onto each sequencer's field names, with optional overrides and extra custom variables
  • Filter leads by a minimum ICP score and deduplicate against leads already in the campaign
  • Preview the exact request batches with a dry run before anything is sent
  • Return a flat summary of leads received, dropped, eligible, created, skipped and failed, with vendor messages per failed address
When to use it
Use it when you have enriched lead lists, for example from Clay or an Apify dataset, and want an assistant to load them into an existing outbound campaign with score gating and duplicate checks. Run a dry run first when pointing at a new campaign.
Requirements
Runs locally via npx (Node.js) as a stdio server, desktop only. Needs an APIFY_TOKEN environment variable for the Apify actor, plus the sequencer's own API key passed as the api_key input (Instantly v2, Smartlead, or HeyReach). The target campaign must already exist, and its ID is required. Network access to Apify and the sequencer API.
Before you install
It writes to your live sequencer campaign unless dry_run is true, so leads can be enrolled and contacted. It handles two credentials: APIFY_TOKEN and the sequencer api_key input. Runs consume Apify credits, charged per lead the sequencer confirms it created, with an optional max_charge_usd cap. Lead data is sent to Apify and to the chosen sequencer. It does not create campaigns or write sequence copy.

Installation

In SourceWeft

  1. Open Mcp Clay To Instantly Smartlead Push in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Sequencer Lead Push MCP Server

[Clay To Instantly Smartlead Push MCP server]

MCP server for the Mamba Labs Sequencer Lead Push actor on Apify.

Push enriched lead rows into an existing Instantly, Smartlead, or HeyReach campaign. ICP score gating and deduplication are built in, and a dry run shows you the exact payload before you send anything.

Install

bash
npx -y @mambalabsdev/mcp-clay-to-instantly-smartlead-push

Claude Desktop

json
{  "mcpServers": {    "mamba-clay-to-instantly-smartlead-push": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-clay-to-instantly-smartlead-push"],      "env": { "APIFY_TOKEN": "your-apify-token" }    }  }}

Get an Apify token at console.apify.com/account/integrations.

Tool

push_leads_to_sequencer

Maps your column names onto the sequencer's field names, drops leads below your ICP score threshold, drops leads already in the campaign, and sends the rest in batches.

InputTypeRequiredNotes
sequencerstringyesinstantly, smartlead or heyreach. HeyReach is LinkedIn native and keys a lead on linkedin_person_url rather than on email
campaign_idstringyesThe target campaign. It must already exist. Instantly campaign IDs are UUIDs; Smartlead and HeyReach campaign IDs are numeric.
api_keystringsee noteYour Instantly v2 key, your Smartlead key, or your HeyReach key
leadsarrayone ofLead rows. Each needs an email at minimum, or a linkedin_person_url on HeyReach.
dataset_idstringone ofAn Apify dataset ID from an upstream run
min_icp_scorenumbernoDrop leads scoring below this. Default 0.
deduplicatebooleannoCheck the campaign first. Default true.
dry_runbooleannoPreview without sending. Default false.
field_mappingobjectnoOverride the default column map
custom_variablesarraynoExtra columns to pass through
max_charge_usdnumbernoOptional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit to rely on the maximum cost per run set in Apify.

api_key is required for any run that calls the sequencer. A dry run with deduplicate false makes no calls at all and needs no key.

Returns one flat summary row: leads received, dropped for no usable identity (an email, or a LinkedIn profile URL on HeyReach), dropped by the ICP gate, dropped as duplicates, eligible, created by the sequencer, skipped by the sequencer, and failed, with the vendor's own message per failed address.

Dry run

dry_run: true runs every step, returns the exact request batches that would have been sent, and creates nothing. Nothing is billed.

Use it the first time you point at a new campaign. The payload you see is the real one, and your API key is never included in it.

Billing

You are charged per lead the sequencer confirms it created. Leads dropped by the gate, dropped as duplicates, with no usable email, skipped or rejected by the vendor, and every lead in a dry run are all free.

Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.

EventPrice (USD)
Actor Start (apify-actor-start)0.00005
Lead pushed to sequencer (lead-pushed)0.01

Pricing is on the actor's Apify page. Running this server consumes Apify credits.

Supported sequencers

SequencerAPINotes
Instantlyv2Needs a v2 key. Keys from v1 do not work: Instantly deprecated v1 on January 19, 2026.
Smartleadv1Current. Smartlead has no v2.
HeyReachpublic APILinkedIn native. Keys a lead on linkedin_person_url, so rows with no LinkedIn profile URL are dropped and rows with no email are kept.

What this server does and does not do

It is a thin client for the Apify actor. It passes your input through and returns the actor's output. The field mapping, the ICP gate, the deduplication and everything each vendor's API needs all live in the actor, not here.

The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. The run is allowed 1,800 seconds. If it is still going two minutes after that, the call stops waiting and returns the run ID with a link to it in the Apify Console, where the results land when it finishes. A run that does not succeed comes back as an error with its run ID and status.

It writes to your sequencer campaign unless dry_run is true. It does not create campaigns and it does not write sequence copy.

Related

Part of the Mamba Labs GTM actor fleet. The same tool is available alongside twenty others in @mambalabsdev/mcp-gtm-suite.

Built by Mamba Labs

Source: README.md at commit e9fe8b1

Tools

1

push_leads_to_sequencer

Push Leads to Sequencer

Push enriched lead rows into an existing Instantly, Smartlead, or HeyReach campaign. Maps common Clay column names onto each sequencer's own field names, optionally drops leads below a minimum ICP score, optionally deduplicates against the leads already in the destination campaign, and sends the rest in batches. Returns one flat summary row: how many leads were received, dropped for having no usable email, dropped by the ICP gate, dropped as duplicates, eligible, actually created by the sequencer, skipped by the sequencer, and failed, plus the vendor's own error message per failed address. The campaign must already exist; this does not create campaigns or write sequence copy. Set dry_run true to get back the exact request payload that would be sent without creating a single lead and without being charged, which is the safe way to check a mapping against a new campaign. Billing is per lead the sequencer confirms it created, so gated, duplicate, skipped, failed and dry-run leads are all free. Instantly uses API v2 and needs a v2 key; Smartlead uses API v1. Requires an APIFY_TOKEN and consumes Apify credits. This WRITES to your sequencer campaign unless dry_run is true.

Parametersleadsapi_keydry_runsequencerrequireddataset_idcampaign_idrequireddeduplicatefield_mappingmin_icp_scoremax_charge_usdcustom_variables

Version history

5
  1. v1.3.1LatestNov 5, 2026
  2. v1.3.0Oct 16, 2026
  3. v1.2.1Oct 6, 2026
  4. v1.2.0Oct 6, 2026
  5. v1.1.0Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts