B2B Waterfall Enrichment avatar

B2B Waterfall Enrichment

Pricing

Pay per usage

Go to Apify Store
B2B Waterfall Enrichment

B2B Waterfall Enrichment

Multi-provider waterfall enrichment for company / email / domain. Tries providers in cheapest-first order, returns first match with attribution and a hard budget cap.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

jts

jts

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

14 hours ago

Last modified

Share

What this Actor does

Multi-provider waterfall enrichment for company / email / domain. Tries providers in cheapest-first order, returns first match with attribution and a hard budget cap.

Input example

{
"lookups": [
{
"email": "founder@linear.app"
}
],
"providers": [
"internal",
"hunter",
"clearbit",
"peopledatalabs",
"apollo"
],
"maxBudgetUsd": 1
}

Input fields

Provide one or more lookups (email / domain / companyName), the provider order, a budget cap, and per-provider API tokens.

  • lookups (array, user input): Array of lookup records. Each item is { email?, domain?, companyName? }. At least one field per item is required.
  • providers (array, user input): Provider order. Cheapest-first is recommended (internal -> hunter -> clearbit -> peopledatalabs -> apollo).
  • maxBudgetUsd (number, user input): Hard cap; the cascade stops before any attempt that would exceed this.
  • apiTokens (object, user input): Bring-your-own tokens. Providers without a token are skipped with status skipped_no_token.

Output dataset

Each successful upstream response is written to the default dataset.

  • input: Original input value submitted to the upstream API.
  • result: Full upstream API response.

Developer notes

Set B2B_WATERFALL_ENRICHMENT_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push