Intent-Based Lead Finder — People Researching Any Topic avatar

Intent-Based Lead Finder — People Researching Any Topic

Pricing

from $14.00 / 1,000 intent leads

Go to Apify Store
Intent-Based Lead Finder — People Researching Any Topic

Intent-Based Lead Finder — People Researching Any Topic

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

Pricing

from $14.00 / 1,000 intent leads

Rating

0.0

(0)

Developer

CAG Signals

CAG Signals

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Categories

Share

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. Its five-company preview returns counts, with optional paid topics.

Questions about fit? Email CAG Signals 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.

{
"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

resolved_topic_nameintent_scoreintent_percentilebusiness_emaillinkedin_urlpreview
Marketing Automationhigh94buyer@example.comlinkedin.com/in/examplefalse

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

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

{
"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?

ActorUse it whenPrice
Company Buyer Intent Lookup — Domain to Intent TopicsYou 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 DiscoveryYou 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 IntentYou 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 TopicYou 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.