Contact Data Enrichment

Workflows that enhance contact records with additional data from external sources like Clay, Trustpilot, and phone validation services

Workflows in this Group

Key fields: clay_original_traffic_source, hs_analytics_source

Dependencies: Clay platform, RB2B, Trustpilot API

Domain Summary

Multiple redundant workflows routing contacts to Clay for external data enrichment, with scattered responsibilities for phone validation, company research, and traffic source attribution. Current architecture lacks centralized orchestration and proper error handling.

Current Problems

• 8 separate workflows performing similar Clay routing with different webhooks - no centralized enrichment strategy
• Test workflow (Trevor Test) still active in production
• Complex delays and notifications in main Clay workflow suggest unreliable external service integration
• Traffic source workaround using external RB2B data suggests attribution gaps
• No visible error handling or retry logic for failed external API calls
• Phone validation and Trustpilot enrichment isolated from main enrichment flow

Rearchitecture Approach

Consolidate into a unified Contact Enrichment orchestrator that routes to appropriate enrichment services based on contact attributes and enrichment requirements. Implement proper error handling, logging, and fallback mechanisms for external service dependencies.

Recommended Automations

Contact Enrichment Orchestrator

Purpose: Central entry point for all contact enrichment needs, routing to appropriate enrichment services based on contact status and data gaps

Trigger: Contact record created or updated with enrichment flag

Entry Criteria Formula: N/A

Logic Overview: Evaluate contact for enrichment needs (cold prospect, research required, phone validation, company data gaps). Route to appropriate enrichment sub-flows. Log enrichment attempts and results. Handle external service failures gracefully.

Replaces: Add to clay list, Add to clay list - cold, Trevor Test - enrich and add to clay table, Manual account research, ADMIN Company Enrichment to Clay

Required Fields:

Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._

Phone Validation Service

Purpose: Validate and correct phone numbers using external validation service

Trigger: Invoked by enrichment orchestrator when phone validation is needed

Entry Criteria Formula: N/A

Logic Overview: Send phone number to validation service. Update contact with corrected phone number if validation successful. Log validation results and any failures.

Replaces: Correct Phone Number

Required Fields:

Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._

Traffic Source Attribution Corrector

Purpose: Update native Salesforce attribution fields with more accurate external data when available

Trigger: Contact updated with Clay traffic source data

Entry Criteria Formula: N/A

Logic Overview: When Clay provides traffic source data, evaluate against existing attribution. Update Lead Source and Lead Source Detail fields with more accurate data. Maintain audit trail of attribution changes.

Replaces: Set proper original traffic source from RB2B

Required Fields:

Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._

Company Reputation Enrichment

Purpose: Enrich contacts with company reputation data from Trustpilot and similar sources

Trigger: Invoked by enrichment orchestrator for accounts needing reputation data

Entry Criteria Formula: N/A

Logic Overview: Call Trustpilot API for company reputation scores and review data. Update related Account record with reputation metrics. Flag high/low reputation scores for sales team attention.

Replaces: trustpilot - enrich contact

Required Fields:

Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._

Cross-Flow Interaction Model

Interaction handoffs were not provided. Add flowInteractionModel entries so build sequencing and contracts are explicit.

Migration Sequence

1. Create new enrichment tracking fields in Salesforce
2. Build Contact Enrichment Orchestrator as main entry flow
3. Migrate Clay webhook configurations to Salesforce external services
4. Build Phone Validation Service sub-flow
5. Build Company Reputation Enrichment sub-flow
6. Build Traffic Source Attribution Corrector
7. Test all enrichment flows with sample data
8. Deactivate original HubSpot enrichment workflows
9. Monitor enrichment success rates and adjust error handling

Architecture Diagram

flowchart TD
    A[Contact Created/Updated] --> B{Needs Enrichment?}
    B -->|Yes| C[Contact Enrichment Orchestrator]
    B -->|No| Z[End]

    C --> D{Enrichment Type}
    D -->|Cold Prospect| E[Clay Cold Prospect API]
    D -->|Phone Validation| F[Phone Validation Service]
    D -->|Company Research| G[Clay Research API]
    D -->|Reputation Data| H[Company Reputation Enrichment]
    D -->|Traffic Source Fix| I[Traffic Source Attribution Corrector]

    E --> J[Update Enrichment Status]
    F --> K[Update Phone + Validation Status]
    G --> L[Update Company Data]
    H --> M[Update Account Reputation Score]
    I --> N[Update Lead Source Fields]

    J --> O[Log Results]
    K --> O
    L --> O
    M --> O
    N --> O

    O --> P{Enrichment Complete?}
    P -->|Yes| Q[Mark Contact Enriched]
    P -->|No| R[Schedule Retry]

    Q --> Z
    R --> S[Wait Period]
    S --&gt; C</code></pre>