Back to Details

sales-tomba

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Tomba Platform Help

Tomba平台使用帮助

Help the user with Tomba.io platform questions — from domain search and email finding through verification, enrichment, bulk operations, API, and integrations.
为用户解答Tomba.io平台相关问题——从域名搜索、邮箱查找，到邮箱验证、联系人信息补全、批量操作、API及集成功能等。

Step 1 — Gather context

步骤1 — 收集上下文信息

Ask the user:
  1. What area of Tomba do you need help with?
    • A) Domain Search — finding all emails at a company
    • B) Email Finder — finding a specific person's email
    • C) Email Verifier — validating email addresses
    • D) Email Enrichment — enriching contacts with company/social data
    • E) Author Finder — finding blog author emails
    • F) LinkedIn Finder — finding emails from LinkedIn profiles
    • G) Phone Finder — finding phone numbers
    • H) Bulk Operations — processing thousands of records at once
    • I) Leads & Lists — managing saved contacts and lists
    • J) Browser Extension — Chrome/Edge/Safari/Firefox extension
    • K) Google Sheets / Excel — add-on or add-in
    • L) API — programmatic access, automation, custom integration
    • M) Integrations — Zapier, HubSpot, Salesforce, Pipedrive, Make, n8n
    • N) Account & Billing — plans, credits, team members
    • O) Something else — describe it
  2. What's your role?
    • A) Sales rep / AE / BDR
    • B) Sales manager / team lead
    • C) RevOps / Sales Ops
    • D) Recruiter
    • E) Marketing
    • F) Founder / solo seller
    • G) Developer / engineering
    • H) Other
  3. 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.
Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.
询问用户：
  1. 你需要Tomba哪方面的帮助？
    • A) 域名搜索——查找某公司的所有邮箱
    • B) 邮箱查找工具——查找特定人员的邮箱
    • C) 邮箱验证工具——验证邮箱地址的有效性
    • D) 联系人信息补全——为联系人补充公司/社交数据
    • E) 作者邮箱查找——查找博客作者的邮箱
    • F) LinkedIn邮箱提取——从LinkedIn个人资料中提取邮箱
    • G) 电话号码查找——查找电话号码
    • H) 批量操作——一次性处理数千条记录
    • I) 线索与联系人列表——管理已保存的联系人和列表
    • J) 浏览器扩展——Chrome/Edge/Safari/Firefox扩展程序
    • K) Google Sheets / Excel——插件或加载项
    • L) API——程序化访问、自动化、自定义集成
    • M) 集成功能——Zapier、HubSpot、Salesforce、Pipedrive、Make、n8n
    • N) 账户与账单——套餐、积分、团队成员
    • O) 其他——请描述具体需求
  2. 你的角色是什么？
    • A) 销售代表 / AE / BDR
    • B) 销售经理 / 团队主管
    • C) 营收运营 / 销售运营
    • D) 招聘人员
    • E) 营销人员
    • F) 创始人 / 独立销售者
    • G) 开发人员 / 工程师
    • H) 其他
  3. 你想要达成什么目标？（描述你的具体目标或问题）
如果用户的请求已经提供了大部分上下文信息，可直接跳至相关步骤。 先基于合理假设给出最佳解答（需明确说明假设），最后仅询问1-2个最关键的澄清问题——不要要求用户提供完整上下文后才给出回复。
注意：如果用户需要特定领域的专业技能，引导他们使用对应的技能并简要说明原因。

Step 2 — Route or answer directly

步骤2 — 引导至对应技能或直接解答

If the request maps to a specialized skill, route:
  • Enrichment strategy across tools → 
    /sales-enrich
  • Building prospect lists / ICP definition → 
    /sales-prospect-list
  • Email deliverability / SPF/DKIM/DMARC → 
    /sales-deliverability
  • Buying signals and prioritization → 
    /sales-intent
  • Connecting tools via Zapier/webhooks → 
    /sales-integration
Otherwise, answer directly from platform knowledge using the reference below.
如果用户的请求对应某个专业技能，进行引导：
  • 跨工具的信息补全策略 → 
    /sales-enrich
  • 构建潜在客户列表 / 理想客户画像定义 → 
    /sales-prospect-list
  • 邮箱送达率 / SPF/DKIM/DMARC设置 → 
    /sales-deliverability
  • 购买信号识别与优先级排序 → 
    /sales-intent
  • 通过Zapier/webhooks连接工具 → 
    /sales-integration
否则，直接基于平台知识库给出解答。

Step 3 — Tomba platform reference

步骤3 — Tomba平台参考指南

Provide module-by-module guidance based on the user's area:
根据用户的需求领域，提供分模块的指导：

Domain Search

域名搜索

  • What it is: Enter a domain (e.g., 
    stripe.com
    ) and Tomba returns all known email addresses at that organization, along with names, titles, departments, social links, and confidence scores
  • Key filters: Department (engineering, sales, marketing, hr, finance, etc.), seniority (junior, senior, executive), country, technology stack
  • Pagination: Results paginated with 
    page
    and 
    limit
    (10, 20, or 50 per page)
  • Email pattern detection: Tomba identifies the email format a company uses (e.g., 
    first.last@
    , 
    firstinitial+last@
    ) — use the Email Format endpoint to check this before guessing
  • Organization data included: Company size, revenue, industry, social links, tech stack, founding year, location
  • Best practices: Use department and seniority filters to narrow results to decision-makers. Export results to a lead list for campaign use.
  • 功能介绍：输入一个域名（例如
    stripe.com
    ），Tomba会返回该机构下所有已知的邮箱地址，以及对应的姓名、职位、部门、社交链接和置信度评分
  • 关键筛选条件：部门（工程、销售、营销、人力资源、财务等）、职级（初级、高级、高管）、国家、技术栈
  • 分页设置：结果通过
    page
    和
    limit
    参数分页（每页10、20或50条结果）
  • 邮箱格式检测：Tomba会识别公司使用的邮箱格式（例如
    first.last@
    、
    firstinitial+last@
    ）——在猜测邮箱前，可使用邮箱格式端点进行查询
  • 包含的企业数据：公司规模、收入、行业、社交链接、技术栈、成立年份、地理位置
  • 最佳实践：使用部门和职级筛选条件，将结果缩小至决策人员。将结果导出至线索列表，用于营销活动。

Email Finder

邮箱查找工具

  • What it is: Provide a person's name + company domain, and Tomba returns their most likely email address with a confidence score
  • Required inputs: Domain + full name (or first name + last name)
  • Output: Email address, confidence score (0-100), verification status, sources
  • Best practices: Always verify the found email with the Email Verifier before sending. Higher confidence scores (90+) are more reliable.
  • 功能介绍：提供人员姓名+公司域名，Tomba会返回其最可能的邮箱地址及置信度评分
  • 必填输入：域名+全名（或名+姓）
  • 输出内容：邮箱地址、置信度评分（0-100）、验证状态、数据来源
  • 最佳实践：在发送邮件前，务必使用邮箱验证工具对找到的邮箱进行验证。置信度评分90分以上的结果更可靠。

Email Verifier

邮箱验证工具

  • What it is: Real-time SMTP/MX validation — checks whether an email address is deliverable
  • Validation checks: Format validation, MX record check, SMTP verification, catch-all detection, disposable email detection
  • Verification statuses: valid, invalid, accept_all (catch-all domain), unknown
  • Speed: Results in under 1 second for most emails
  • Best practices: Always verify emails before outbound campaigns to keep bounce rate <3%. Batch verify lists before importing into campaign tools. Be cautious with "accept_all" — these domains accept everything but may still bounce.
  • 功能介绍：实时SMTP/MX验证——检查邮箱地址是否可送达
  • 验证检查项：格式验证、MX记录检查、SMTP验证、 catch-all检测、临时邮箱检测
  • 验证状态：valid（有效）、invalid（无效）、accept_all（catch-all域名）、unknown（未知）
  • 速度：大多数邮箱的验证结果可在1秒内返回
  • 最佳实践：在开展外呼营销活动前，务必验证所有邮箱，将退信率控制在3%以下。在导入营销工具前，批量验证联系人列表。对于“accept_all”状态需谨慎——这些域名会接收所有邮件，但仍可能出现退信。

Email Enrichment

联系人信息补全

  • What it is: Provide an email address and get back person + company data — name, title, company, social handles, location, and more
  • Output fields: Full name, job title, company name, industry, social profiles (LinkedIn, Twitter), location, phone (if available)
  • Use case: Enrich inbound leads, fill in missing CRM fields, segment contacts by firmographic data
  • Best practices: Use enrichment to fill gaps in CRM records before outbound. Combine with domain search for full account coverage.
  • 功能介绍：提供邮箱地址，获取对应的个人+企业数据——姓名、职位、公司、社交账号、地理位置等
  • 输出字段：全名、职位、公司名称、社交账号（LinkedIn、Twitter）、地理位置、电话号码（若有）
  • 使用场景：补全入站线索的信息、填充CRM中缺失的字段、根据企业特征对联系人进行细分
  • 最佳实践：在开展外呼活动前，使用信息补全功能填充CRM记录中的空白。结合域名搜索功能，获取完整的企业联系人信息。

Author Finder

作者邮箱查找

  • What it is: Provide an article/blog URL and Tomba returns the author's email and profile data
  • Use case: PR outreach, journalist contact, content marketing partnerships
  • Best practices: Great for reaching out to blog authors, journalists, or content creators. Verify the email before sending.
  • 功能介绍：提供文章/博客URL，Tomba会返回作者的邮箱及个人资料数据
  • 使用场景：公关拓展、记者联系、内容营销合作
  • 最佳实践：非常适合联系博客作者、记者或内容创作者。发送邮件前务必验证邮箱。

LinkedIn Finder

LinkedIn邮箱提取

  • What it is: Provide a LinkedIn profile URL and Tomba returns the associated professional email
  • Options: 
    full=true
    returns all associated emails, not just the primary one
  • Use case: Sales prospecting from LinkedIn, recruiter outreach
  • Best practices: Use the browser extension to find emails while browsing LinkedIn. Combine with enrichment for full contact profiles.
  • 功能介绍：提供LinkedIn个人资料URL，Tomba会返回对应的工作邮箱
  • 可选参数：
    full=true
    会返回所有关联的邮箱，而非仅主邮箱
  • 使用场景：从LinkedIn挖掘销售线索、招聘人员拓展
  • 最佳实践：使用浏览器扩展程序，在浏览LinkedIn时直接查找邮箱。结合信息补全功能，获取完整的联系人资料。

Phone Finder

电话号码查找

  • What it is: Discover direct dial and mobile phone numbers for contacts
  • Access: Available as an option on domain search and finder endpoints (
    enrich_mobile=true
    )
  • Best practices: Phone numbers cost more credits than email lookups. Only request phone data for contacts you plan to call.
  • 功能介绍：查找联系人的直拨电话和手机号码
  • 访问方式：作为域名搜索和查找工具端点的可选参数（
    enrich_mobile=true
    ）
  • 最佳实践：电话号码查询消耗的积分比邮箱查询更多。仅为计划致电的联系人请求电话号码数据。

Bulk Operations

批量操作

  • What it is: Process thousands of records at once — bulk email finder, bulk verifier, bulk domain search, bulk LinkedIn finder, bulk enrichment, bulk phone finder
  • Scale: Up to 10,000 records per batch
  • Async processing: Bulk jobs run in background. Use 
    webhook_url
    parameter to get notified when complete.
  • Best practices: Verify your input list format before bulk upload. Use webhook callbacks instead of polling for completion. Start with a small test batch (50-100) to validate results before processing the full list.
  • 功能介绍：一次性处理数千条记录——批量邮箱查找、批量验证、批量域名搜索、批量LinkedIn邮箱提取、批量信息补全、批量电话号码查找
  • 处理规模：每批最多支持10,000条记录
  • 异步处理：批量任务在后台运行。使用
    webhook_url
    参数接收任务完成通知。
  • 最佳实践：批量上传前，验证输入列表的格式。使用webhook回调而非轮询来获取任务完成状态。先处理一个小的测试批次（50-100条）验证结果，再处理完整列表。

Leads & Lead Lists

线索与联系人列表

  • What it is: Save, organize, and manage contacts discovered through Tomba's search tools
  • Features: Create lists, add contacts from any search, filter and export
  • Use case: Build targeted campaign lists, organize contacts by account or campaign
  • Best practices: Create separate lists per campaign or persona. Export to CRM or campaign tool when ready for outreach.
  • 功能介绍：保存、整理和管理通过Tomba搜索工具发现的联系人
  • 功能特性：创建列表、从任意搜索结果添加联系人、筛选和导出
  • 使用场景：构建目标营销活动列表、按企业或营销活动整理联系人
  • 最佳实践：为每个营销活动或用户角色创建单独的列表。准备好拓展时，导出至CRM或营销工具。

Browser Extensions

浏览器扩展程序

  • Available for: Chrome, Edge, Safari, Firefox
  • Features: Find emails while browsing any website, LinkedIn integration, domain search from any page
  • Best practices: Pin the extension for quick access. Use on company "About" pages, LinkedIn profiles, and blog author pages for fastest results.
  • 支持浏览器：Chrome、Edge、Safari、Firefox
  • 功能特性：浏览任意网站时查找邮箱、LinkedIn集成、从任意页面进行域名搜索
  • 最佳实践：将扩展程序固定到浏览器工具栏，方便快速访问。在公司“关于我们”页面、LinkedIn个人资料页和博客作者页面使用，可获得最快的结果。

Google Sheets & Excel

Google Sheets & Excel

  • Google Sheets add-on: Run domain search, email finder, and verifier directly in your spreadsheet
  • Excel add-in: Same capabilities in Microsoft Excel
  • Best practices: Great for enriching an existing spreadsheet of companies or contacts without leaving the spreadsheet. Use for batch processing when you don't need the full API.
  • Google Sheets插件：在电子表格中直接运行域名搜索、邮箱查找和验证功能
  • Excel加载项：在Microsoft Excel中提供相同功能
  • 最佳实践：非常适合在不离开电子表格的情况下，补全现有公司或联系人列表的信息。当不需要完整API功能时，可用于批量处理。

Data Model

数据模型

EntityKey fieldsNotes
Email resultemail, first_name, last_name, full_name, gender, phone_number, type, country, position, department, seniority, twitter, linkedin, score, verification, sourcesCore output from domain search and finder
Organizationwebsite_url, organization, location, social_links, industries, founded, company_size, company_type, revenue, description, pattern, keywordsReturned alongside domain search results
Verificationemail, status (valid/invalid/accept_all/unknown), is_disposable, is_webmailOutput from verifier
Enrichmentemail, first_name, last_name, position, company, social profiles, location, phoneOutput from enrichment endpoint
Email formatformat, percentagePattern used by a domain (e.g., first.last@ at 85%)
实体关键字段说明
Email resultemail, first_name, last_name, full_name, gender, phone_number, type, country, position, department, seniority, twitter, linkedin, score, verification, sources域名搜索和查找工具的核心输出
Organizationwebsite_url, organization, location, social_links, industries, founded, company_size, company_type, revenue, description, pattern, keywords域名搜索结果附带的企业数据
Verificationemail, status (valid/invalid/accept_all/unknown), is_disposable, is_webmail邮箱验证工具的输出
Enrichmentemail, first_name, last_name, position, company, social profiles, location, phone信息补全端点的输出
Email formatformat, percentage域名使用的邮箱格式（例如
first.last@
占85%）

API Quick Reference

API快速参考

EndpointMethodPathWhat it does
Domain SearchGET
/v1/domain-search
Find all emails at a domain
Email FinderGET
/v1/email-finder
Find a specific person's email
Email VerifierGET
/v1/verifier
Validate an email address
Email EnrichmentGET
/v1/enrich
Enrich an email with person/company data
Author FinderGET
/v1/author-finder
Find article author's email
LinkedIn FinderGET
/v1/linkedin
Find email from LinkedIn URL
Phone FinderGET
/v1/phone-finder
Find phone numbers
Email CountGET
/v1/email-count
Count emails at a domain by department/seniority
Email FormatGET
/v1/email-format
Get email patterns used at a domain
Email SourcesGET
/v1/email-sources
Find where an email appears on the web
Domain StatusGET
/v1/domain-status
Check if domain is webmail/disposable
Similar DomainsGET
/v1/similar
Find similar/competitor domains
TechnologyGET
/v1/technology
Detect tech stack of a domain
Base URL: 
https://api.tomba.io/v1/
Auth: 
X-Tomba-Key
+ 
X-Tomba-Secret
headers Rate limits: 429 returned when exceeded (specific thresholds vary by plan) SDKs: JavaScript, Python, PHP, Ruby, Go, Rust, C#, Dart, Elixir, Lua, Perl, R (13+ official libraries) Full reference: See 
references/tomba-api-reference.md
端点请求方法路径功能
Domain SearchGET
/v1/domain-search
查找某域名下的所有邮箱
Email FinderGET
/v1/email-finder
查找特定人员的邮箱
Email VerifierGET
/v1/verifier
验证邮箱地址的有效性
Email EnrichmentGET
/v1/enrich
为邮箱补充个人/企业数据
Author FinderGET
/v1/author-finder
查找文章作者的邮箱
LinkedIn FinderGET
/v1/linkedin
从LinkedIn URL提取邮箱
Phone FinderGET
/v1/phone-finder
查找电话号码
Email CountGET
/v1/email-count
按部门/职级统计某域名下的邮箱数量
Email FormatGET
/v1/email-format
获取某域名使用的邮箱格式
Email SourcesGET
/v1/email-sources
查找邮箱在网络上的来源
Domain StatusGET
/v1/domain-status
检查域名是否为网页邮箱/临时邮箱
Similar DomainsGET
/v1/similar
查找相似/竞争域名
TechnologyGET
/v1/technology
检测某域名的技术栈
基础URL：
https://api.tomba.io/v1/
认证方式：
X-Tomba-Key
+ 
X-Tomba-Secret
请求头 速率限制：超出限制时返回429错误（具体阈值因套餐而异） SDK：JavaScript、Python、PHP、Ruby、Go、Rust、C#、Dart、Elixir、Lua、Perl、R（13+官方库） 完整参考：查看
references/tomba-api-reference.md

Integrations

集成功能

IntegrationTypeWhat it does
SalesforceCRMSync discovered contacts to Salesforce
HubSpotCRMDirect email integration, enrich CRM records
PipedriveCRMSync findings to Pipedrive contacts
ZapierAutomation8,000+ app connections — trigger on domain search, email find, enrichment
MakeAutomationVisual automation workflows with Tomba actions
n8nAutomationSelf-hosted automation with Tomba nodes
PabblyAutomationWorkflow automation integration
IntegratelyAutomationSimple integration automation
PipedreamAutomationDeveloper-focused workflow automation
Google SheetsProductivityAdd-on for in-spreadsheet email finding and verification
ExcelProductivityAdd-in for desktop spreadsheet workflows
AirtableProductivityOrganize contact data in Airtable
MCPAIModel Context Protocol server (local + remote) for AI agent integration
集成工具类型功能
SalesforceCRM将发现的联系人同步至Salesforce
HubSpotCRM直接邮箱集成，补全CRM记录
PipedriveCRM将结果同步至Pipedrive联系人
Zapier自动化工具支持8000+应用连接——可触发域名搜索、邮箱查找、信息补全等操作
Make自动化工具通过可视化工作流实现Tomba操作自动化
n8n自动化工具自托管式自动化，支持Tomba节点
Pabbly自动化工具工作流自动化集成
Integrately自动化工具简单的集成自动化
Pipedream自动化工具面向开发者的工作流自动化
Google Sheets生产力工具电子表格插件，可直接在其中查找和验证邮箱
Excel生产力工具桌面电子表格加载项
Airtable生产力工具在Airtable中整理联系人数据
MCPAI工具模型上下文协议服务器（本地+远程），用于AI Agent集成

Pricing (as of March 2026 — verify current pricing)

定价（截至2026年3月——请以当前定价为准）

PlanPrice/moSearchesVerificationsNotes
Free$02550Basic access, no credit card required
Starter$391,0002,000API access, bulk operations, browser extension
Growth$895,00010,000Expanded quotas, team sharing
Pro$18920,00040,000Webhooks, full domain search results, downloads
Enterprise$38950,000100,000Maximum tier, custom plans available above this
All paid plans include API access, bulk operations, browser extensions, and team member invitations.
套餐每月价格搜索次数验证次数说明
Free$02550基础访问权限，无需信用卡
Starter$391,0002,000API访问、批量操作、浏览器扩展
Growth$895,00010,000更高的配额、团队共享功能
Pro$18920,00040,000Webhook、完整域名搜索结果下载、导出功能
Enterprise$38950,000100,000最高等级套餐，支持自定义套餐
所有付费套餐均包含API访问、批量操作、浏览器扩展和团队成员邀请功能。

Step 4 — Actionable guidance

步骤4 — 可执行指导

Based on the user's specific question, provide:
  1. Step-by-step instructions with exact UI navigation or API calls
  2. Configuration recommendations with specific values (e.g., "set limit to 50 for faster pagination")
  3. Common pitfalls for the specific workflow
  4. Verification steps — how to confirm it's working correctly
根据用户的具体问题，提供：
  1. 分步操作说明，包含精确的UI导航或API调用示例
  2. 配置建议，包含具体参数值（例如“将limit设置为50以加快分页速度”）
  3. 常见陷阱，针对特定工作流
  4. 验证步骤——如何确认操作已成功完成

Common workflows

常见工作流

Find all contacts at a target company:
  1. Domain Search with the company's domain → get all known emails
  2. Filter by department (sales, engineering) and seniority (director+)
  3. Verify the emails you plan to contact
  4. Save to a lead list → export to CRM or campaign tool
Find a specific person's email:
  1. Email Finder with their name + company domain → get the email + confidence score
  2. If confidence <80%, check Email Format for the domain to validate the pattern
  3. Verify the email with Email Verifier before sending
  4. Enrich the contact for additional context (title, social profiles)
Clean an existing list before a campaign:
  1. Bulk verify all emails → separate into valid, invalid, accept_all
  2. Remove invalid emails immediately
  3. For accept_all: include but monitor bounce rates closely
  4. Enrich missing fields (names, titles) for personalization
  5. Export clean, enriched list to your campaign tool
Monitor competitor tech stack:
  1. Technology endpoint → see what tools a company uses
  2. Similar Domains → find competitor/adjacent companies
  3. Combine with domain search to find the right contacts
  4. Use for technographic-based outreach → see 
    /sales-intent
查找目标公司的所有联系人：
  1. 使用域名搜索功能，输入公司域名 → 获取所有已知邮箱
  2. 按部门（销售、工程）和职级（总监及以上）筛选结果
  3. 验证计划联系的邮箱
  4. 保存至线索列表 → 导出至CRM或营销工具
查找特定人员的邮箱：
  1. 使用邮箱查找工具，输入其姓名+公司域名 → 获取邮箱+置信度评分
  2. 若置信度<80%，查询该域名的邮箱格式以验证模式
  3. 使用邮箱验证工具验证邮箱后再发送邮件
  4. 为联系人补充信息，获取更多上下文（职位、社交资料）
营销活动前清理现有列表：
  1. 批量验证所有邮箱 → 分为有效、无效、accept_all三类
  2. 立即移除无效邮箱
  3. 对于accept_all类：可保留但需密切监控退信率
  4. 补全缺失字段（姓名、职位）以实现个性化
  5. 将清理后的补全列表导出至营销工具
监控竞争对手的技术栈：
  1. 使用技术栈端点 → 查看公司使用的工具
  2. 使用相似域名功能 → 查找竞争对手/相关公司
  3. 结合域名搜索功能，找到合适的联系人
  4. 用于基于技术特征的拓展 → 查看
    /sales-intent

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • Don't skip email verification after finding. The Email Finder returns probable emails based on pattern matching — they're not guaranteed deliverable. Always run found emails through the Email Verifier before adding them to campaigns. Sending to unverified emails destroys sender reputation.
  • Don't ignore the Email Format endpoint. Before searching for individual emails, check the domain's email format first (
    /v1/email-format
    ). If you know the company uses 
    first.last@domain.com
    (85% match), you can validate results faster and skip low-confidence guesses.
  • Don't waste credits on unfiltered domain searches. A domain search on a large company can return thousands of results. Use department, seniority, and country filters to narrow to decision-makers you'll actually contact. Each search costs credits regardless of how many results you use.
  • Don't forget about webhook callbacks for bulk jobs. Bulk operations are asynchronous — the API returns immediately but processing continues in background. Use the 
    webhook_url
    parameter to get notified when done instead of polling. Polling wastes API calls and may hit rate limits.
  • Don't assume all plans include the same features. Webhooks require Pro plan or above. Full domain search result downloads are plan-gated. Check your plan's limits before building workflows that depend on these features.
基于研究的最佳实践——请仔细阅读，尤其是关于套餐限制功能和集成问题的内容，这些信息可能会过时。
  • 找到邮箱后不要跳过验证步骤：邮箱查找工具基于模式匹配返回可能的邮箱——这些邮箱并非100%可送达。在将其添加至营销活动前，务必通过邮箱验证工具进行验证。向未验证的邮箱发送邮件会损害发件人信誉。
  • 不要忽略邮箱格式端点：在查找单个邮箱前，先查询该域名的邮箱格式（
    /v1/email-format
    ）。如果知道公司使用
    first.last@domain.com
    格式（匹配度85%），你可以更快地验证结果，跳过低置信度的猜测。
  • 不要在未筛选的域名搜索上浪费积分：对大型公司进行域名搜索可能返回数千条结果。使用部门、职级和国家筛选条件，将结果缩小至实际会联系的决策人员。无论你使用多少条结果，每次搜索都会消耗积分。
  • 不要忘记批量任务的webhook回调：批量操作是异步的——API会立即返回响应，但处理仍在后台进行。使用
    webhook_url
    参数接收完成通知，而非轮询。轮询会浪费API调用次数，可能触发速率限制。
  • 不要假设所有套餐包含相同功能：Webhook需要Pro套餐及以上。完整域名搜索结果下载功能受套餐限制。在构建依赖这些功能的工作流前，请检查你的套餐限制。

Step 5 — Related skills

步骤5 — 相关技能

  • /sales-enrich
    — Enrichment strategy across tools (waterfall enrichment, CRM hygiene, credit optimization)
  • /sales-prospect-list
    — Build targeted prospect lists with ICP definition and segmentation
  • /sales-deliverability
    — Email deliverability setup (SPF/DKIM/DMARC, warmup, inbox placement)
  • /sales-intent
    — Interpret buying signals and prioritize accounts (use Tomba's tech detection as a signal)
  • /sales-integration
    — Connect Tomba to CRM and other tools via Zapier, Make, or API
  • /sales-cadence
    — Design outbound sequences for contacts found in Tomba
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install: 
    npx skills add sales-skills/sales --skills sales-do
  • /sales-enrich
    — 跨工具的信息补全策略（瀑布式补全、CRM数据清理、积分优化）
  • /sales-prospect-list
    — 构建目标潜在客户列表，包含理想客户画像定义和细分
  • /sales-deliverability
    — 邮箱送达率设置（SPF/DKIM/DMARC、邮箱预热、收件箱投递）
  • /sales-intent
    — 识别购买信号并对企业进行优先级排序（使用Tomba的技术检测作为信号）
  • /sales-integration
    — 通过Zapier、Make或API将Tomba连接至CRM和其他工具
  • /sales-cadence
    — 为通过Tomba找到的联系人设计外呼序列
  • /sales-do
    — 不确定使用哪个技能？该路由会将任何销售目标匹配到合适的技能。安装方式：
    npx skills add sales-skills/sales --skills sales-do

Examples

示例

Example 1: Finding emails at a target company

示例1：查找目标公司的所有联系人

User says: "I need to find all the sales leaders at Stripe using Tomba" Skill does:
  1. Recommends Domain Search on 
    stripe.com
    with department=sales and seniority=executive,senior
  2. Shows how to filter results and interpret confidence scores
  3. Recommends verifying emails before outreach
  4. Suggests saving results to a lead list and exporting to campaign tool Result: Filtered, verified list of sales leaders at Stripe ready for outreach
用户提问："我需要使用Tomba查找Stripe的所有销售负责人" 技能处理：
  1. 建议使用域名搜索功能，输入
    stripe.com
    ，筛选条件为部门=销售、职级=高管/高级
  2. 展示如何筛选结果并解读置信度评分
  3. 建议在拓展前验证邮箱
  4. 建议将结果保存至线索列表并导出至营销工具 结果：已筛选、验证的Stripe销售负责人列表，可直接用于拓展

Example 2: Bulk email verification before a campaign

示例2：营销活动前批量验证邮箱

User says: "I have a CSV of 3,000 contacts and need to verify all the emails before launching a Lemlist campaign" Skill does:
  1. Walks through bulk verification setup — CSV format, upload process
  2. Recommends using webhook callback for async completion notification
  3. Explains how to interpret results (valid, invalid, accept_all, unknown)
  4. Advises removing invalid emails and flagging accept_all for monitoring
  5. Points to 
    /sales-lemlist
    for importing the clean list into Lemlist Result: Verified contact list with clear action per status, ready for campaign import
用户提问："我有一个包含3000个联系人的CSV文件，需要在启动Lemlist营销活动前验证所有邮箱" 技能处理：
  1. 引导完成批量验证设置——CSV格式、上传流程
  2. 建议使用webhook回调接收异步完成通知
  3. 解释如何解读结果（有效、无效、accept_all、未知）
  4. 建议移除无效邮箱，并标记accept_all类以密切监控
  5. 引导至
    /sales-lemlist
    ，了解如何将清理后的列表导入Lemlist 结果：已验证的联系人列表，每个状态都有明确的处理建议，可直接导入营销工具

Example 3: Using the Tomba API for automated enrichment

示例3：使用Tomba API实现自动化信息补全

User says: "I want to auto-enrich new HubSpot contacts with Tomba data via Zapier" Skill does:
  1. Outlines the Zapier workflow: HubSpot "New Contact" trigger → Tomba "Enrich" action → HubSpot "Update Contact" action
  2. Explains field mapping from Tomba enrichment to HubSpot properties
  3. Warns about credit consumption and recommends filtering to ICP-matching contacts only
  4. Points to 
    /sales-integration
    for advanced multi-tool workflows Result: Automated enrichment pipeline from HubSpot → Tomba → HubSpot with credit-conscious filtering
用户提问："我想要通过Zapier自动补全新的HubSpot联系人的Tomba数据" 技能处理：
  1. 概述Zapier工作流：HubSpot“新联系人”触发器 → Tomba“信息补全”操作 → HubSpot“更新联系人”操作
  2. 解释Tomba信息补全字段与HubSpot属性的映射关系
  3. 提醒积分消耗问题，建议仅为符合理想客户画像的联系人进行补全
  4. 引导至
    /sales-integration
    ，了解高级多工具工作流 结果：从HubSpot → Tomba → HubSpot的自动化信息补全管道，包含积分优化筛选

Troubleshooting

故障排除

Low match rate on domain search

域名搜索匹配率低

Symptom: Domain search returns very few results for a company you know has many employees Cause: Tomba's database may have limited coverage for that specific company, especially smaller or newer companies Solution: Try searching by company name instead of domain. Use the Email Finder with specific names (from LinkedIn) for targeted lookups. Consider waterfall enrichment with multiple providers — see 
/sales-enrich
.
症状：对某家你知道有很多员工的公司进行域名搜索，返回的结果很少 原因：Tomba的数据库对该公司的覆盖可能有限，尤其是小型或新成立的公司 解决方案：尝试通过公司名称而非域名进行搜索。使用邮箱查找工具，结合LinkedIn上的具体姓名进行定向查找。考虑使用多供应商的瀑布式信息补全——查看
/sales-enrich
。

Email Verifier returns "unknown"

邮箱验证工具返回“unknown”

Symptom: Verification returns "unknown" status instead of valid/invalid Cause: The mail server didn't respond definitively — this happens with some corporate email servers that limit SMTP verification Solution: Don't treat "unknown" as "valid." For high-value prospects, include them but monitor bounce rates closely. For bulk campaigns, exclude unknowns to protect sender reputation.
症状：验证返回“unknown”状态，而非有效/无效 原因：邮件服务器未给出明确响应——部分企业邮件服务器会限制SMTP验证，导致此问题 解决方案：不要将“unknown”视为“有效”。对于高价值潜在客户，可保留但需密切监控退信率。对于批量营销活动，排除unknown类邮箱以保护发件人信誉。

API rate limit errors (429)

API速率限制错误（429）

Symptom: Getting 429 Too Many Requests responses from the API Cause: Exceeding your plan's rate limit — making too many requests too quickly Solution: Implement exponential backoff (wait 1s, 2s, 4s between retries). Batch requests where possible. Use bulk endpoints instead of making individual calls in a loop. If consistently hitting limits, consider upgrading your plan.
症状：从API收到429 Too Many Requests响应 原因：超出套餐的速率限制——短时间内发送了过多请求 解决方案：实现指数退避策略（重试间隔为1秒、2秒、4秒）。尽可能批量请求。使用批量端点而非循环发送单个请求。如果持续超出限制，考虑升级套餐。",