CRM & Sequencer Sync

API v2 can push a CluGTM lead list into a connected CRM or sequencer:

No other destinations are supported. Outreach, Salesloft, Pipedrive and Close can’t be sync targets.

Before you start

1. Connect the destination in the app. Open Integrations in the sidebar, find HubSpot, Salesforce or Lemlist under Available and click Link. HubSpot and Salesforce connect by signing in; Lemlist asks for your Lemlist API key in the Connect Lemlist dialog. See CRM integration.
2. Have a list ready. Sync pushes every saved lead in the list. An empty list returns 400 validation_error.
3. Know what each destination needs. HubSpot and Lemlist need an email on the lead; Salesforce needs a last name (taken from the full name when missing). Leads without them end up in skipped or failed. Enrich the list first if emails are missing.

The flow

1. Quote. Call POST /credits/estimate with tool: "sync_to_crm" or "sync_to_sequencer", the list_id, the provider, and the same sub_action, campaign_id and field_mapping you’ll send to sync. You get a quote_id (5 minutes, single use) and the estimated_cost.
2. Ask a person. Show the provider, list, lead count and cost, and wait for a clear yes.
3. Sync. Call the sync endpoint with the same fields, the quote_id and approved: true. Up to 500 leads the push runs to completion and the response has the final counts.
4. Poll, for big lists. Above 500 leads the push is queued and the response has status: "pending". Poll GET /migrate/status/{workflow_id} until status is completed or failed.

# 1. Quote
curl -X POST https://api.cleanlist.ai/api/v2/credits/estimate \
  -H "Authorization: Bearer clapi_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"tool": "sync_to_crm", "list_id": "LIST_ID", "provider": "hubspot", "sub_action": "contacts"}'
 
# 2. After the user confirms, sync
curl -X POST https://api.cleanlist.ai/api/v2/migrate/crm \
  -H "Authorization: Bearer clapi_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "hubspot",
    "list_id": "LIST_ID",
    "sub_action": "contacts",
    "quote_id": "qte_v1_...",
    "approved": true
  }'

Sync a list to your CRM

POST /migrate/crm

Scope: sync:write · Cost: 0.2 credits per lead

Creates one CRM record per lead in the list.

Request body

Unknown fields are rejected with 422 validation_error; for example, sequence_id is no longer accepted.

Enroll a list in a Lemlist campaign

POST /migrate/sequencer

Scope: sync:write · Cost: 0.2 credits per lead

Adds every lead in the list as a contact in a Lemlist campaign.

Request body

curl -X POST https://api.cleanlist.ai/api/v2/migrate/sequencer \
  -H "Authorization: Bearer clapi_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "lemlist",
    "list_id": "LIST_ID",
    "campaign_id": "cam_9d41ab2f",
    "quote_id": "qte_v1_...",
    "approved": true
  }'

The response

Both endpoints return the same shape. For a list of up to 500 leads the push runs inside the request and the counts are final:

{
  "workflow_id": "cl-sync_9f2c1a4b7e3d0f28",
  "status": "completed",
  "provider": "hubspot",
  "list_id": "LIST_ID",
  "total_leads": 128,
  "successful": 121,
  "failed": 2,
  "skipped": 5,
  "estimated_cost": 26,
  "credits_charged": 25,
  "timestamp_ms": 1751404800000
}

Lists over 500 leads: queued syncs

A list of more than 500 leads is queued instead of pushed inside the request. The sync endpoint answers at once with status: "pending", successful, failed and credits_charged at 0, and a workflow_id (it starts with crm-bulk-push-). skipped can already count CSV rows that are people already on the list, which are pushed once.

GET /migrate/status/{workflow_id}

Scope: sync:write · Cost: free

Returns the counts so far. Poll it every few seconds until status is completed or failed.

curl https://api.cleanlist.ai/api/v2/migrate/status/WORKFLOW_ID \
  -H "Authorization: Bearer clapi_your_api_key"

{
  "workflow_id": "crm-bulk-push-org_2xyz...-...",
  "status": "completed",
  "total_leads": 12000,
  "successful": 11640,
  "skipped": 210,
  "failed": 50,
  "unpaid": 100,
  "credits_charged": 2328,
  "timestamp_ms": 1751404800000
}

Once completed, successful + skipped + failed + unpaid equals total_leads. An unknown handle, a handle from another workspace, or one that finished and expired returns 404 not_found.

Cost

Sync costs 0.2 credits per lead, rounded up per call. The quote prices every lead in the list (128 leads quote 26 credits), and those credits are reserved when the push starts. When it finishes you’re charged only for the leads written to the destination, and skipped and failed leads are refunded: in the example above, 121 written leads cost 25 credits. If the push fails as a whole, the reservation is refunded. A queued push holds the quoted credits for its whole run and settles once at the end, so it never costs more than the quote.

Errors

See Errors & Rate Limits for every code.

Preview and discovery routes

Three free routes help an agent check a push before quoting it: POST /migrate/preview (what a push would do), GET /migrate/sequencer/campaigns (your Lemlist campaigns and their ids) and GET /migrate/crm/connections (which destinations are connected). They’re built for the CluGTM MCP, and aren’t available to AppSumo-only workspaces (they return 403 there). If they aren’t available to you, copy the campaign id from Lemlist.

Related

• Credits & the quote model
• Lead Lists
• People Finder API
• CRM integration
• Integrations overview
• Connect CluGTM to Claude (MCP)