Mcp Clay To Instantly Smartlead Push

com.mambabuilt由 mambabuilt.com 發布v1.3.1更新於 Nov 7, 2026

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

已驗證STDIO僅桌面效率與工作流商業與電商

概覽

AI 產生的概覽

透過 Apify actor 將已補齊的潛在客戶資料推送到既有的 Instantly、Smartlead 或 HeyReach 行銷活動，支援 ICP 評分過濾、去重與試跑。

可以做什麼
  • 將名單資料列推送到既有的 Instantly、Smartlead 或 HeyReach 行銷活動，資料可來自傳入的陣列或 Apify 資料集 ID
  • 把 Clay 風格的欄位名稱對應到各序列工具的欄位名稱，可覆寫對應並附加自訂變數
  • 依最低 ICP 評分過濾名單，並與行銷活動中既有的名單去重
  • 透過試跑預覽實際會送出的請求批次
  • 回傳彙總結果：接收、捨棄、合格、建立、略過與失敗的名單數量，並附上每個失敗地址的廠商訊息
適用情境
適用於已備妥補齊後的名單（例如來自 Clay 或 Apify 資料集），希望由助理在評分過濾與查重後匯入既有外呼行銷活動的情境。第一次指向新的行銷活動時，建議先試跑。
執行需求
透過 npx（Node.js）在本機以 stdio 執行，僅限桌面端。需要 APIFY_TOKEN 環境變數供 Apify actor 使用，並透過 api_key 輸入提供序列工具本身的金鑰（Instantly v2、Smartlead 或 HeyReach）。目標行銷活動必須已存在且需提供其 ID。需要連線至 Apify 與序列工具 API 的網路。
安裝前請注意
除非 dry_run 為 true，否則會寫入實際的序列工具行銷活動，名單可能被加入並開始接觸。涉及兩組憑證：APIFY_TOKEN 與序列工具的 api_key 輸入。執行會消耗 Apify 額度，依序列工具確認建立的名單筆數計費，可用 max_charge_usd 設定上限。名單資料會傳送給 Apify 與所選的序列工具。它不會建立行銷活動，也不撰寫序列文案。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Clay To Instantly Smartlead Push，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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

來源：README.md，提交 e9fe8b1

工具

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.

輸入參數leadsapi_keydry_runsequencer必填dataset_idcampaign_id必填deduplicatefield_mappingmin_icp_scoremax_charge_usdcustom_variables

版本歷史

5
  1. v1.3.1最新Nov 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

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分