Deepline Native: Job Change

Detect a person’s recent job change.

Tool ID: job_change

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(
  'job_change',
  {
    "company_domain": "example.com",
    "company_linkedin": "https://www.linkedin.com/in/jane-doe",
    "professional_email": "jane.doe@example.com"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute job_change --input '{
  "company_domain": "example.com",
  "company_linkedin": "https://www.linkedin.com/in/jane-doe",
  "professional_email": "jane.doe@example.com"
}' --json

Example response

The static output schema is not detailed enough to generate a reliable example. Use deepline tools get job_change --json for the complete live contract.

Input reference

Detect whether a person has changed jobs. Charges $0.14 only when job_change_status is “moved”. Returns output.job_change_status and an optional person profile.

Name	Type	Required	Default	Details
`payload.company_domain`	`string`	No	—	Domain of the person’s previous/current employer (2-500 chars, e.g. acme.com).
`payload.company_linkedin`	`string`	No	—	LinkedIn company page URL or ID of the person’s previous/current employer (max 500 chars).
`payload.professional_email`	`string`	No	—	Work email address of the contact (max 254 chars).
`payload.personal_email`	`string`	No	—	Personal email address of the contact (max 254 chars).
`payload.contact_linkedin`	`string`	No	—	LinkedIn profile URL or ID of the contact (max 500 chars).
`payload.contact_full_name`	`string`	No	—	Full name of the contact when LinkedIn is unavailable (max 250 chars).
`payload.custom_fields`	`record`	No	—	Opaque metadata echoed back in finder responses via custom_fields (max 16 keys).

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`record`	Yes	—	Provider response payload.
`result.meta`	`record`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: per_result (per result).
Estimated Deepline credits: 1.96 per pricing unit.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Deepline Native: Job Change

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