# Intent-Based Lead Finder — People Researching Any Topic (`cag_ai-actors/topic-based-lead-prospecting`) Actor

Find B2B leads associated with a supported research topic. Preview masked rows; paid output includes business contact fields only where available.

- **URL**: https://apify.com/cag_ai-actors/topic-based-lead-prospecting.md
- **Developed by:** [CAG Signals](https://apify.com/cag_ai-actors) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $14.00 / 1,000 intent leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Intent-Based Lead Finder — People Researching Any Topic

Find person-level B2B leads associated with a supported research topic. Review available intent scores and match fields to decide which records merit further research. Business email and LinkedIn fields are included only where available; contact coverage is not guaranteed.

**First step:** preview returns up to 25 lead rows with email and LinkedIn identifiers masked. Paid results are optional. Review the price and your data-handling controls before proceeding. A research signal does not prove a purchase decision.

**Evaluating known company accounts instead?** Start with [Company Buyer Intent Lookup](https://apify.com/cag_ai-actors/company-intent-signals). Its five-company preview returns counts, with optional paid topics.

Questions about fit? [Email CAG Signals](mailto:cagsignals@techallstar.com) or reply to your invitation. Never post personal identifiers, customer lists or credentials in public Issues.

### What buyer-intent data means

Buyer-intent data estimates the topics a person or company is actively researching. A topic, intent tier, and percentile help rank timing and fit; they are signals, not proof of intent or purchase. Use them alongside your own CRM context and lawful outreach rules.

### Sample output

The values below are illustrative; the field names match the public dataset contract.

```json
{
  "record_type": "DATA",
  "source_actor": "topic-based-lead-prospecting",
  "data_source": "licensed-b2b-intent",
  "contract_version": "2.0",
  "resolved_topic_name": "Marketing Automation",
  "matched": true,
  "hem": "illustrative-hashed-email-match-key",
  "intent_score": "high",
  "intent_percentile": 94,
  "business_email": "buyer@example.com",
  "linkedin_url": "https://www.linkedin.com/in/example",
  "preview": false,
  "retrieved_at": "2026-08-29T12:00:00.000Z"
}
```

Dataset table preview:

![Illustrative intent-lead dataset table](./docs-assets/sample-output-table.png)

| resolved_topic_name | intent_score | intent_percentile | business_email | linkedin_url | preview |
|---|---|---:|---|---|---:|
| Marketing Automation | high | 94 | buyer@example.com | linkedin.com/in/example | false |

**Person-level data:** paid output can include a business email address and LinkedIn profile URL where available in the licensed source data. Preview identifiers remain masked.

### Run it in Apify Console

1. Open the Actor and select **Start**.
2. Leave `Marketing Automation` as `topic` and keep `previewMode` enabled.
3. Start the run and inspect the **Output** dataset. Preview returns up to 25 real, top-ranked leads with email and LinkedIn identifiers masked.
4. Disable `previewMode` only after the topic resolution and output shape look correct. Use `dryRun: true` instead when you need only the exact billable count.

Preview and dry-run requests do not emit `topic-lead-found` events. Apify platform usage may still apply according to your Apify plan.

### Run it through the API

```bash
curl -X POST \
  "https://api.apify.com/v2/acts/cag_ai-actors~topic-based-lead-prospecting/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "Marketing Automation",
    "maxResults": 25,
    "previewMode": true,
    "dryRun": false
  }'
```

### Input

```json
{
  "topic": "Marketing Automation",
  "maxResults": 100,
  "minScore": "high",
  "minPercScore": 80,
  "previewMode": true,
  "dryRun": false
}
```

- `topic` accepts one supported B2B topic name and must resolve to one exact active B2B taxonomy match.
- `maxResults` defaults to 100 in live mode; preview is capped at 25.
- `minScore` and `minPercScore` optionally filter for stronger intent.
- `previewMode` returns masked real preview rows without paid result events.
- `dryRun` takes precedence over preview and returns only the exact billable lead count.

### Output fields

- `record_type` distinguishes `DATA`, `ERROR`, `TOPIC_RESOLUTION_ERROR`, `SUPPRESSED`, and the final `SUMMARY` row.
- `resolved_topic_name` shows the exact resolved topic name.
- `hem` is a hashed-email match key.
- `intent_score` and `intent_percentile` describe intent strength.
- `business_email` and `linkedin_url` appear when available; coverage is not guaranteed.
- `preview`, `data_source`, `contract_version`, and `retrieved_at` identify run mode, source, and retrieval time.
- `SUPPRESSED` rows identify only the resolved topic and suppression status; they contain no person identifier.
- The `SUMMARY` row reports input, matched, delivered, charged, unmatched, and suppressed counts plus total charge.

### Pricing

Base pay-per-result price: **$0.02 per intent lead ($20 per 1,000)**. Actor Start is $0.00. Apify plan discounts may lower the unit price; use this Actor's Pricing tab for current plan-specific rates and platform-cost details.

**No-match, no-charge guarantee:** zero-result topics, suppressed leads, invalid topic terms, validation failures, preview rows, dry-run rows, and error rows do not emit the `topic-lead-found` event. Apify platform usage may still apply.

### Integrations

#### n8n HTTP Request

Create an **HTTP Request** node with method POST, the synchronous dataset endpoint above, an `Authorization: Bearer ...` header, and a JSON body built from the workflow topic. Split the returned JSON array and route only rows that meet your own lawful-use and suppression rules.

#### Make

Use **HTTP > Make a request** with the same endpoint, headers, and JSON body. Parse the response as JSON and map the approved fields into a restricted CRM or review queue.

#### Clay HTTP API

Add an HTTP API enrichment column, choose POST, and map a Clay topic value into `topic`. Start with `previewMode: true`; do not persist or expose paid person-level fields until your retention and access rules are in place.

#### curl / API

The curl example above returns dataset items synchronously. For larger paid runs, start the Actor asynchronously and fetch the restricted default dataset after the run succeeds.

#### Apify MCP

After connecting the Apify MCP server to an MCP-compatible agent, ask it to run `cag_ai-actors/topic-based-lead-prospecting` with the same JSON input. Keep `previewMode` enabled for the first agent-initiated run and require human confirmation before a paid or person-level run.

### FAQ

#### Can I enter a topic name?

The name must resolve to exactly one active B2B taxonomy match; ambiguous or missing names return suggestions and no paid event.

#### What does preview return?

It returns up to 25 real, top-ranked people with email and LinkedIn identifiers masked. It does not emit paid result events.

#### What is the difference between preview and dry run?

Preview returns masked lead rows. `dryRun: true` returns only the exact number of billable leads and takes precedence over preview.

#### When am I charged?

Only after a paid-mode intent lead is written to the dataset. Suppressed, preview, dry-run, validation, no-result, and error paths do not emit paid events.

#### Are email and LinkedIn fields always present?

No. They appear only when they are available in the licensed source data; every delivered lead still includes its available match and intent fields.

#### What is `hem`?

It is a hashed-email match key supplied for identity matching. It is not a plaintext email address.

#### Can I filter by intent strength?

Yes. Use `minScore` for the categorical tier and `minPercScore` for the percentile threshold.

#### How do I cap spend?

Set `ACTOR_MAX_TOTAL_CHARGE_USD` on the run and choose an appropriate `maxResults`. The Actor stops further paid delivery when the charge limit is reached.

#### How should I secure the output?

Restrict dataset access, choose a short retention period, prevent uncontrolled exports, and maintain suppression and deletion workflows before running paid person-level searches.

#### Can I use these leads for sensitive decisions?

No. Do not use the output for eligibility, employment, housing, credit, insurance, health, or other similarly sensitive decisions.

### Data provenance and responsible use

CAG Signals provides B2B buyer-intent workflows for account research and prioritization.

CAG Signals delivers licensed B2B buyer-intent data through a managed data service. CAG Signals is independently operated and is not affiliated with or endorsed by any upstream data provider.

Results use licensed B2B buyer-intent data and may contain person-level business data. Use the Actor only for lawful B2B sales, marketing, and research involving records you are permitted to process. Do not use output for eligibility, credit, employment, housing, insurance, consumer profiling, discriminatory targeting, or raw-data resale. Apply an appropriate legal basis, access controls, retention limits, security safeguards, and suppression/deletion process.

For a suppression or removal request, use the **Issues** tab on this Actor page
without posting an email address, profile URL, hashed identifier, dataset row,
API token, or other personal data. Ask for a private intake method and provide
the minimum identifier only through that private channel. CAG Signals will
acknowledge the request within 24 hours, investigate the relevant records, and
apply suppression or deletion where required.

### Which Actor should I use?

| Actor | Use it when | Price |
|---|---|---|
| [Company Buyer Intent Lookup — Domain to Intent Topics](https://apify.com/cag_ai-actors/company-intent-signals) | You have a company domain or LinkedIn company URL and want its buying-intent topics. | $0.005 per matched record ($5 per 1,000) |
| [Find Companies by Buyer Intent — B2B Account Discovery](https://apify.com/cag_ai-actors/b2b-account-intent-finder) | You have intent topics and want ranked companies researching them. | Preview up to 25 companies, then $0.005 per company result ($5 per 1,000) |
| [B2B Contact Intent Enrichment — Email & LinkedIn Intent](https://apify.com/cag_ai-actors/b2b-buyer-intent-enrichment) | You already have contacts or companies and want to add current intent topics. | $0.01 per matched contact record ($10 per 1,000) |
| [Intent-Based Lead Finder — People Researching Any Topic](https://apify.com/cag_ai-actors/topic-based-lead-prospecting) | You have intent topics and want people researching them. | $0.02 per intent lead ($20 per 1,000) |

### Support

Use the **Issues** tab on this Actor page with the run ID, expected behavior,
and observed behavior. Do not include API tokens, credentials, customer data,
or personal identifiers. CAG Signals responds to new issues within 24 hours.

# Changelog

This Actor's version history is a separate document: https://apify.com/cag_ai-actors/topic-based-lead-prospecting/changelog.md

# Actor input Schema

## `topic` (type: `string`):

Supported B2B topic name. Example: Marketing Automation. Names resolve to exactly one active taxonomy match (case-insensitive exact name, not the first search hit). Existing saved integrations may continue to pass a legacy topic identifier during the 2.0 migration; new integrations should use names.

## `maxResults` (type: `integer`):

Maximum number of leads to fetch in live mode. Free preview mode is capped at 25 real masked records by the managed data service.

## `minScore` (type: `string`):

Only return leads at or above this intent tier. Leave unset for all tiers.

## `minPercScore` (type: `integer`):

Only return leads with a percentile score at or above this value (0-99).

## `previewMode` (type: `boolean`):

Return up to 25 real, top-ranked people from the managed preview service. Email and LinkedIn identifiers remain masked and no Actor result event is charged.

## `dryRun` (type: `boolean`):

If true, returns the exact number of billable leads available without returning any leads or charging. This takes precedence over preview mode.

## Actor input object example

```json
{
  "topic": "Marketing Automation",
  "maxResults": 100,
  "previewMode": true,
  "dryRun": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "topic": "Marketing Automation"
};

// Run the Actor and wait for it to finish
const run = await client.actor("cag_ai-actors/topic-based-lead-prospecting").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "topic": "Marketing Automation" }

# Run the Actor and wait for it to finish
run = client.actor("cag_ai-actors/topic-based-lead-prospecting").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "topic": "Marketing Automation"
}' |
apify call cag_ai-actors/topic-based-lead-prospecting --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cag_ai-actors/topic-based-lead-prospecting"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MYZMk8bJsKQu6VN9H/builds/IDMmzicqYMdboYfgN/openapi.json