Skip to main content

​
How to Run Waterfall Enrichment in Claude Code

Claude Code can operate Deepline from the terminal. Use a maintained or owned Play for multi-step work. Inspect its contract, run a pilot, and review the output.

112+

catalog integrations

1 Play

production Play contract

Pilot first

review before scale

Observable

status, usage, and errors

Install

​
Define the email enrichment task

This guide covers verified work-email lookup, not email sending. Match the person and employer, validate the returned address, and stop when the declared acceptance rule passes. Treat permission to contact the person and the sending channel as separate checks. Before running anything, choose what counts as a usable record. A waterfall tries providers in a declared sequence. It advances only when the current result fails the Play’s acceptance rule; a returned value alone is not success. If every stage misses, the Play returns its declared no-result output. The maintained Play is the source of truth for its current stages. The evaluation guide separates identity, validation, cost, and CRM write eligibility. The B2B waterfall guide explains when the pattern is useful.

​
Give Claude Code the Deepline skill

Then ask Claude Code:
Find verified work emails for leads.csv with a maintained waterfall Play. Inspect the contract and run a three-row pilot before the full file.

Discover

​
Resolve the current workflow

Claude Code searches the live catalog and inspects the selected Play:
Check the accepted CSV fields, output shape, current workflow identity, and pricing information. The Deepline catalog contains 112+ integrations; the described Play declares the smaller route used for this job.

Pilot

​
Run the production-shaped Play on representative rows

Review:
  • accepted, ambiguous, invalid, no-result, and failed rows
  • provider provenance for accepted values
  • output columns and downstream compatibility
  • usage and pricing units for stages that executed
  • errors, retries, and validation behavior
If the result fits the job, use the same contract on the full file:

Own

​
Put a custom route in version control

Use an owned Play when you need a different provider sequence, custom validation, approvals, CRM writes, schedules, or webhooks:
The durable artifact is the checked Play, not a remembered shell flag or provider list.

Billing

​
Estimate from the route that actually ran

  • BYOK: Deepline charges no platform fee for provider requests; you pay providers under your own contracts.
  • Managed billing: Some tools charge for returned results, while others charge per request or page. Attempted calls can therefore carry usage even when the row has no result.
  • Standalone examples: A successful DropLeads Email Finder result costs 0.26 Deepline credits. Hunter Email Finder costs 0.30 credits. Prospeo Enrich Person costs 0.55 credits. These rates do not define a waterfall total.
Recheck live pricing before publication or execution. Use the pilot’s usage to estimate your own input mix.

Related

​
Keep reading

Continue Reading

Install Deepline. Ask Claude Code to search the live Play catalog and inspect the selected contract. Create a representative pilot CSV. Run the maintained Play with —watch. Review its output, provenance, usage, and errors.
The maintained Play contract is the source of truth for its current stages. Deepline has a broader integration catalog, but an individual waterfall uses only the providers declared by that Play. Run deepline plays describe before execution instead of relying on a fixed marketing-page list.
The total depends on which stages execute, the result path, and your billing mode. BYOK means you pay providers directly. Managed tools may charge per result, request, or page. Use a representative pilot and the live pricing contract rather than a universal per-row estimate.
A waterfall can fill gaps left by one provider, but the lift depends on input quality, ICP, geography, field, provider route, and validation policy. Measure accepted, ambiguous, invalid, no-result, and failed rows on representative data.
Yes. Create an owned .play.ts workflow from the inspected contracts, edit its stages, and run deepline plays check. Publish it when the route, validation, retries, and review boundaries should become a reusable team contract.