# Lead Magnet Form Inventory (`junipr/lead-magnet-form-inventory`) Actor

Inventory public lead-magnet forms, newsletter forms, gated content CTAs, form fields, consent copy, thank-you/download links, and placement context

- **URL**: https://apify.com/junipr/lead-magnet-form-inventory.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $27.50 / 1,000 browser page checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Lead Magnet Form Inventory

Inventory public lead-magnet forms, newsletter forms, gated content CTAs, form fields, consent copy, thank-you/download links, and placement context.

### What it does

Renders public pages and inventories lead forms, fields, requirements, CTAs, consent text, privacy links, gated assets, placement, and friction issues.

The actor emits one row per public lead form, or a no-form diagnostic. Dataset and report output is produced only after every applicable PPE charge is accepted.

### Common uses

- Inventory lead magnet forms
- Audit newsletter signup fields
- Find missing privacy links on forms
- Export gated content CTA inventory
- Review lead capture friction

### Input

Supply public HTTP(S) URLs or deterministic `htmlInputs`. URL fetching rejects localhost and private-network destinations; `allowedDomains` can narrow access further.

- `startUrls`
- `sitemapUrls`
- `htmlInputs`
- `allowedDomains`
- `maxPages`
- `maxDepth`
- `includeEvidence`
- `includeRawSnapshots`
- `requestDelayMs`
- `timeoutMs`
- `userAgentMode`
- `pageUrls`
- `followInternalLeadLinks`
- `formSelectors`
- `ctaTerms`
- `includeHiddenFields`
- `maxFormsPerPage`
- `maxForms`
- `maxBrowserPages`
- `viewportWidth`
- `viewportHeight`
- `maxChargeUsd`
- `includeReport`

The caps in `maxPages, maxForms, maxBrowserPages, maxScreenshots, timeoutMs` and `maxChargeUsd` are enforced. A zero charge cap is a hard zero budget.

### Output

- `sourceUrl`
- `sourceType`
- `pageTitle`
- `recordType`
- `recordName`
- `issueCode`
- `severity`
- `evidenceSnippet`
- `recommendation`
- `canonicalUrl`
- `httpStatus`
- `scannedAt`
- `pageUrl`
- `formId`
- `formType`
- `ctaText`
- `leadMagnetTitle`
- `fieldNames`
- `requiredFieldCount`
- `consentText`
- `privacyLinkUrl`
- `thankYouOrDownloadSignal`
- `placementContext`

Reports:

- `lead-magnet-form-inventory-summary-report.md`
- `lead-magnet-form-inventory-records.csv`
- `lead-magnet-form-inventory-issues.json`
- `lead-magnet-form-inventory-evidence-samples.json`
- `lead-magnet-form-inventory-run-metadata.json`

### Pricing

Platform-usage pass-through is off. Locked fixed-inclusive events:

| Event | Price |
| --- | ---: |
| `actor-start` | $0.08 |
| `browser-page-checked` | $0.0275 |
| `form-record-extracted` | $0.0095 |
| `form-issue-detected` | $0.0195 |
| `report-generated` | $0.18 |

The actor charges `actor-start` before fetching/rendering, deduplicates page events, charges record/finding events only for corresponding output, and stops before further output on partial, limited, or over-budget charges. Screenshot events fire only when a real browser PNG exists.

### Safety and limitations

- Public pages only; no authentication, CAPTCHA bypass, access-control evasion, or private data.
- Browser waits, pages, records, changes, forms, popups, and screenshots are bounded.
- Blocked, empty, and missing-baseline cases produce diagnostics instead of invented success.
- Results describe source evidence at scan time and may change later.
- Store discounts, icons, publication, and scheduler state are separate live configuration gates.

### Local validation

```bash
pnpm --filter @junipr/lead-magnet-form-inventory build
pnpm --filter @junipr/lead-magnet-form-inventory test
pnpm --filter @junipr/lead-magnet-form-inventory smoke
```

Fixtures cover success, weak/blocked evidence, comparison, no-result, and cap behavior. Tests also prove schema equality, pricing metadata, charge guards, zero budget, reports, and charge-before-output ordering.

# Actor input Schema

## `startUrls` (type: `array`):

startUrls for Lead Magnet Form Inventory.

## `sitemapUrls` (type: `array`):

sitemapUrls for Lead Magnet Form Inventory.

## `htmlInputs` (type: `array`):

htmlInputs for Lead Magnet Form Inventory.

## `allowedDomains` (type: `array`):

allowedDomains for Lead Magnet Form Inventory.

## `maxPages` (type: `integer`):

maxPages for Lead Magnet Form Inventory.

## `maxDepth` (type: `integer`):

maxDepth for Lead Magnet Form Inventory.

## `includeEvidence` (type: `boolean`):

includeEvidence for Lead Magnet Form Inventory.

## `includeRawSnapshots` (type: `boolean`):

includeRawSnapshots for Lead Magnet Form Inventory.

## `requestDelayMs` (type: `integer`):

requestDelayMs for Lead Magnet Form Inventory.

## `timeoutMs` (type: `integer`):

timeoutMs for Lead Magnet Form Inventory.

## `userAgentMode` (type: `string`):

userAgentMode for Lead Magnet Form Inventory.

## `pageUrls` (type: `array`):

pageUrls for Lead Magnet Form Inventory.

## `followInternalLeadLinks` (type: `boolean`):

followInternalLeadLinks for Lead Magnet Form Inventory.

## `formSelectors` (type: `array`):

formSelectors for Lead Magnet Form Inventory.

## `ctaTerms` (type: `array`):

ctaTerms for Lead Magnet Form Inventory.

## `includeHiddenFields` (type: `boolean`):

includeHiddenFields for Lead Magnet Form Inventory.

## `maxFormsPerPage` (type: `integer`):

maxFormsPerPage for Lead Magnet Form Inventory.

## `maxForms` (type: `integer`):

maxForms for Lead Magnet Form Inventory.

## `maxBrowserPages` (type: `integer`):

maxBrowserPages for Lead Magnet Form Inventory.

## `viewportWidth` (type: `integer`):

viewportWidth for Lead Magnet Form Inventory.

## `viewportHeight` (type: `integer`):

viewportHeight for Lead Magnet Form Inventory.

## `maxChargeUsd` (type: `number`):

maxChargeUsd for Lead Magnet Form Inventory.

## `includeReport` (type: `boolean`):

includeReport for Lead Magnet Form Inventory.

## Actor input object example

```json
{
  "startUrls": [],
  "sitemapUrls": [],
  "htmlInputs": [
    {
      "sourceUrl": "https://example.com/guide",
      "sourceType": "rendered",
      "html": "<title>Guide</title><form id='guide' data-placement='hero'><h2>Download the growth guide</h2><input name='email' required><label><input name='consent' required> I agree to marketing</label><a href='/privacy'>Privacy</a><button>Download guide</button></form>"
    }
  ],
  "allowedDomains": [],
  "maxPages": 5,
  "maxDepth": 5,
  "includeEvidence": false,
  "includeRawSnapshots": false,
  "requestDelayMs": 5,
  "timeoutMs": 5,
  "userAgentMode": "",
  "pageUrls": [],
  "followInternalLeadLinks": false,
  "formSelectors": [],
  "ctaTerms": [],
  "includeHiddenFields": false,
  "maxFormsPerPage": 10,
  "maxForms": 10,
  "maxBrowserPages": 3,
  "viewportWidth": 5,
  "viewportHeight": 5,
  "maxChargeUsd": 50,
  "includeReport": true
}
```

# Actor output Schema

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

No description

## `report` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/lead-magnet-form-inventory").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/lead-magnet-form-inventory").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 '{}' |
apify call junipr/lead-magnet-form-inventory --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/lead-magnet-form-inventory"
        }
    }
}

```

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/kubhLT5HmwM1hZz7K/builds/UugVJgRK7wfAGucxQ/openapi.json