Execute Clay primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "clay main workflow", "primary task with clay".
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.
clay-install-auth setupIn 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 |
In Clay UI, add a waterfall enrichment column:
first_name, last_name, domain// 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);
}
}
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
)
Add an HTTP API column to push high-scoring leads to your CRM:
ICP Score >= 70 AND ISNOTEMPTY(Work Email){
"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}}"
}
}
}
# 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 | 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 |
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.
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.
For AI-powered personalization and CRM sync, see clay-core-workflow-b.
npx skills add jeremylongshore/clay-core-workflow-a下载完整 Skill 目录,包含 SKILL.md 及所有相关文件
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer