Lemlist: Post Contacts Merge

Merge Contacts.

Tool ID: lemlist_post_contacts_merge

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_post_contacts_merge',
  {
    "primaryId": "primary_123",
    "secondaryIds": [
      "secondary_123"
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_post_contacts_merge --input '{
  "primaryId": "primary_123",
  "secondaryIds": [
    "secondary_123"
  ]
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "success": true,
    "primaryId": "primary_123",
    "merged": true,
    "mergedIds": [
      "merged_123"
    ],
    "remainingIds": [
      "remaining_123"
    ]
  }
}

Use deepline tools get lemlist_post_contacts_merge --json for the latest machine-readable contract.

Input reference

Merges up to 10 lemlist contacts into one. The survivor (primaryId) keeps its id and every value it holds; its empty fields are filled from the other contacts, which are then deleted. Everything attached to a deleted contact (leads in campaigns, activities, tasks, list memberships, inbox conversations) is moved to the survivor. When a CRM is connected, the survivor keeps its CRM link (or adopts the first linked record’s when it has none) and receives the merged values there; lemlist never merges or deletes anything in the CRM itself, so the other records’ CRM entries stay in the CRM, unlinked from lemlist — merge them CRM-side too, or a CRM import may recreate the duplicate. The contacts are folded into the survivor one at a time and the run stops at the first failure: mergedIds lists what went through, remainingIds what still exists. A first-fold failure returns an error See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.primaryId`	`string`	Yes	—	The surviving contact. A lemlist contact id (`ctc_xxx`) or one of the contact’s email addresses.
`payload.secondaryIds`	`array`	Yes	—	The contacts folded into the survivor then deleted, 9 at most. A lemlist contact id (`ctc_xxx`) or one of the contact’s email addresses. Must not contain `primaryId`, and each contact is listed once. Minimum items: 1. Maximum items: 9.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.success`	`boolean`	Yes	—	—
`result.data.primaryId`	`string`	Yes	—	ID of the surviving lemlist contact — resolved from the email when one was given.
`result.data.merged`	`boolean`	Yes	—	`true` once at least one contact was folded into the survivor.
`result.data.mergedIds`	`array`	Yes	—	IDs of the contacts folded into the survivor and deleted, in fold order.
`result.data.remainingIds`	`array`	Yes	—	IDs of the contacts NOT merged because an earlier fold failed. Empty when everything went through.
`result.data.rejectedFields`	`array`	No	—	Fields whose adopted value was refused by a uniqueness rule (kept survivor-side). Only present when it happened.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Lemlist: Post Contacts Merge

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation