Lemlist: Get Contact Sourcing

Get the buying-committee contacts found by a Lemlist contact-sourcing run, or whether it is still running.

Tool ID: lemlist_get_contact_sourcing

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_get_contact_sourcing',
  {
    "runId": "run_123",
    "companyId": "company_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_get_contact_sourcing --input '{
  "runId": "run_123",
  "companyId": "company_123"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "runId": "run_123",
    "companyId": "company_123",
    "status": "pending"
  }
}

Use deepline describe lemlist_get_contact_sourcing --json for the latest machine-readable contract.

Input reference

Reads one contact-sourcing run — by its own id, or the latest run of an account. The HTTP status carries the run state: 200 the run completed and contacts is filled, 202 the run is still queued or going (poll again), 400 the run failed and error says why, 404 no such run. Exactly one of runId or companyId is required.

Name	Type	Required	Default	Details
`payload.runId`	`string`	No	—	The run to read, as returned by `POST /contact-sourcing`.
`payload.companyId`	`string`	No	—	Read the LATEST run of this account instead (`cpn_xxx` format).

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.runId`	`string`	No	—	—
`result.data.companyId`	`string`	No	—	—
`result.data.status`	`"pending" \| "running" \| "completed" \| "failed"`	No	—	Allowed: `pending`, `running`, `completed`, `failed`.
`result.data.ranAt`	`string`	No	—	Format: `date-time`.
`result.data.completedAt`	`string`	No	—	Format: `date-time`.
`result.data.reasoning`	`string`	No	—	The AI’s read-out of the account — why it picked these people, or found nobody.
`result.data.error`	`string`	No	—	Only on a failed run.
`result.data.contacts`	`array`	No	—	—
`result.data.contacts[].leadId`	`string`	No	—	People-Database id. Pass it to `POST /contact-sourcing/contacts` to add this person as a contact.
`result.data.contacts[].role`	`"decision_maker" \| "user" \| "influencer"`	No	—	Allowed: `decision_maker`, `user`, `influencer`.
`result.data.contacts[].fitScore`	`number`	No	—	How well the person matches the team’s ICP, 0-100.
`result.data.contacts[].reasoning`	`string`	No	—	—
`result.data.contacts[].fullName`	`string`	No	—	—
`result.data.contacts[].jobTitle`	`string`	No	—	—
`result.data.contacts[].linkedinUrl`	`string`	No	—	—
`result.data.contacts[].country`	`string`	No	—	—
`result.data.contacts[].companyName`	`string`	No	—	The person’s CURRENT employer, which is not always the account classified.
`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