Amazon Lead Scraper

Build a qualified lead file from Amazon. The run accepts Amazon page URLs and keeps names, email addresses, titles, companies, and domain together for matching and research.

The record

The dataset schema names every field before the run. The first working set is name, url, domain, email, title, company, domain_mx_valid, and scrapedAt. Dataset views keep related fields together without changing the underlying row.

Input

Amazon Lead Scraper accepts source URLs. Run controls stay in the same form.

Field	What it controls	Starting value
startUrls	Enter Amazon search terms or identifiers, one per line.	["zulay milk frother"]
maxItems	Stop after this many dataset rows.	100
maxSeconds	Stop after this many seconds and keep completed rows.	240
includeEmpty	Keep empty-result records in the returned record.	false
maxConcurrency	Set the number of source requests that may run in parallel.	4

Example input

{
  "startUrls": [
    "zulay milk frother"
  ],
  "maxItems": 1,
  "maxSeconds": 240
}

Price

$0.00001 per dataset item. Other Apify plans use the rates shown in the Pricing tab.

Console, API, schedules, and exports

Runs can begin in Apify Console, from a saved task, or through the Actor API. A schedule can reuse the same input. Completed rows remain in the run dataset for API retrieval and Apify dataset exports.

POST https://api.apify.com/v2/acts/fJw6laJjpArYBvMyn/runs
GET  https://api.apify.com/v2/datasets/{datasetId}/items

Saved tasks

Twenty task pages cover distinct research, comparison, operations, automation, and export jobs. The opening set is:

• Amazon lead exact lookup: Review one Amazon record around name, title, url, and domain. The saved task uses startUrls, maxItems, and maxSeconds and opens the overview view. Configured in Amazon Lead Scraper.
• Amazon lead account comparison: Compare Amazon leads using name, url, domain, and email. The identity view keeps the differences close together. Configured in Amazon Lead Scraper.
• Amazon lead source list: Process a saved Amazon input queue with startUrls, maxItems, and maxSeconds. Source and identifier fields remain visible in the source view. Configured in Amazon Lead Scraper.
• Amazon lead identity index: Index Amazon leads by name, title, email, and company. The saved input keeps the same matching keys from run to run. Configured in Amazon Lead Scraper.
• Amazon lead contact coverage: Assemble an Amazon register centered on domain, email, domain_mx_valid, and name. The task keeps startUrls, maxItems, and maxSeconds visible for later review. Configured in Amazon Lead Scraper.
• Amazon lead audience benchmark: Compare a second field set across Amazon leads, led by name, url, domain, and email. Results open as the time table. Configured in Amazon Lead Scraper.

Related products

• Amazon Product Scraper
• Amazon Product Export Scraper
• Google Maps Email Scraper
• LinkedIn Email Scraper
• LinkedIn Profile Scraper

Support

Include the Actor ID, run ID, saved task name, and affected input when reporting an issue. That is enough to locate the run and its dataset.