Lemlist: Post Contacts Lists Listid Entities

Add or Remove Contacts in a List.

Tool ID: lemlist_post_contacts_lists_listid_entities

Run this action

This action has conditional or dynamic input fields that cannot be represented by a reliable static example. Inspect the live contract before executing it:

deepline tools get lemlist_post_contacts_lists_listid_entities --json

Example response

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

{
  "data": {
    "message": "Example message",
    "addedCount": 123,
    "alreadyInList": 123
  }
}

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

Input reference

Adds existing CRM contacts to a static contact list, or removes them when ?action=remove is set. - Add (default): send a POST with a contactIds body. Contacts already in the list are silently skipped (no duplicates) and reported in alreadyInList. - Remove: send a POST with ?action=remove and a contactIds body. Contacts that are not in the list are silently skipped; removedCount reflects the associations actually removed. This only affects list membership, the contacts are not deleted from your CRM. The list must be a static contact list (clt_xxx). Dynamic lists (auto-populated by filter rules) and company lists are rejected. Removal uses POST ?action=remove on purpose: a DELETE request body is dropped by our stack, so DELETE on this path is not supported and returns 405 Method Not Allowed.

Name	Type	Required	Default	Details
`payload.listId`	`string`	Yes	—	The unique identifier of the contact list (`clt_xxx` format). Must be a static contact list. Pattern: `^clt_[a-zA-Z0-9]+$`.
`payload.action`	`"remove"`	No	—	Omit to add the contacts to the list. Set to `remove` to remove them from the list. Allowed: `remove`.
`payload.contactIds`	`array`	Yes	—	Array of contact IDs (`ctc_xxx` format) to add to or remove from the list. Required, non-empty, maximum 1,000 per request. Minimum items: 1. Maximum items: 1000.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.message`	`string`	No	—	—
`result.data.addedCount`	`integer`	No	—	Number of contacts added to the list (add only).
`result.data.alreadyInList`	`integer`	No	—	Number of contacts that were already in the list and therefore skipped (add only).
`result.data.removedCount`	`integer`	No	—	Number of list associations actually removed (remove only). Contacts that were not in the list are not counted.
`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 Lists Listid Entities

Run this action

Example response

Input reference

Output reference

Deepline cost

​Run this action

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

Example response

Input reference

Output reference

Deepline cost

Related documentation