IMPLEMENTATION GUIDE
Choose native sync or a custom workflow
Close and Pipedrive have native EnrichLoops integrations. Authorize the connection, choose your source identifiers, and map enriched company and person fields to the CRM. Native connections manage writeback and can push changed enrichment data to linked records. Test a record and review its Activity before enabling automatic enrichment.
For HubSpot and other CRMs, use your own workflow around a Loop. Trigger a request when a company is created or its domain changes, then receive the completed profile on your HTTPS endpoint. Your handler writes the selected fields back through the CRM API. The Loop delivers data; your workflow controls CRM updates and any follow-up actions.
Map identifiers and fields deliberately
Use the company website domain or LinkedIn company URL for company enrichment. For contacts you already have, people enrichment accepts a work email or LinkedIn profile URL. These are separate lookups with different outputs. A company lookup fills account context; it does not automatically enrich every associated contact.
Start with the fields your team uses: industry for segmentation, employee count or range for qualification, and headquarters for territory routing. Store the freshness timestamps in dedicated fields when useful. Match returned values to your CRM field types; an employee range belongs in a text or mapped option field, while an employee count belongs in a numeric field.
Protect manual edits and prevent update loops
For native integrations, choose the field update policy, such as filling empty fields or overwriting unless a teammate has edited the value. Set a daily credit cap before enabling automation. For custom workflows, implement the same policy in your handler: read the existing value, decide whether enrichment can replace it, and leave fields untouched when the result provides no useful value.
Store the EnrichLoops task ID with the CRM record in custom workflows so the webhook can find the correct destination. Verify the webhook signature and track delivery IDs to avoid duplicate processing. Limit enrollment to changes in source identifiers so writing an enriched industry or headcount does not immediately start another lookup.
Test new records, repeats, and incomplete results
Test a new company, an updated domain, an existing record with a manually edited field, and a repeated webhook delivery. Confirm that the correct CRM record changes and that your handler preserves useful values when enrichment returns incomplete data. Use the Activity view for native connections, or your own task and writeback logs for a custom workflow.
Company records refresh every 14 days, with one credit per successful lookup and zero credits for repeats within the freshness window. Failed lookups are not charged. Native connections can keep linked records current as data changes; with a Loop, schedule or trigger additional lookups in your own workflow. Review field quality and credit use on a small sample before starting a larger backfill.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Pipedrive data enrichmentEnrich organizations and people with the native Pipedrive integration.IntegrationsNative CRM integrations and webhook workflow guides.LoopsEnrichment delivery for your custom CRM workflows.Common questions
Which CRMs have native integrations?
Close and Pipedrive have native EnrichLoops integrations. For HubSpot, Salesforce, and other CRMs, your workflow sends enrichment requests and writes the completed profile back through the CRM API.
Does company enrichment also enrich contacts?
Company and people enrichment are separate lookups. Use a company domain or LinkedIn company URL for the account, and an existing work email or LinkedIn profile URL for a contact.