clay-core-workflow-a
Build a complete lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment. Use when building lead generation features, enriching prospect lists, or creating automated data enrichment workflows. Trigger with phrases like "clay lead enrichment", "clay main workflow", "enrich contacts in clay", "clay prospect list", "clay enrichment pipeline".
Best use case
clay-core-workflow-a is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build a complete lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment. Use when building lead generation features, enriching prospect lists, or creating automated data enrichment workflows. Trigger with phrases like "clay lead enrichment", "clay main workflow", "enrich contacts in clay", "clay prospect list", "clay enrichment pipeline".
Teams using clay-core-workflow-a should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clay-core-workflow-a/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clay-core-workflow-a Compares
| Feature / Agent | clay-core-workflow-a | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build a complete lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment. Use when building lead generation features, enriching prospect lists, or creating automated data enrichment workflows. Trigger with phrases like "clay lead enrichment", "clay main workflow", "enrich contacts in clay", "clay prospect list", "clay enrichment pipeline".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# 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:
| Column | Type | Purpose |
|--------|------|---------|
| `domain` | Input (webhook) | Company domain to enrich |
| `first_name` | Input (webhook) | Contact first name |
| `last_name` | Input (webhook) | Contact last name |
| `Company Name` | Enrichment (Clearbit/Apollo) | Auto-filled from domain |
| `Employee Count` | Enrichment (Clearbit) | Company headcount |
| `Industry` | Enrichment (Clearbit) | Industry classification |
| `Work Email` | Enrichment (Waterfall) | Verified work email |
| `Job Title` | Enrichment (Apollo/PDL) | Current title |
| `LinkedIn URL` | Enrichment (Apollo) | Profile link |
| `ICP Score` | Formula | Computed fit score |
### 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
```typescript
// 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:
```json
{
"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
```bash
# 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
| Error | Cause | Solution |
|-------|-------|----------|
| Low email find rate (<40%) | Bad input data | Clean domains, remove personal email domains |
| Credits burning fast | Waterfall hitting all providers | Enable "stop on first result" |
| Duplicate rows in table | Same lead sent twice | Deduplicate before webhook submission |
| CRM push failing | Invalid field mapping | Test HTTP API column on single row first |
| Enrichment not running | Auto-run disabled | Enable auto-run in column settings |
## Output
- Enriched lead table with emails, titles, company data
- ICP scores for lead prioritization
- Qualified leads auto-pushed to CRM
- Credit usage report for cost tracking
## Resources
- [Clay University -- Enrichment Overview](https://university.clay.com/docs/actions-data-credits)
- [Clay University -- CSV Import](https://university.clay.com/docs/csv-import-overview)
- [Clay University -- Sources](https://university.clay.com/docs/sources)
## Next Steps
For AI-powered personalization and CRM sync, see `clay-core-workflow-b`.Related Skills
calendar-to-workflow
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
workhuman-core-workflow-b
Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".
workhuman-core-workflow-a
Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".
wispr-core-workflow-b
Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".
wispr-core-workflow-a
Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".
windsurf-core-workflow-b
Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".
windsurf-core-workflow-a
Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".
webflow-core-workflow-b
Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".
webflow-core-workflow-a
Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".
veeva-core-workflow-b
Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".
veeva-core-workflow-a
Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".
vastai-core-workflow-b
Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".