Lemlist: Post Contact Sourcing Contacts

Add a person recommended by Lemlist contact sourcing as a contact at their company, optionally finding their email.

Tool ID: lemlist_post_contact_sourcing_contacts

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_post_contact_sourcing_contacts',
  {
    "leadId": "lead_123",
    "companyId": "company_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_post_contact_sourcing_contacts --input '{
  "leadId": "lead_123",
  "companyId": "company_123"
}' --json

Example response

The static output schema lacks the details for a reliable example. Use deepline describe lemlist_post_contact_sourcing_contacts --json for the complete live contract.

Input reference

Turns one contact-sourcing recommendation into a lemlist contact. leadId comes from a run’s contacts[].leadId — a People-Database id, not a contact id. companyId is required and verified: the new contact is filed under that account, whatever the person’s profile lists as their current employer. Someone your workspace already has as a contact is left where they are — an Add never moves a contact from one account to another — and the call answers 409 rather than reporting a creation that did not happen.

Name	Type	Required	Default	Details
`payload.leadId`	`string`	Yes	—	People-Database id, from a run’s `contacts[].leadId`.
`payload.companyId`	`string`	Yes	—	—
`payload.listId`	`string`	No	—	File the new contact into this contact list (`clt_xxx`). Omit to leave it in all contacts.
`payload.findEmail`	`boolean`	No	`false`	Also run email enrichment on the new contact. Spends enrichment credits.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`unknown`	Yes	—	Provider response payload.
`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.

​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