sales-clay
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseClay Platform Help
Clay平台帮助
Help the user with Clay platform questions — from waterfall enrichment and Claygent AI agents through Sculptor workflows, Signals, Audiences, Ad Sync, Email Sequencer, CRM sync, and webhook/API integrations.
为用户解答Clay平台相关问题 — 覆盖Waterfall Enrichment、Claygent AI Agent、Sculptor工作流、Signals、受众管理、Ad Sync、邮件序列工具、CRM同步、webhook/API集成等全模块。
Step 1 — Gather context
步骤1 — 收集上下文
Ask the user:
-
What area of Clay do you need help with?
- A) Waterfall Enrichment — finding emails, phones, firmographics via 150+ providers
- B) Claygent — AI research agents for prospect research, web scraping, gated content
- C) Sculptor — building workflows with natural language, conditional logic, automation
- D) Signals — tracking job changes, promotions, funding, website visits
- E) Audiences — dynamic buyer segments from CRM + enrichment + signals
- F) Ad Sync — pushing audiences to LinkedIn, Meta, Google Ads
- G) Email Sequencer — native outbound email sequences
- H) CRM Sync — Salesforce, HubSpot, Dynamics 365 bidirectional sync
- I) Webhooks & HTTP API — inbound/outbound data flow, external API calls
- J) Data Credits & Billing — credit usage, plan optimization, provider costs
- K) Something else — describe it
-
What's your role?
- A) Sales rep / AE / BDR
- B) Sales manager / team lead
- C) RevOps / GTM Ops
- D) Marketing / Growth
- E) Founder / solo seller
- F) GTM Engineer
- G) Other
-
What are you trying to accomplish? (describe your specific goal or question)
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
向用户询问以下信息：
-
你需要Clay哪个模块的帮助？
- A) Waterfall Enrichment — 通过150+供应商查询邮箱、手机号、公司基本信息
- B) Claygent — 用于潜客调研、网页爬取、 gated内容获取的AI研究Agent
- C) Sculptor — 支持自然语言配置、条件逻辑、自动化能力的工作流构建工具
- D) Signals — 追踪职位变动、晋升、融资、网站访问等事件
- E) Audiences — 整合CRM数据、富集数据、信号数据生成的动态买家分群
- F) Ad Sync — 将受众群体同步到LinkedIn、Meta、Google Ads平台
- G) 邮件序列工具 — 原生外发邮件序列功能
- H) CRM Sync — 与Salesforce、HubSpot、Dynamics 365的双向同步
- I) Webhooks & HTTP API — 入站/出站数据流、外部API调用能力
- J) 数据积分与计费 — 积分消耗、套餐优化、供应商成本相关问题
- K) 其他内容 — 请描述具体问题
-
你的角色是什么？
- A) 销售代表/AE/BDR
- B) 销售经理/团队负责人
- C) RevOps/GTM Ops
- D) 营销/增长岗
- E) 创始人/独立销售
- F) GTM工程师
- G) 其他
-
你想要达成什么目标？（描述你的具体目标或问题）
**如果用户的请求已经提供了大部分上下文信息，可以直接跳转到对应的步骤。**先基于合理假设给出你能提供的最优答案（需明确说明假设内容），最后仅询问1-2个最关键的澄清问题 —— 不要等收集完所有信息才给出回复。
Step 2 — Route or answer directly
步骤2 — 流转或直接解答
If the request maps to a specialized skill, route:
- Enrichment strategy / provider comparison →
/sales-enrich - Cadence strategy / sequence design →
/sales-cadence - Intent signal strategy / prioritization →
/sales-intent - B2B advertising strategy →
/sales-b2b-advertising - CRM data hygiene strategy →
/sales-data-hygiene - Prospect list building strategy →
/sales-prospect-list - Lead scoring model design →
/sales-lead-score - Tool integration architecture →
/sales-integration
Otherwise, answer directly using the platform reference below.
如果用户的请求对应更专业的skill，请引导至对应入口：
- 富集策略/供应商对比 →
/sales-enrich - 触达节奏策略/序列设计 →
/sales-cadence - 意图信号策略/优先级排序 →
/sales-intent - B2B广告策略 →
/sales-b2b-advertising - CRM数据卫生策略 →
/sales-data-hygiene - 潜客名单搭建策略 →
/sales-prospect-list - 线索评分模型设计 →
/sales-lead-score - 工具集成架构 →
/sales-integration
否则，参考下方的平台说明直接给出答案。
Step 3 — Clay platform reference
步骤3 — Clay平台参考说明
Core concepts
核心概念
| Concept | What it is |
|---|---|
| Table | Spreadsheet-like workspace where you build enrichment + automation workflows. Each row = a person or company. |
| Waterfall Enrichment | Query multiple data providers in sequence — if Provider A misses, Provider B tries, then C, etc. Maximizes coverage. |
| Claygent | AI research agent that browses the web, searches databases, navigates gated content. Reusable and versionable. |
| Sculptor | Natural language workflow builder — describe what you want in plain English, Clay builds the automation with conditional logic. |
| Signals | Event triggers — job changes, promotions, funding rounds, website visits, company news. |
| Audiences | Dynamic segments combining first-party data (CRM) + third-party data (enrichment) + signals. |
| Ad Sync | Push Audiences to LinkedIn Ads, Meta Ads, Google Ads for targeted campaigns. |
| Email Sequencer | Native outbound email with multi-step sequences, triggers, and personalization. |
| Actions | Operations that run on rows — enrichments, AI research, HTTP calls, CRM writes. Consume Actions credits. |
| Data Credits | Currency for enrichment lookups. Different providers cost different amounts. Unused credits roll over up to 2x monthly allocation on paid plans. |
| Destinations | Where enriched data goes — CRM, data warehouse, email tools, webhooks, websites. |
| 概念 | 说明 |
|---|---|
| Table | 类电子表格的工作区，你可以在此搭建富集+自动化工作流。每一行对应一个联系人或企业。 |
| Waterfall Enrichment | 按顺序查询多个数据供应商 —— 如果供应商A没有返回数据，就尝试供应商B，再尝试C，以此类推，最大化数据覆盖率。 |
| Claygent | 可以浏览网页、搜索数据库、访问gated内容的AI研究Agent，支持复用和版本管理。 |
| Sculptor | 自然语言工作流构建器 —— 用日常英语描述你的需求，Clay会自动生成带条件逻辑的自动化流程。 |
| Signals | 事件触发器 —— 职位变动、晋升、融资轮次、网站访问、公司新闻等。 |
| Audiences | 整合第一方数据（CRM）+ 第三方数据（富集结果）+ 信号数据的动态分群。 |
| Ad Sync | 将受众群体推送到LinkedIn Ads、Meta Ads、Google Ads用于定向投放。 |
| 邮件序列工具 | 原生外发邮件功能，支持多步骤序列、触发规则和个性化配置。 |
| Actions | 运行在每行数据上的操作 —— 数据富集、AI研究、HTTP调用、CRM写入，会消耗Actions积分。 |
| Data Credits | 用于数据富集查询的货币，不同供应商的消耗额度不同。付费套餐中未使用的积分最多可以结转至月度配额的2倍。 |
| Destinations | 富集后数据的输出位置 —— CRM、数据仓库、邮件工具、webhooks、网站等。 |
Data model
数据模型
| Object | Key fields | Notes |
|---|---|---|
| Table | name, rows, columns, webhook URL | Each table has a unique webhook URL for inbound data |
| Row | All column values | Each row = one person/company being enriched |
| Column | name, type, enrichment source | Can be manual, enriched, computed, or AI-generated |
| Enrichment | provider, input fields, output fields, credits | 150+ providers available via waterfall |
| Claygent | prompt, instructions, version | Reusable AI agent — can browse web, extract data |
| Workflow (Sculptor) | natural language description, steps, conditions | Converted to executable automation |
| Signal | type (job change, funding, visit), trigger conditions | Fires when conditions match |
| Audience | segment rules, source data, sync destinations | Dynamic — updates as data changes |
| Sequence | steps, delays, conditions, sender | Email Sequencer outbound campaign |
| 对象 | 核心字段 | 说明 |
|---|---|---|
| Table | 名称、行、列、webhook URL | 每个表格都有唯一的webhook URL用于接收入站数据 |
| Row | 所有列的值 | 每一行对应一个正在被富集的联系人/企业 |
| Column | 名称、类型、富集来源 | 可以是手动填写、富集生成、计算生成或AI生成 |
| Enrichment | 供应商、输入字段、输出字段、积分消耗 | 串联150+供应商的Waterfall能力 |
| Claygent | 提示词、指令、版本 | 可复用的AI Agent —— 可以浏览网页、提取数据 |
| 工作流（Sculptor） | 自然语言描述、步骤、条件 | 会被转换为可执行的自动化流程 |
| Signal | 类型（职位变动、融资、访问）、触发条件 | 条件匹配时触发 |
| Audience | 分群规则、源数据、同步目的地 | 动态更新 —— 数据变化时分群自动更新 |
| Sequence | 步骤、延迟、条件、发件人 | 邮件序列工具的外发 campaign |
Waterfall enrichment — how it works
Waterfall Enrichment — 运行逻辑
- Add enrichment columns to your table (e.g., "Work Email", "Phone", "Company Revenue")
- Configure the waterfall — pick providers in priority order (e.g., Hunter → Dropcontact → Apollo → People Data Labs)
- Clay queries Provider 1 — if it returns data, done. If not, tries Provider 2, then 3, etc.
- Each provider hit costs Data Credits — different providers cost different amounts
- Coverage rates compound — if each provider covers 60%, a 3-provider waterfall might hit 85-95%
Key providers available: Hunter, Apollo, Clearbit/Breeze, People Data Labs, Dropcontact, ZoomInfo, Lusha, RocketReach, Snov.io, Cognism, LeadMagic, and 140+ more.
Best practices:
- Start with cheaper providers, escalate to expensive ones
- Use "only if empty" logic so you don't burn credits on already-enriched rows
- Monitor credit consumption per provider in table settings
- Test waterfall order on a small batch before running at scale
- 在表格中添加富集列（例如“工作邮箱”、“手机号”、“公司营收”）
- 配置Waterfall顺序 —— 按优先级选择供应商（例如Hunter → Dropcontact → Apollo → People Data Labs）
- Clay查询第一个供应商 —— 如果返回数据就结束，否则尝试第二个，再尝试第三个，以此类推
- 每次成功查询供应商都会消耗Data Credits —— 不同供应商的消耗额度不同
- 覆盖率叠加 —— 如果单个供应商覆盖率是60%，3个供应商的Waterfall覆盖率可以达到85-95%
可用的核心供应商：Hunter、Apollo、Clearbit/Breeze、People Data Labs、Dropcontact、ZoomInfo、Lusha、RocketReach、Snov.io、Cognism、LeadMagic等140+供应商。
最佳实践：
- 优先使用更便宜的供应商，再切换到贵的供应商
- 使用“仅为空时查询”逻辑，避免为已经有富集结果的行消耗积分
- 在表格设置中监控每个供应商的积分消耗情况
- 大规模运行前先在小批量数据上测试Waterfall顺序
Claygent — AI research agents
Claygent — AI研究Agent
- What it does: Browses the web, searches databases, extracts structured data from unstructured sources
- Use cases: Find company tech stack, extract pricing from websites, research competitor features, find decision-maker info from LinkedIn profiles, summarize 10-K filings
- MCP server support: Connect to Salesforce, Gong, Google Docs, Notion for data access
- Best practices: Write clear, specific instructions. Version your agents so you can roll back. Test on 5-10 rows before scaling.
- 能力：浏览网页、搜索数据库、从非结构化数据源提取结构化数据
- 使用场景：查询公司技术栈、提取网站定价信息、调研竞品功能、从LinkedIn profile获取决策人信息、摘要10-K filings
- MCP服务器支持：可以连接Salesforce、Gong、Google Docs、Notion获取数据
- 最佳实践：编写清晰具体的指令，为你的Agent做版本管理方便回滚，大规模运行前先在5-10行数据上测试。
Sculptor — workflow builder
Sculptor — 工作流构建器
- What it does: Describe workflows in natural language → Clay generates the automation
- Capabilities: Conditional logic (if/then), data transformation, multi-step enrichment chains, formatting
- Best practices: Start simple, add complexity incrementally. Review the generated logic before running at scale.
- 能力：用自然语言描述工作流 → Clay自动生成自动化流程
- 支持功能：条件逻辑（if/then）、数据转换、多步骤富集链路、格式处理
- 最佳实践：从简单流程开始，逐步增加复杂度，大规模运行前先检查生成的逻辑是否正确。
Signals
Signals
- Job changes: Track when prospects change roles, get promoted, or move companies
- Funding events: Trigger outreach when target companies raise rounds
- Website visits: Identify companies visiting your site (requires tracking setup)
- Company news: Monitor for acquisitions, product launches, expansions
- Plan gate: Signals require Launch plan or above
- 职位变动：追踪潜客换岗、晋升、换公司的事件
- 融资事件：目标公司完成融资时触发触达
- 网站访问：识别访问你网站的公司（需要配置追踪）
- 公司新闻：监控收购、产品发布、扩张等事件
- 套餐限制：Signals功能需要Launch及以上套餐
Audiences & Ad Sync
Audiences & Ad Sync
- Audiences: Combine CRM data + enrichment + signals into dynamic segments
- Ad Sync: Push audiences to LinkedIn Ads, Meta Ads, Google Ads
- Plan gate: Ad Sync requires Growth plan or above (1 audience included; Enterprise gets 2)
- Best practices: Use Audiences for ABM campaigns — enrich target accounts, build segments, sync to ad platforms for air cover alongside outbound
- Audiences：整合CRM数据+富集数据+信号数据生成动态分群
- Ad Sync：将受众群体推送到LinkedIn Ads、Meta Ads、Google Ads
- 套餐限制：Ad Sync需要Growth及以上套餐（包含1个受众名额；企业版包含2个）
- 最佳实践：将Audiences用于ABM campaign —— 富集目标账户、搭建分群、同步到广告平台，和外发触达形成配合。
Email Sequencer
邮件序列工具
- What it does: Multi-step outbound email sequences with personalization
- Features: A/B testing, send scheduling, reply detection, auto-pause on reply
- Available on: Free plan and above
- Best practices: Use Clay's enrichment to personalize every email. Combine with Signals to trigger sequences on job changes or funding events.
- 能力：支持个性化配置的多步骤外发邮件序列
- 功能：A/B测试、发送时间调度、回复检测、收到回复后自动暂停
- 可用套餐：免费版及以上都可以使用
- 最佳实践：使用Clay的富集结果为每封邮件做个性化配置，结合Signals功能在职位变动或融资事件发生时触发序列。
CRM Sync
CRM Sync
- Salesforce: Bidirectional sync — import leads/contacts/accounts for enrichment, push enriched data back. Create/update records automatically.
- HubSpot: Import contacts/companies, enrich in Clay, push back. Native marketplace app available.
- Dynamics 365: Create, update, and lookup records directly from Clay workflows.
- ActiveCampaign: Manage contacts and automations from Clay.
- Plan gate: CRM Sync requires Growth plan or above.
- Salesforce：双向同步 —— 导入线索/联系人/账户做富集，再将富集后的数据推回，自动创建/更新记录。
- HubSpot：导入联系人/公司，在Clay中富集后推回，有原生市场应用。
- Dynamics 365：可以直接在Clay工作流中创建、更新、查询记录。
- ActiveCampaign：从Clay管理联系人和自动化流程。
- 套餐限制：CRM Sync需要Growth及以上套餐。
Webhooks & HTTP API
Webhooks & HTTP API
- Inbound webhooks: Each table has a unique webhook URL. POST JSON to it → creates new rows. Use for triggering enrichment from external events (form submissions, Zapier, custom apps).
- HTTP API action: Call any external API from within a Clay table. Configure method (GET/POST/PUT/DELETE), headers, body, and field mapping. Use for pushing data to tools that don't have native integrations.
- Plan gate: HTTP API requires Growth plan or above.
- No traditional REST API: Clay doesn't expose a public REST API for querying/managing tables programmatically. Integration is webhook-based.
- Enterprise People & Company API: Lightweight lookup via email, LinkedIn URL, or domain. Available only on Enterprise plans.
- 入站webhooks：每个表格都有唯一的webhook URL，向其POST JSON数据 → 自动创建新行，用于从外部事件（表单提交、Zapier、自定义应用）触发富集流程。
- HTTP API操作：在Clay表格中调用任意外部API，支持配置请求方法（GET/POST/PUT/DELETE）、请求头、请求体和字段映射，用于向没有原生集成的工具推送数据。
- 套餐限制：HTTP API需要Growth及以上套餐。
- 无传统REST API：Clay没有提供公开的REST API用于程序化查询/管理表格，集成仅基于webhook实现。
- 企业版联系人和公司API：支持通过邮箱、LinkedIn URL、域名进行轻量级查询，仅企业版套餐可用。
Pricing & credits (as of March 2026 — verify current pricing)
定价与积分（2026年3月版本 —— 请核实当前最新定价）
| Plan | Price | Actions/mo | Data Credits/mo | Key features |
|---|---|---|---|---|
| Free | $0 | 500 | 100 | Unlimited seats/tables, waterfall, Claygent, Sequencer, 200 rows/table |
| Launch | $167-185/mo | 15,000 | 2,500 | Phone enrichment, Signals, 50K rows/table, email integrations |
| Growth | $446-495/mo | 40,000 | 6,000 | CRM sync, HTTP API, webhooks, web intent, Ad Sync (1 audience), priority support |
| Enterprise | Custom | Custom | Custom | Data warehouse sync, unlimited Audience rows, SSO/RBAC, Ad Sync (2 audiences), dedicated strategist |
- Unused credits roll over up to 2x monthly allocation on paid plans
- Additional credits available at ~30% premium
- Actions reset monthly (no rollover)
| 套餐 | 价格 | 月度Actions额度 | 月度Data Credits额度 | 核心功能 |
|---|---|---|---|---|
| 免费版 | $0 | 500 | 100 | 不限席位/表格、Waterfall、Claygent、邮件序列工具、单表200行上限 |
| Launch | $167-185/月 | 15,000 | 2,500 | 手机号富集、Signals、单表5万行上限、邮件集成 |
| Growth | $446-495/月 | 40,000 | 6,000 | CRM同步、HTTP API、webhooks、网页意图、Ad Sync（1个受众）、优先支持 |
| 企业版 | 定制 | 定制 | 定制 | 数据仓库同步、不限受众行数、SSO/RBAC、Ad Sync（2个受众）、专属策略顾问 |
- 付费套餐中未使用的积分最多可以结转至月度配额的2倍
- 额外购买积分有~30%的溢价
- Actions额度每月重置，不结转
Integrations
集成
Native CRM: Salesforce, HubSpot, Dynamics 365, ActiveCampaign, Pipedrive
Email/Outbound: Outreach, Salesloft, Apollo, Smartlead, Instantly, Lemlist, Reply.io
Data providers: 150+ via waterfall (Hunter, Clearbit, People Data Labs, ZoomInfo, Apollo, Lusha, Dropcontact, Cognism, RocketReach, etc.)
Advertising: LinkedIn Ads, Meta Ads, Google Ads (via Ad Sync)
Automation: Zapier, Make, HTTP API
Data warehouses: Snowflake, BigQuery (Enterprise)
Other: Slack, Google Sheets, Airtable, Notion
原生CRM：Salesforce、HubSpot、Dynamics 365、ActiveCampaign、Pipedrive
邮件/外发工具：Outreach、Salesloft、Apollo、Smartlead、Instantly、Lemlist、Reply.io
数据供应商：通过Waterfall支持150+（Hunter、Clearbit、People Data Labs、ZoomInfo、Apollo、Lusha、Dropcontact、Cognism、RocketReach等）
广告平台：LinkedIn Ads、Meta Ads、Google Ads（通过Ad Sync）
自动化工具：Zapier、Make、HTTP API
数据仓库：Snowflake、BigQuery（企业版）
其他：Slack、Google Sheets、Airtable、Notion
Step 4 — Actionable guidance
步骤4 — 可落地指导
When answering, always:
- Specify the plan requirement — many features are plan-gated. Don't recommend CRM Sync to a Free user.
- Include credit impact — waterfall enrichment burns credits fast. Help users optimize provider order and "only if empty" logic.
- Recommend testing at small scale — always test on 5-50 rows before running enrichment or Claygent on thousands.
- Link to Clay University — point users to university.clay.com for detailed guides on specific features.
- Consider the full workflow — Clay is most powerful when enrichment → signals → sequencing → CRM sync work together. Help users build end-to-end workflows, not isolated steps.
给出答案时请始终遵循以下要求：
- 明确说明套餐要求 —— 很多功能有套餐限制，不要向免费版用户推荐CRM Sync功能。
- 说明积分消耗影响 —— Waterfall Enrichment的积分消耗很快，帮助用户优化供应商顺序和“仅为空时查询”逻辑。
- 推荐小范围测试 —— 对数千行数据运行富集或Claygent任务前，务必先在5-50行数据上测试。
- 引导到Clay University —— 指向university.clay.com获取特定功能的详细指南。
- 考虑全工作流链路 —— 当富集→信号→序列→CRM同步配合使用时Clay的能力最强，帮助用户搭建端到端工作流，而不是孤立的步骤。
Gotchas
注意事项
Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
-
Credit burn from waterfall enrichment is the #1 surprise cost. Each provider in a waterfall consumes credits independently. A 5-provider waterfall on 10,000 rows can burn 50,000 credits if you're not using "only if empty" logic. Always test on small batches and monitor credit usage in table settings.
-
No public REST API — webhook-only integration model. Clay doesn't expose traditional API endpoints for managing tables or data programmatically. All external integration is via inbound webhooks (POST to table URL) and outbound HTTP API actions. This surprises developers expecting a standard CRUD API.
-
CRM Sync requires Growth plan ($446+/mo). Many users sign up for Launch expecting to sync with Salesforce/HubSpot, then discover CRM sync is plan-gated. Same for HTTP API and webhooks — all require Growth.
-
Claygent results vary with prompt quality. AI research agents are powerful but sensitive to instruction quality. Vague prompts produce inconsistent results. Always write specific, structured instructions and test on 5-10 rows before scaling.
-
Data credit costs vary by provider — not all enrichments cost the same. A Hunter email lookup might cost 1 credit while a ZoomInfo enrichment costs 10+. The waterfall order matters for cost optimization, not just coverage.
基于调研整理的最佳实践 —— 请仔细核对，尤其是套餐限制和集成相关的内容可能已经过时。
-
Waterfall Enrichment的积分消耗是最常见的超支原因。 Waterfall中的每个供应商都会单独消耗积分，如果没有使用“仅为空时查询”逻辑，对1万行数据运行5个供应商的Waterfall可能消耗5万积分。始终先在小批量数据上测试，在表格设置中监控积分使用情况。
-
无公开REST API —— 仅支持webhook集成模式。 Clay没有提供传统的API端点用于程序化管理表格或数据，所有外部集成都通过入站webhooks（POST到表格URL）和出站HTTP API操作实现，这一点会让期望标准CRUD API的开发者感到意外。
-
CRM Sync需要Growth套餐（$446+/月）。 很多用户购买Launch套餐后希望同步Salesforce/HubSpot，才发现CRM同步有套餐限制。HTTP API和webhooks也是一样，都需要Growth套餐。
-
Claygent的结果质量和提示词质量高度相关。 AI研究Agent能力很强，但对指令质量很敏感，模糊的提示词会得到不一致的结果。始终编写具体、结构化的指令，大规模运行前先在5-10行数据上测试。
-
不同供应商的Data Credits成本不同 —— 不是所有富集的成本都一样。 Hunter的邮箱查询可能消耗1积分，而ZoomInfo的富集可能消耗10积分，Waterfall的顺序不仅影响覆盖率，也影响成本优化。
Step 5 — Related skills
步骤5 — 相关skills
- — Enrichment strategy across all tools (for choosing providers, comparing approaches)
/sales-enrich - — Multi-channel outbound sequence design (for cadence strategy beyond Clay's sequencer)
/sales-cadence - — Buying signals and account prioritization (for signal strategy beyond Clay's Signals)
/sales-intent - — Building targeted prospect lists (for list strategy)
/sales-prospect-list - — Lead scoring models (for scoring strategy using Clay's enrichment data)
/sales-lead-score - — B2B advertising strategy (for ad strategy beyond Clay's Ad Sync)
/sales-b2b-advertising - — CRM data hygiene (for data quality strategy using Clay's CRM sync)
/sales-data-hygiene - — Connecting tools with webhooks, Zapier, APIs
/sales-integration - — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
/sales-donpx skills add sales-skills/sales --skills sales-do
- —— 跨工具的富集策略（用于选择供应商、对比不同方案）
/sales-enrich - —— 多渠道外发序列设计（用于Clay邮件序列之外的触达节奏策略）
/sales-cadence - —— 购买信号和账户优先级排序（用于Clay Signals之外的信号策略）
/sales-intent - —— 搭建定向潜客名单（用于名单策略）
/sales-prospect-list - —— 线索评分模型（用于使用Clay富集数据的评分策略）
/sales-lead-score - —— B2B广告策略（用于Clay Ad Sync之外的广告策略）
/sales-b2b-advertising - —— CRM数据卫生（用于使用Clay CRM同步的数据质量策略）
/sales-data-hygiene - —— 通过webhooks、Zapier、API连接工具
/sales-integration - —— 不知道用哪个skill？路由工具会将任意销售目标匹配到正确的skill。安装命令：
/sales-donpx skills add sales-skills/sales --skills sales-do
Examples
示例
Example 1: Setting up waterfall enrichment for work emails
示例1：搭建工作邮箱的Waterfall Enrichment流程
User says: "I have a list of 5,000 leads with names and companies but no emails. How do I find their work emails in Clay?"
Skill does: Recommends waterfall enrichment with provider order (Hunter → Dropcontact → Apollo → People Data Labs), "only if empty" logic between steps, small batch test first (50 rows), and credit budget estimate.
Result: Step-by-step waterfall setup with provider prioritization and cost optimization.
用户提问：“我有一份5000条线索的名单，有姓名和公司，但没有邮箱，怎么在Clay里找到他们的工作邮箱？”
Skill处理逻辑：推荐用（Hunter → Dropcontact → Apollo → People Data Labs）的供应商顺序搭建Waterfall Enrichment，步骤之间配置“仅为空时查询”逻辑，先做小批量测试（50行），给出积分预算估算。
结果：包含供应商优先级和成本优化的Waterfall搭建分步指南。
Example 2: Building an intent-triggered outbound workflow
示例2：搭建意图触发的外发工作流
User says: "I want to automatically enrich and email prospects when they change jobs at target accounts."
Skill does: Walks through Signals setup (job change trigger), enrichment waterfall for new role details, Claygent for company research, Email Sequencer for personalized outreach, and CRM sync to log activity. Notes Launch plan minimum for Signals.
Result: End-to-end automated workflow from signal detection through outbound.
用户提问：“我想要在目标账户的潜客换工作时，自动富集他们的信息并发送邮件。”
Skill处理逻辑：一步步讲解Signals配置（职位变动触发器）、获取新职位信息的富集Waterfall、公司调研用的Claygent、个性化触达的邮件序列工具、记录活动的CRM同步，说明最低需要Launch套餐才能使用Signals。
结果：从信号检测到外发触达的端到端自动化工作流。
Example 3: Clay vs Apollo for enrichment
示例3：Clay和Apollo的富集能力对比
User says: "Should I use Clay or Apollo for contact enrichment? We already have Apollo."
Skill does: Explains Clay's waterfall approach (150+ providers, higher coverage) vs Apollo's single-database model (275M+ contacts, simpler). Notes Clay as an enrichment orchestrator that can include Apollo as one provider. Recommends Clay for teams needing maximum coverage; Apollo alone for teams prioritizing simplicity and built-in outbound.
Result: Clear comparison with recommendation based on team needs.
用户提问：“我应该用Clay还是Apollo做联系人富集？我们已经有Apollo了。”
Skill处理逻辑：说明Clay的Waterfall模式（150+供应商，覆盖率更高）和Apollo的单数据库模式（2.75亿+联系人，更简单）的差异，说明Clay是富集编排工具，可以把Apollo作为其中一个供应商使用。推荐需要最大化覆盖率的团队使用Clay，优先考虑简单性和原生外发能力的团队可以只用Apollo。
结果：基于团队需求的清晰对比和推荐。
Troubleshooting
问题排查
Waterfall enrichment returning low match rates
Waterfall Enrichment匹配率低
Symptom: Running waterfall enrichment but only getting 30-40% email coverage.
Cause: Provider order may not be optimized, or input data quality is poor (misspelled company names, outdated titles).
Solution: Clean input data first — standardize company names and verify LinkedIn URLs. Reorder providers with highest-coverage providers first. Add more providers to the waterfall (5-7 is typical for 80%+ coverage). Check that "only if empty" logic is working correctly between providers. Test with a small batch to identify which providers perform best for your ICP.
症状：运行Waterfall Enrichment后仅获得30-40%的邮箱覆盖率。
原因：供应商顺序可能没有优化，或者输入数据质量差（公司名拼写错误、职位过时）。
解决方案：先清理输入数据 —— 标准化公司名称、核实LinkedIn URL。调整供应商顺序，把覆盖率最高的供应商放在前面。在Waterfall中添加更多供应商（通常5-7个供应商可以达到80%+的覆盖率）。检查供应商之间的“仅为空时查询”逻辑是否正常运行。用小批量数据测试，找到对你的ICP效果最好的供应商。
Credits running out faster than expected
积分消耗比预期快
Symptom: Data Credits depleted before the monthly cycle ends.
Cause: Waterfall enrichment without "only if empty" logic queries every provider for every row, even if the first one succeeds. Multi-column enrichment compounds costs (email + phone + company = 3x credits per row).
Solution: Add "only if empty" conditions between waterfall steps. Prioritize cheaper providers first. Run enrichment on high-priority segments rather than entire database. Monitor per-provider credit consumption in table settings. Consider upgrading plan for more credits if the ROI justifies it.
症状：Data Credits在月度周期结束前就用完了。
原因：没有配置“仅为空时查询”逻辑的Waterfall会为每一行数据查询所有供应商，哪怕第一个供应商已经返回了结果。多列富集也会叠加成本（邮箱+手机号+公司信息=每行消耗3倍积分）。
解决方案：在Waterfall步骤之间添加“仅为空时查询”条件，优先使用更便宜的供应商，只对高优先级分群运行富集而不是全数据库，在表格设置中监控每个供应商的积分消耗，如果ROI达标可以考虑升级套餐获取更多积分。
CRM sync not working
CRM同步不工作
Symptom: Enriched data isn't syncing back to Salesforce/HubSpot.
Cause: CRM sync requires Growth plan ($446+/mo). Also, field mapping must be configured correctly — Clay column names must map to CRM field API names, not display labels.
Solution: Verify you're on Growth plan or above. Check field mapping in the CRM integration settings — use API field names (e.g., not "Email Address"). Test sync with a single row before bulk operations. Check CRM-side permissions — the connected user needs create/update access on the target object.
Email症状：富集后的数据没有同步回Salesforce/HubSpot。
原因：CRM同步需要Growth套餐（$446+/月），另外字段映射可能配置错误 —— Clay的列名需要映射到CRM的字段API名称，而不是显示标签。
解决方案：核实你使用的是Growth及以上套餐，检查CRM集成设置中的字段映射 —— 使用API字段名（例如而不是“邮箱地址”），批量操作前先测试单行同步，检查CRM端的权限 —— 连接的用户需要有目标对象的创建/更新权限。
Email