AS
Apify Store
/pipelinelabs/lead-scraper-apollo-zoominfo-lusha-ppe
🎉Leads Scraper ✅ $1/1k Leads ✅ 50K/Run With EMAILS✅Like Apollo
$1/1k Leads - Scrape Up to 50K leads per run with Emails, LinkedIn URL, Phone Numbers, & More! Similar to Apollo, ZoomInfo, Lusha. 250+ Million Verified Database!
liveasyncunknown~30s typical
lead generationleadapollozoominfolushappe
$0.00001
per result + $0.005 call
plus $0.001 platform fee per run
Actor charges $0.00001 per result; Cracked adds 25% plus a $0.005 call fee
Bring your own Apify Store key: provider portion drops to $0.
$Set up https://cracked-ai-pearl.vercel.app/SKILL.md, then use Cracked to run apify /pipelinelabs/lead-scraper-apollo-zoominfo-lusha-ppe for me.
Input
| Field | Type | Description |
|---|---|---|
| totalResults | integer | What this does: Sets how many leads to extract in this run. Best practice: Start with a smaller test run (e.g. 200-1000), then scale up once the results look right. default 1000 |
| personRoleSection | string | UI section |
| personTitleIncludes | array | What this does: Returns people whose title matches any entered term. Best practice: Use 1-3 high-signal titles first, then add more only if needed. |
| personTitleExcludes | array | What this does: Removes people with titles matching these terms. Best practice: Use this to remove assistant/junior/intern-style false positives. |
| includeTitleVariants | boolean | What this does: Expands common title equivalents (e.g. CEO <-> Chief Executive Officer). Best practice: Turn ON for broader recall; turn OFF only when you need strict title wording. default false |
| seniorityIncludes | array | What this does: Includes selected seniority levels. Best practice: Pair with Excludes to keep only target decision levels. |
| seniorityExcludes | array | What this does: Excludes selected seniority levels. Best practice: Use to remove levels like Entry/Intern when targeting decision makers. |
| functionIncludes | array | What this does: Includes selected departments/functions. Best practice: Start with 1-2 core functions before broadening. |
| functionExcludes | array | What this does: Excludes selected departments/functions. Best practice: Use to remove adjacent teams that create noisy matches. |
| roleMatchMode | string (all | any) | What this does: Chooses how title/seniority/function combine: all = AND (strict), any = OR (broader). Best practice: Start with OR for discovery, then switch to AND when you need precision. default "any" |
| contactSection | string | UI section |
| hasEmail | boolean | What this does: Only returns leads with an email value. Best practice: Enable for outreach use-cases. default false |
| hasPhone | boolean | What this does: Only returns leads with a phone value. Best practice: Enable only when phone is required, since this reduces volume. default false |
| emailStatusIncludes | array | What this does: Filters by email deliverability. Verified = confirmed deliverable. Unverified = pattern match, unavailable, catch all. Best practice: Use Verified only for high-quality outbound. Add Unverified to increase volume at the cost of deliverability. |
| emailStatusExcludes | array | What this does: Excludes selected email deliverability statuses. Best practice: Usually use Includes only; use Excludes when you need fine control. |
| personFirstNameIncludes | array | What this does: Includes only leads with these first names. Best practice: Use only when you already know exact names. |
| personFirstNameExcludes | array | What this does: Excludes leads with these first names. Best practice: Use for cleanup only. |
| personLastNameIncludes | array | What this does: Includes only leads with these last names. Best practice: Combine with title/company/location to avoid over-restricting. |
| personLastNameExcludes | array | What this does: Excludes leads with these last names. Best practice: Use for cleanup only. |
| personLocationSection | string | UI section |
| personLocationCountryIncludes | array | What this does: Includes only people located in the selected countries. Best practice: Start with 1-2 core countries to reduce noise. |
| personLocationCountryExcludes | array | What this does: Excludes people located in the selected countries. Best practice: Use this to remove regions you cannot sell to. |
| personLocationStateIncludes | array | What this does: Includes selected person states/regions. Best practice: Use country + state together for cleaner geography. |
| personLocationStateExcludes | array | What this does: Excludes selected person states/regions. Best practice: Use with includes to avoid noisy states. |
| personLocationCityIncludes | array | What this does: Includes only people in these cities. Best practice: Combine with country/state filters so city names are interpreted correctly. |
| personLocationCityExcludes | array | What this does: Excludes people in these cities. Best practice: Use to remove metro areas that create low-fit results. |
| companySection | string | UI section |
| companyMatchMode | string (all | any) | What this does: Controls how Company includes combine (name + industry). Best practice: Use Any (OR) for broader discovery. Use All (AND) for stricter precision. default "any" |
| companyNameIncludes | array | What this does: Includes leads at companies whose names match any entered value. Best practice: Use for account-based targeting (named account lists). |
| companyNameExcludes | array | What this does: Excludes leads at companies whose names match any entered value. Best practice: Use to remove partners, competitors, or internal accounts. |
| companyIndustryIncludes | array | What this does: Includes only selected company industries. Best practice: Start with a narrow set of primary industries, then expand. |
| companyIndustryExcludes | array | What this does: Excludes selected company industries. Best practice: Remove adjacent industries that look similar but are out of scope. |
| companyKeywordSection | string | UI section |
| companyKeywordIncludes | array | What this does: Includes companies whose name/description contains these keywords. Best practice: Use product/problem keywords to find similar companies. |
| companyKeywordExcludes | array | What this does: Excludes companies whose name/description contains these keywords. Best practice: Add obvious false-positive terms to clean results quickly. |
| companyKeywordMode | string (broad | phrase | exact) | What this does: Controls text matching style for company keyword filters. Best practice: Start with Broad. Move to Phrase/Exact when narrowing results. default "broad" |
| companySizeSection | string | UI section |
| companySizeIncludes | array | What this does: Includes selected company size buckets. Best practice: Pick the closest size band to your ideal customers first. |
| companySizeExcludes | array | What this does: Excludes selected company size buckets. Best practice: Use to remove segments outside your target size profile. |
| companyEmployeeMin | integer | What this does: Adds a custom company size minimum include range. Best practice: Use with Company size buckets when you need finer control. |
Call it
curl
curl https://cracked-ai-pearl.vercel.app/v1/run \
-H "Authorization: Bearer ck_live_..." -H "content-type: application/json" \
-d '{"provider":"apify","endpoint":"/pipelinelabs/lead-scraper-apollo-zoominfo-lusha-ppe","input":{},"wait":false}'poll
curl "https://cracked-ai-pearl.vercel.app/v1/runs/<runId>?wait=30" -H "Authorization: Bearer ck_live_..."cli
npx cracked-ai run -p apify -e /pipelinelabs/lead-scraper-apollo-zoominfo-lusha-ppe -i '{}' -w 120mcp
run_tool({ provider: "apify", endpoint: "/pipelinelabs/lead-scraper-apollo-zoominfo-lusha-ppe", input: {}, wait: false })Try it
Runs against your signed-in workspace balance. Sign in if you have not.