CRM Lead Enrichment & Scoring – Emails, Phones, Social Links

What this Actor does

It enriches CRM contacts with publicly available data and optional third-party APIs. It accepts contacts from JSON, CSV, or an Apify dataset, normalizes and validates contact fields, deduplicates records, enriches website and company signals, scores lead quality, and can deliver results to downstream integrations.

What can this Actor do?

• Multiple input sources: JSON, CSV, or dataset ID
• Website enrichment for metadata, emails, social links, phone, address, and job-title hints
• Optional paid enrichment with Clearbit and Hunter
• Deduplication using configurable keys
• Quality scoring with signal breakdown
• Confidence, caching, learning, and budget-control features
• Optional webhook, n8n, and OpenClaw integrations

Why use it

The Actor helps clean and enrich CRM data so teams can:

• Improve outbound targeting with validated contact signals
• Prioritize stronger leads using quality scores
• Reduce manual research and data cleanup
• Route high-value leads into sales workflows
• Control enrichment costs with adaptive and budget-aware settings

How to use it

1. Open the Actor and choose contactsSource.
2. Provide contacts using contactsJson, contactsCsv, or datasetId.
3. Map fields with emailField, firstNameField, lastNameField, and companyField.
4. Configure enrichment, crawling, scoring, integrations, and intelligence settings as needed.
5. Run the Actor and review the Dataset and Output tabs.

Input overview

Top-level input groups:

• contactsSource, contactsJson, contactsCsv, datasetId
• emailField, firstNameField, lastNameField, companyField
• maxContacts, dedupeKeys, skipTestDomains
• enrichment
• crawling
• scoring
• integrations
• intelligence
• output

Supported enrichment providers:

• Website fallback enrichment
• Clearbit
• Hunter

Useful controls:

• crawling.maxRequestsPerMinute
• crawling.maxConcurrency
• crawling.requestTimeoutSecs
• crawling.maxRetries
• crawling.useProxy
• crawling.usePlaywrightFallback

Output

The Actor writes:

• Dataset items to the default dataset
• A summary to OUTPUT_SUMMARY in the default key-value store
• Summary plus full results to OUTPUT in the default key-value store

Each dataset item contains fields like:

• contactId
• input
• normalized
• enrichment
• metrics
• dedupe
• score
• status
• chargeable
• reason
• leadType
• warnings

Example dataset item:

{
  "contactId": "abc123",
  "input": {
    "email": "john@example.com",
    "firstName": "John",
    "company": "Example Inc"
  },
  "normalized": {
    "email": "john@example.com",
    "emailValid": true,
    "domain": "example.com",
    "rootDomain": "example.com",
    "isSubdomain": false,
    "subdomainLabel": null,
    "isTestDomain": false,
    "isFreeEmailProvider": false,
    "companyNameNormalized": "Example Inc",
    "firstName": "John",
    "lastName": null
  },
  "enrichment": {
    "website": {
      "url": "https://example.com",
      "title": "Example Inc - Home",
      "metaDescription": "Example company homepage",
      "foundEmails": ["info@example.com"],
      "socialLinks": {
        "facebook": null,
        "instagram": null,
        "linkedin": "https://linkedin.com/company/example",
        "twitter": null,
        "youtube": null
      },
      "phone": null,
      "address": null,
      "jobTitle": null
    },
    "clearbit": null,
    "hunter": null
  },
  "metrics": {
    "enrichmentSourcesUsed": ["website"],
    "fetchTimesMs": {
      "website": 2341
    },
    "errors": [],
    "confidenceScore": 92
  },
  "dedupe": {
    "isDuplicate": false,
    "duplicateOf": null,
    "dedupeHash": "..."
  },
  "score": {
    "value": 78,
    "breakdown": {
      "emailValid": 25,
      "hasWebsite": 20,
      "hasPhone": 15,
      "hasSocial": 10,
      "companySignals": 8
    }
  },
  "status": "ok",
  "chargeable": true,
  "leadType": "business",
  "warnings": []
}

Intelligence and automation features

• Adaptive enrichment can skip paid providers when confidence is already high.
• Domain cache can reuse website and provider results across runs.
• Progressive pipeline can limit paid APIs to a top-confidence subset.
• AI fallback supports off, heuristic, and webhook modes.
• Domain learning tracks reliable and unreliable domains over time.
• Budget guardrails cap Clearbit and Hunter calls per run.
• Integrations can send results to generic webhooks, n8n, or OpenClaw.
• Route-specific webhooks can be used for high-score or failed contacts.

Marketing and intent signals

Use these as GTM signals:

• Contactability: valid email, phone, social presence.
• Company maturity: richer metadata, address presence, about/contact pages.
• Quality/intent proxy: stronger company signals and lower failure patterns.
• Reliability: confidence score, explainability notes, domain-learning state.

Suggested workflow:

• Route score >= threshold and strong confidence to outbound sequence.
• Route failed/partial leads to nurture or verification workflows.

Tips and advanced options

• Start with website-only enrichment to keep costs low.
• Keep concurrency/rate conservative for stable crawling.
• Enable caching and learning for recurring runs on similar domains.
• Enable adaptive/progressive mode before turning on paid APIs at scale.
• Use route webhooks for high-score and failed queues.

Compliance

Use the Actor responsibly and in compliance with privacy laws, target-site policies, and third-party API terms, including GDPR and CCPA where applicable.

Support

If this Actor helps your workflow, please leave a 5-star rating on the Actor page.

Quick video walkthrough: https://youtu.be/81tHxtsWMb8?si=K3MYD_WpcUM3rjLU