Imported from jeremylongshore/tons-of-skills-marketplace (skills/.curated/clay-core-workflow-a/SKILL.md). Install upstream with npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-core-workflow-a. Copyright stays with the author (MIT).

Clay Core Workflow A: Lead Enrichment Pipeline

Overview

Primary workflow for Clay: take a list of companies or contacts, push them into a Clay table via webhook, let Clay's enrichment columns fill in missing data (emails, titles, company info, tech stack), and export the enriched results to your CRM or outreach tool. This is the core use case for 90%+ of Clay users.

Prerequisites

• Completed clay-install-auth setup
• Clay table with webhook source configured
• At least one enrichment provider connected (Apollo, Clearbit, Hunter, etc.)
• Destination CRM or outreach tool (HubSpot, Salesforce, Instantly, etc.)

Instructions

Step 1: Design Your Clay Table Schema

In the Clay web UI, create a table with these column types:

Step 2: Set Up Waterfall Email Enrichment

In Clay UI, add a waterfall enrichment column:

1. Click + Add Column > Find Work Email (Waterfall)
2. Configure provider order (cheapest first):
   • Apollo (2 credits) -- highest coverage
   • Hunter.io (2 credits) -- strong for smaller companies
   • Prospeo (2 credits) -- European coverage
3. Map input: first_name, last_name, domain
4. Enable Stop on first result to save credits
5. Enable Auto-run on new rows

Step 3: Push Leads into Clay via Webhook

// src/workflows/enrich-leads.ts
import { getClayClient } from '../clay/instance';

interface LeadInput {
  domain: string;
  first_name: string;
  last_name: string;
  source?: string;
}

async function enrichLeadList(leads: LeadInput[]): Promise<void> {
  const clay = getClayClient();

  // Validate and deduplicate before sending
  const cleaned = leads
    .filter(l => l.domain?.includes('.') && l.first_name && l.last_name)
    .filter((l, i, arr) =>
      arr.findIndex(x => x.domain === l.domain && x.first_name === l.first_name) === i
    );

  console.log(`Sending ${cleaned.length} leads to Clay (filtered ${leads.length - cleaned.length} invalid/dupes)`);

  const result = await clay.sendBatch(cleaned, 200);
  console.log(`Sent: ${result.sent}, Failed: ${result.failed}`);

  if (result.errors.length > 0) {
    console.error('Failed rows:', result.errors);
  }
}

Step 4: Add ICP Scoring Formula

In Clay, add a Formula column named ICP Score:

// Clay formula syntax (similar to spreadsheet formulas)
// Score 0-100 based on company fit

LET(
  size_score, IF(Employee Count > 500, 30, IF(Employee Count > 100, 20, IF(Employee Count > 20, 10, 0))),
  industry_score, IF(OR(Industry = "Software", Industry = "Technology", Industry = "SaaS"), 30, IF(Industry = "Financial Services", 20, 10)),
  title_score, IF(OR(CONTAINS(Job Title, "VP"), CONTAINS(Job Title, "Director"), CONTAINS(Job Title, "Head")), 25, IF(CONTAINS(Job Title, "Manager"), 15, 5)),
  email_score, IF(ISNOTEMPTY(Work Email), 15, 0),
  size_score + industry_score + title_score + email_score
)

Step 5: Configure CRM Export

Add an HTTP API column to push high-scoring leads to your CRM:

1. Click + Add Column > HTTP API
2. Set conditional run: ICP Score >= 70 AND ISNOTEMPTY(Work Email)
3. Configure the API call to your CRM:

{
  "method": "POST",
  "url": "https://api.hubapi.com/crm/v3/objects/contacts",
  "headers": {
    "Authorization": "Bearer {{HubSpot API Key}}",
    "Content-Type": "application/json"
  },
  "body": {
    "properties": {
      "email": "{{Work Email}}",
      "firstname": "{{first_name}}",
      "lastname": "{{last_name}}",
      "company": "{{Company Name}}",
      "jobtitle": "{{Job Title}}"
    }
  }
}

Step 6: Monitor Enrichment Results

# Check your table's enrichment progress in the Clay UI
# Key metrics to watch:
# - Email find rate: target >60%
# - Company enrichment rate: target >85%
# - Average credits per row: target <10
# - ICP score distribution: should have clear A/B/C tiers

Error Handling

Output

Produce a controlled enrichment manifest with source consent/purpose, table scope, provider waterfall, qualification conditions, deduplication key, credit budget, CRM action decision, and quality review. The output should not be treated as automatically accurate or permission to contact a lead; verify the data and applicable outreach/CRM policy before use.

Examples

Import a small staging list with synthetic or approved records, enable a two-provider waterfall only after a qualifying condition, and verify that a repeat submission updates rather than duplicates the CRM record. If quality, consent, or budget checks fail, stop the CRM action and retain the prior table configuration while the owner resolves the issue.

Resources

• Clay University -- Enrichment Overview
• Clay University -- CSV Import
• Clay University -- Sources

Next Steps

For AI-powered personalization and CRM sync, see clay-core-workflow-b.