# Spot CRM Contacts Whose Email Is from a Past Employer

**Use case:** 

A contact who changed jobs keeps receiving sequences at an address that will bounce. Paste the profile URLs from your CRM: this task returns the email at each person's current company, and labels it work_other when the only company address on record belongs to another employer, usually a past one. Those are the contacts to re-check before the next send.

## Input

```json
{
  "profileUrls": [
    "https://www.linkedin.com/in/jane-doe-example",
    "https://www.linkedin.com/in/john-smith-example",
    "https://www.linkedin.com/in/maria-garcia-example"
  ],
  "includePersonalEmails": false
}
```

## Output

```json
{
  "_status": {
    "label": "Status",
    "format": "string"
  },
  "_input": {
    "label": "Input",
    "format": "object"
  },
  "fullName": {
    "label": "Name",
    "format": "string"
  },
  "jobTitle": {
    "label": "Job title",
    "format": "string"
  },
  "companyName": {
    "label": "Company",
    "format": "string"
  },
  "email": {
    "label": "Best email",
    "format": "string"
  },
  "emailType": {
    "label": "Type",
    "format": "string"
  },
  "emailCount": {
    "label": "Addresses",
    "format": "number"
  },
  "profileUrl": {
    "label": "Profile",
    "format": "string"
  },
  "_note": {
    "label": "Note",
    "format": "string"
  },
  "_error": {
    "label": "Details",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The LinkedIn Email Finder — Bulk, Pay Only per Email Found Actor is ready to run with the inputs already set for "Spot CRM Contacts Whose Email Is from a Past Employer". [Sign up or log in](https://console.apify.com/create-task-from-example/phIYenrr7Mfhm6gE3) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Spot CRM Contacts Whose Email Is from a Past Employer" task

The LinkedIn Email Finder — Bulk, Pay Only per Email Found Actor will start running based on the input automatically. You can also change all the input fields, like linkedin profile urls and include personal mailboxes (gmail, yahoo, isp mail), to match your specific use case.

### 3. Receive the "Spot CRM Contacts Whose Email Is from a Past Employer" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as status, input, name, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Spot CRM Contacts Whose Email Is from a Past Employer" task via API](https://apify.com/b2bsearch/linkedin-email-finder.md).

## FAQ

### How does the task tell which contacts changed jobs?

The stale CRM email task compares each address on record with the person's current employer. A row labelled work_other has only an address at another company, which usually means the contact has moved on.

### What should I do with work_other rows?

Treat work_other rows from the stale CRM email task as do-not-send until checked. The row shows the contact's current company: find the address there, or reach that new account as a warm lead.

### Is work_other priced like a found email?

work_other rows cost less than an address at the current employer in the stale CRM email task, and profiles with nothing on record are free. The current prices per 1,000 are on the Actor's Pricing tab.

### Can I run the stale CRM email check every month?

Schedule the stale CRM email task monthly on your active contacts. Each run returns today's reading of the records; compare the email type across runs to catch new job changes.

## About this Actor

This example demonstrates how to use [LinkedIn Email Finder — Bulk, Pay Only per Email Found](https://apify.com/b2bsearch/linkedin-email-finder.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/b2bsearch/linkedin-email-finder.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/b2bsearch/linkedin-email-finder.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).