Scope the records
Connect the CRM and pick the object and list. Or start with a small export. Source IDs stay with every record.
CRM enrichment
Find missing titles, normalize inconsistent fields and verify email addresses. Then write the selected values back to the correct CRM records.
HubSpot, Salesforce and Pipedrive through Pipedream OAuth. Records keep their source IDs.
100+ checks find the gaps, enrichment fills them, e-mail and phone lookups charged only when found.
Changed values go back to the matching records. You run the sync and choose the conflict rule.
For example: fill missing titles and standardize country values in a HubSpot segment.
Connect the CRM and pick the object and list. Or start with a small export. Source IDs stay with every record.
Run the checks: missing titles, inconsistent countries, role-based or disposable emails, duplicates.
Request the missing details. See what was found, what changed and what stayed open.
Map the fields, choose the conflict rule and write the changes back to the matching records.
Source IDs are kept through import and update, so a name alone never decides where a value lands.
Read and sync-back support per system. Plan requirements on the pricing page.
| Connection | Objects | Plan |
|---|---|---|
| HubSpot | Contacts, companies, deals | Premium |
| Salesforce | Leads, contacts, accounts, opportunities | Premium |
| Pipedrive | People, organizations, deals | Premium |
| Google Sheets | Spreadsheet rows and mapped cells | Pro |
| Airtable | Records in a selected base and table | Pro |
| Notion | Database records and properties | Premium |
Write-back is an action you run. Nothing changes in your CRM until you sync.
The HubSpot page covers properties, lists and the enrichment options step by step.
No. Pick one object and one list or segment. Or start with a small export as CSV and connect later.
By their source record ID, which ListPlus keeps on every row. Names alone are never used to match.
No. You choose the fields that are written, and Only fill empty keeps populated values. A conflict rule decides what happens when a value changed on both sides.
The gap stays visible and no credits are charged. The record keeps its status so you can decide whether further research is worth it.
No. You run it, from the list or through your own agent via the API. Scheduled triggers are not available yet.
Try the sample list or bring your own starting point.