Skip to main content
deepline tools execute deepline_native:company_to_contact_by_role_waterfall \
  --payload '{"company_name":"<company_name>","domain":"<domain>","roles":"<roles>","seniority":"<seniority>"}'

How It Works

Providers are tried left to right. The first one to return a result wins — the rest are skipped. At least 3 results are required before stopping.

Parameters

NameTypeRequiredDescription
company_namestringYesCompany name.
domainstringYesCompany domain (required after resolver step).
rolesstring[]YesPrimary persona intent for contact lookup. Accepts one or more role strings as an array or comma-separated string. Prefer exact, real-world title tokens when you know them, for example CEO, CTO, CMO, Founder, Co-Founder, VP Marketing, Head of Security, Director of Engineering, or RevOps. Broad functional inputs like marketing, security, finance, product, engineering, sales, or growth are allowed, but they are inherently noisier and may return adjacent roles unless paired with strong seniority or additional exact titles. A good default is to pass 1-3 exact titles when possible, and only fall back to broad functions when the user intent is actually broad.
senioritystring[]YesBroad seniority intent for cross-provider matching. Use portable values like C-Level, Founder, VP, Head, Director, Manager, Senior, Entry, or Intern instead of provider-specific enums. Treat this as a level hint, not a substitute for a good role string. In practice, exact titles usually matter more than seniority for precision. Use seniority to narrow broad functions like engineering or marketing, but do not rely on seniority alone to express the persona.
limitnumberNoOptional result cap per waterfall step (1-100). Use 1 for cheap sanity checks and 3-10 for better contact coverage in normal runs.

Cost

0-0.91 credits — waterfalls stop at the first match, so you only pay for the provider that returns a result.
StepMax Credits
Apollo0.2
Icypeas0.2
Prospeo0.6
Crustdata0