Complete a professional email field
Use known person and company context to search for an available work email.
CRM data enrichment API
Fill missing work emails and business phone numbers inside your CRM.
Enrich a lead when it is created, assigned or qualified. Request its missing work email or business phone through the contact waterfall, then map returned fields into Salesforce, HubSpot or your own CRM.
Start with records from the regions and segments your team actually works.
CRM record event
IllustrativeRequestComplete missing fields before assignmentKnown contact · company and email selected
TargetWise routeOne entity per lookup
Person-company matchMatched
Requested contact fieldReturned
Existing CRM valuePreserved by merge rule
15+ sourcesavailable for contact waterfall routing
Email + phonefield-specific contact requests
Normalizedone result for CRM logic
One recordper on-demand request
Salesforce and HubSpot examples
Map API fields into a CRM contact or lead.
Call POST /api/v1/contacts/enrich with a supported person identifier and explicit email/phone switches. Check the result before applying these example mappings.
| TargetWise response | Salesforce Lead / Contact | HubSpot Contact | Write rule |
|---|---|---|---|
| data.work_email | Fill an empty field after confirming the person match. | ||
| data.business_phone | Phone | phone | Use the general phone field, not MobilePhone or mobilephone. |
| unresolved_fields | No field update | No field update | Keep existing values when a requested field is missing. |
| request_id | Integration log | Integration log | Record alongside the CRM record ID for troubleshooting. |
These are field-mapping examples for an integration you build, not native connectors. The current phone_type is unknown; do not label the number as mobile.
Where CRM enrichment fits
Fill the missing field at a meaningful record event.
CRM enrichment adds available external context to a known contact or company record so the next workflow decision has better inputs.
A record does not need every possible field to be useful. The practical question is which missing field blocks routing, qualification, research or review. TargetWise lets the calling workflow request that supported field when the decision occurs.
The CRM remains the system of record. TargetWise returns an enrichment outcome; your automation decides whether to preserve, add, review or ignore each returned value.
On demand is different from database cleanup.TargetWise does not take a CSV or sweep an entire CRM. Trigger individual requests from the record events that matter to your process.
Enrichment building blocks
Add only the context each CRM step needs.
Keep the request narrow and connect it to a clear downstream decision.
Request phone data for a known contact
Add the supported business-phone field when a workflow needs it.
Resolve the business behind the record
Use a company domain or supported identifier to retrieve available company data.
Use one TargetWise contract
Keep supplier credentials, retrieval routes and source field mappings out of your CRM workflow.
Call from deterministic CRM logic
Use application code when triggers, field selection and result branches should be explicit.
Support an AI-assisted review flow
Let an authorized agent request context while the host controls permissions and writes.
Reference CRM flow
Trigger, enrich, evaluate and merge.
Separate external retrieval from the decision to change a record.
Trigger on one record
Start when a contact or company is created, assigned, reviewed or advanced.
Select missing fields
Request only the supported data needed for the next CRM decision.
Evaluate the outcome
Branch on matched, partial or not-found results.
Apply merge rules
Preserve existing values and write only when your field policy permits.
Record integrity
Enrichment should improve a CRM without silently erasing trusted data.
A returned value is an input to your merge policy, not an automatic instruction to overwrite. Compare the result with the record’s origin, age and confirmation state.
Keep an audit of the identifier used, requested fields, outcome and any downstream change according to your own retention rules. Route ambiguous matches and sensitive changes to review.
- Preserve customer-provided values by default
- Define field-level acceptance and overwrite rules
- Do not retry no-match without new identity evidence
- Require approval before consequential writes
Example decision order
What the CRM workflow evaluates
1Is the intended person or company resolved?
2Was the required field returned?
3Does an existing trusted value already exist?
4Can the rule write, or is review required?
CRM moments
Request enrichment where it changes the next decision.
TargetWise fits into the workflow you already operate; it is not a replacement CRM or engagement suite.
Add company context to a new inbound record.
Resolve the business before routing logic evaluates the known lead.
Complete a missing contact field before review.
Request the work email or business phone needed by the assigned workflow.
Retrieve company context for a rule.
Use available business data as one input to the customer’s own qualification logic.
Let an agent request context without writing silently.
Expose enrichment through MCP and keep the final record update behind explicit merge logic.
Frequently asked questions
What to know before you build.
Inputs, triggers, returned fields and the practical limits of an event-driven CRM integration.
Free plan
Benchmark CRM enrichment on records that represent your real workflow.
Test the fields, markets and no-match cases that matter before connecting a production trigger.