Sales
•
Lead generation
Public-Data ICP Account Harvesting
Builds ICP-matched account and contact lists from public directories, registries, marketplaces, maps, GitHub, open datasets, approved Apify Actors, or supplied files—without LinkedIn scraping—then enriches, scores, deduplicates, and writes linked Nex lead records.
Last updated
Builds ICP-matched account and contact lists from public directories, registries, marketplaces, maps, GitHub, open datasets, approved Apify Actors, or supplied files—without LinkedIn scraping—then enriches, scores, deduplicates, and writes linked Nex lead records.
What this agent does
Builds ICP-matched account and contact lists from public directories, registries, marketplaces, maps, GitHub, open datasets, approved Apify Actors, or supplied files—without LinkedIn scraping—then enriches, scores, deduplicates, and writes linked Nex lead records.
Who this is for
Designed for founders, revenue leaders, and go-to-market teams that want a reviewable public-data icp account harvesting workflow grounded in their own organizational context.
When it runs
When an ICP and an approved public data source, actor, dataset, or file are ready.
How the workflow works
Choose source and ICP → collect accounts and contacts → enrich → score → deduplicate → write linked Nex lead records.
Inputs and prerequisites
Connect the relevant systems, define the approved data scope and success criteria, and assign a human owner for review. The workflow should not run on data or channels the team has not authorized.
Typical inputs include HubSpot, Salesforce, Attio; the team’s ICP, voice, playbooks, and approval rules; and the source records needed for this specific run.
Outputs
The agent returns a sourceable result, its reasoning and evidence, linked Nex records or proposed updates when relevant, and approval-ready drafts or next actions. For this template, the core flow is: Choose source and ICP → collect accounts and contacts → enrich → score → deduplicate → write linked Nex lead records.
Approvals and safeguards
Uses public or supplied data and approved actors; it excludes LinkedIn scraping and requires review of source compliance and lead eligibility.
Integrations
This template can use HubSpot, Salesforce, Attio. Connections, permissions, and available actions vary by the workspace configuration.
What it can replace
Consolidates or replaces parts of the workflow handled across Clay, Apollo, Crunchbase, Apify, Clearbit. It does not claim to replace every capability of each product. Referenced workflow tools include Clay, Apollo, Crunchbase, Apify, Clearbit.
Estimated software savings
Est. $200–$900/mo. Illustrative monthly software-stack consolidation range based on overlapping workflow categories and public self-serve prices reviewed on August 25, 2026. Actual savings vary by plan, seats, usage, retained tools, and data costs; Nex may complement rather than replace every capability.
Use the template prompt
Use the Copy prompt action on this page to copy the current Nex template prompt. Review integrations, permissions, thresholds, tone, and approval gates before running it in your workspace.
Frequently asked questions
What does the Public-Data ICP Account Harvesting agent do?
Builds ICP-matched account and contact lists from public directories, registries, marketplaces, maps, GitHub, open datasets, approved Apify Actors, or supplied files—without LinkedIn scraping—then enriches, scores, deduplicates, and writes linked Nex lead records.
What data and integrations does the Public-Data ICP Account Harvesting agent use?
It uses only approved context and connected systems relevant to the workflow. In this template, that can include HubSpot, Salesforce, Attio. Exact access depends on the integrations and permissions configured in Nex.
Does this agent replace Clay, Apollo, Crunchbase?
Consolidates or replaces parts of the workflow handled across Clay, Apollo, Crunchbase, Apify, Clearbit. It does not claim to replace every capability of each product. The Est. $200–$900/mo figure is an illustrative software-stack consolidation range, not a guaranteed outcome.
Last updated
August 25, 2026. Template behavior and third-party pricing can change; verify operational and pricing details before publishing or running the workflow.