Jipup CRM workflows · Update
Keep CRM data up to date HubSpotSalesforcePipedrive and other CRMs

Keep your CRM up to date. Every record was right, once.

One contact gets promoted, another moves to a new company, a third has no job at all. Your CRM keeps whatever was typed into it. Two workflows read the source that does change, rewrite the record and alert the rep who owns it, so your CRM data stays up to date without anyone chasing it.

your CRM · contacts
ContactJob titleCompanyChecked
Claire Foster Marketing Manager Ramp 14 months ago
Jason Miller Sales Manager Gusto 14 months ago
Sarah Mitchell Consultant Northwind Consulting 14 months ago
Mark Levin CTO Notion 14 months ago
Nadia Rahman Growth Manager Deel 14 months ago
2 updates · 1 departure · 3 tasks created 5 records, last checked 14 months ago.
The problem · 1

CRM data decay: nothing moves in your CRM, everything moves outside.

A record doesn't go stale on its own: it stays exactly as it was written. Five events, out in the world, make it wrong, and not one of them leaves a trace in the CRM. Across our customers' databases we observe 15 to 30% of B2B contacts changing jobs each year, depending on the segment.

The problem · 2

Outdated contact data doesn't look like an error.

That's what makes it expensive: it's spelled right, filled in, well formatted. No data quality check catches it. Here are the four shapes it takes in every database, plus a fifth that isn't a defect at all.

01

The contact changed companies

He left eight months ago. The record still ties him to his former employer, with the work address that goes with it, the one that was switched off the day he left.

CRM Sales Manager · Gusto
actual Head of Sales · Rippling
j.miller@gusto.com mailbox closed

What it costs: sequences sent into the void, and an account you think is covered when nobody is left in it. Turn a job change into a buying signal →

02

The job title no longer fits

She's still at the company, still reachable, but she's been promoted. Your CRM talks to her like an individual contributor while she now owns the budget.

CRM Marketing Manager
actual VP Marketing
segmented as non decision-maker

What it costs: the right person with the wrong pitch, and segments that file your best records in the wrong bucket.

03

The contact has no current role

End of contract, layoff, career break: the person shows no current position, and the record keeps presenting them as an employee of their former company.

last role Consultant · Northwind Consulting
ended March 2026
current role none

What it costs: follow-ups sent to an employer she has left, at an address that no longer exists. Remove dead email addresses from your CRM →

04

The company record dates from the import

Headcount, industry, website, address: the values entered on day one were never touched again. The company, meanwhile, has tripled in size.

headcount 40 → 180
industry empty · website empty
created Mar 12, 2024, never edited

What it costs: an ICP computed on two-year-old headcounts, and your biggest accounts filed among the small ones. Enrich company records, French legal data included →

05 · a different kind

And the reverse: your best customer just joined a prospect

The same event, read the other way. Someone who knows you, who has already bought, who has already championed your product internally, lands at an account where you have no way in. It's the best opening signal for a sales cycle, and it shows up nowhere in your CRM, because nothing writes it there.

What it's worth: a warm way into a cold account, as long as you learn about it while the person is settling in, not a year later. Estimate what it's worth on your database → Track champion moves as buying signals →

Laura Bennett
yesterday customer at Ramp
today VP Marketing · Rippling (prospect)
The problem · 3

Nobody discovers a stale record. They trip over it.

An email that bounces, a front desk that says "he doesn't work here anymore": it's usage that reveals the error, months after the event. In the meantime the record has been used: called, counted in a report, targeted by a campaign. The Ogo Security case: 21 champion moves tracked in 30 days →

One contact record, two years, three events Illustrative diagram · no delay is fixed: records are checked in real time, as often as you set
Promotion Company change Departure Without checks 21 months out of 24 with a wrong record With Jipup workflows until your next run today 6 months 1 year 18 months 2 years
The record is right The record is wrong An event, out in the world

The dates are an example; the mechanism isn't. Without checks, a record stays wrong until someone notices while using it, and nothing guarantees that day ever comes. The agent reads the source in real time: the gap between the event and the fix comes down to how often you have it run.

What you can do about it

Two workflows that read the source that moves.

Job change tracking and CRM enrichment do the same job: read the source that does change (the person's LinkedIn profile, the company's LinkedIn page, the French company registry) and rewrite the record in your CRM. They stack.

LinkedInClaudeHubSpotSalesforce

Solves The contact changed companies · The job title no longer fits · The contact has no current role

Job change tracking

Workflow · Update

Checks, contact by contact, whether the person still holds the role your CRM says. It finds their LinkedIn profile (the one on the record, or it looks it up), reads it, compares it with what you have, and only writes when it's sure.

  • Writes the new job title, company and location on the record
  • Repoints the contact's primary company to the new employer
  • Creates the company record if it's missing from your CRM
  • Tells an internal promotion apart from a company change
  • Flags departures without writing anything in the job title
  • Creates a sales task, assigned to the record owner
  • Re-enriches email and mobile at the new company, optionally
  • Keeps the former employer as a secondary association, or detaches it if you choose

Before comparing anything, the agent checks that the profile it found really belongs to the person. A namesake's profile reads just as cleanly as the right one: without that check, a stranger's job would end up written on your record.

When the new employer exists nowhere in your database, the agent creates the company record from what the change revealed (name, domain, headcount), then associates it. You get a filled-in account, not an empty shell. Without this step the update stays cosmetic: the title is fixed, but account views, reports and ABM keep counting the contact at the old company.

LinkedIn

Solves The job title no longer fits

Contact profile refresh

Skill · CRM enrichment

Rereads the contact's LinkedIn profile and realigns the record with it: job title, location, profile URL.

  • By default, only fills fields that are still empty
  • The overwrite option turns it into a true refresh of records already filled in
  • An empty field on LinkedIn never erases a value in your CRM
LinkedIndata.gouv, French government open data

Solves The company record dates from the import

Company record refresh

Skill · CRM enrichment

Realigns the company record with two sources that are kept current: its LinkedIn page and, for companies registered in France, the national business registry (INSEE).

  • Industry, headcount, website, address, description, LinkedIn page
  • For French companies: SIREN, head-office SIRET, APE code, legal form, headcount band, from data.gouv
  • The INSEE status says what no other source does: the company is active, or it has ceased trading
  • Replaces outdated values, never with blanks; the same overwrite option applies

The legal data doesn't depend on LinkedIn: a small business with no LinkedIn page still has a SIREN, and that's exactly the one with the thinnest record. Companies registered in France only.

Four workflows in Jipup · the other two: Duplicate detection and merging · New hire detection · see also CRM enrichment for missing data

How it works

Set it up once. It keeps coming back on its own.

OAuth connection to your CRM, once. Then you decide how often it runs, on which records, and what it's allowed to write. Weekly, daily, or on your own schedule: spend is capped by the volume per run and the eligibility rules, not by a forced delay between runs.

01 When it runs, on which records, and how far it goes without you.

Agent settings · Job change tracking All changes saved.
Schedule · Frequency
Manual Weekly Daily Cron
Conditions · Which records are eligible
HubSpot segment · Customers & champions2,480 contacts
A HubSpot segment, or your own conditions on CRM properties.
Volume per run
500 records max1,500 to 3,000 credits
Enrichment after a job change
Work email+5 credits / record found
Mobile+50 credits / record found
If a value already exists in the CRM: enrich anyway (overwrite). Nothing is charged when nothing is found.
Company reassociation
Detach the former company from the contact
Off: the former company stays associated as secondary.
Run Save 3 credits per contact scanned, +3 once if the LinkedIn URL must be found

02 Every write is logged: the old value, the new one, and what triggered it.

Activity · Job change tracking Trigger: scheduled
480records checked
7changes written
7tasks created
0fields cleared
HubSpot objectChangeStatusCredits
Jason Miller Title Sales Manager Head of Sales · Company Gusto Rippling new email found Done 8
Claire Foster Title Marketing Manager VP Marketing internal promotion Done 3
Sarah Mitchell Left Northwind Consulting, no current role task created, title unchanged Done 3
Mark Levin No change detected Done 3
Emily Chen Can't be verified: the LinkedIn profile belongs to a namesake Skipped 0

Each row opens on the detail: old and new value field by field, LinkedIn profile source, confidence level, and a direct link to the HubSpot record.

Get started

250 free credits when you create your account.

250free credits, no credit card
3credits per contact scanned
1credit per company refreshed from LinkedIn

A job change scan is billed per scan, whether or not it finds a change: you pay for the check, not the outcome (+3 credits once if the LinkedIn URL has to be found). A contact whose profile can't be found, or whose profile isn't the right person, isn't charged. Email (5 credits) and mobile (50 credits) re-enrichment after a change are billed only when found. A company refresh costs 1 credit from its LinkedIn page (+1 if the page URL has to be found) and 1 for French legal data. Your free credits cover 83 contact scans. Plans start at €120 a month for 10,000 credits, no commitment. See pricing and credit packs →

Start for free Book a demo 250 free credits, no credit card. Connect your CRM in two clicks.
Native integration with HubSpot and Salesforce · and other CRMs
HubSpot Salesforce Pipedrive