List Employer Changes
list_employer_changesAsk an ENRICHMENT RUN who appears to have changed employer, comparing what it fetched against the account each contact is on. For 'who moved', after a run has fetched the employers. It reads what the run left behind: no CRM call, no provider call, no credit, nothing queued or changed. A mover here is a FINDING, not an action. IT NEEDS A RUN THAT ASKED FOR THE EMPLOYER: a contact's employer has no home on a contact -- the CRM holds an account link, the provider holds a company name -- so the template must OBSERVE employer_name. A run that did not returns examined 0, which means 'nothing was compared', NOT 'nobody moved'. Check examined before believing moved. IT IS NOT run_job_change_sweep, which enriches, compares and queues the whole departure in one step and spends credits doing it; this only answers, over a run that already paid. EACH MOVER CARRIES provider_record_id: hand those to create_records_run's person_ids and it creates each person under their new company, with no second search and no second credit. That is the composition: enrich, compare, create.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes | The enrichment run whose staged employers to compare. | |
| moved_only | No | Return only the movers. The examined and moved counts are reported either way, so this narrows the rows and never the answer. | |
| connection_id | Yes | The CRM connection. Call list_crm_connections first. |