Cosmetics Recall Monitor

Pricing

Rating

Developer

Actor stats

Categories

Share

A product recall and safety alert intelligence feed for teams that need source-backed risk signals before manual review catches up. Monitors EU Safety Gate alerts, EU ICSMS and returns buyer-ready records with source evidence.

Who this is for

Procurement, sales, partnerships, compliance, and research teams use this actor when they need a focused cosmetics recall feed instead of a broad generic scraper.

Buyer outcomes

• Find relevant cosmetics recall records faster with normalized source evidence and match context.
• Prioritize review using scores, confidence, source URLs, and buyer-ready summary fields.
• Route new or changed records into recurring workflows through saved inputs, schedules, and alerts.

Sources monitored

• EU Safety Gate alerts
• EU ICSMS

Inputs

• sourceMode: use sample for the default Store test, startUrls for URL-backed runs, or another supported source mode when configured.
• startUrls: optional public URLs with a working small default/prefill for URL-backed smoke runs.
• sourceIds: approved source identifiers to keep runs scoped to known public data sources.
• maxItems: bounded result limit; the default is intentionally small for first-run validation.
• sinceLastRun: return only new or changed records when scheduled delta mode is enabled.
• watchlistTerms: buyer keywords, companies, products, places, or risk terms used for monitoring context.
• webhookUrl: optional completion or alert destination for recurring workflows.
• outputMode: use sample records for Store validation or buyer-ready records for production runs.

Outputs

The actor returns buyer-ready records with source attribution, match context, and normalized fields for review or downstream routing.

• recordId: Stable record ID for exports, dedupe, and downstream joins.
• title: Buyer-readable opportunity or record title.
• sourceName: Source identifier used to trace where the record came from.
• sourceUrl: Direct source URL for review and audit.
• dedupeKey: Stable key used for delta mode and duplicate suppression.
• retrievedAt: Timestamp showing when the actor retrieved or generated this record.
• score: Normalized field for filtering, routing, or downstream review.
• scoreReasons: Buyer-readable explanation for the score or match.
• confidence: Normalized field for filtering, routing, or downstream review.
• errors: Normalized field for filtering, routing, or downstream review.
• runSummary: Run-level summary for counts, filters, charges, and next actions.

Pricing

This actor uses Apify pay-per-event pricing. Current public listing guidance: $29-$49 / 1,000 launch validation records until public data proof is complete. Charges are tied to buyer-visible value events such as recall-alert, dataset-processed, record-saved, enriched-record. Small validation runs are supported so you can inspect output before scaling a schedule.

• recall-alert: Charge when Cosmetics Recall Monitor produces Change Alert. Typical price: $0.043. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• dataset-processed: Base charge when Cosmetics Recall Monitor writes a non-empty default dataset. Typical price: $0.011. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• record-saved: Charge for each buyer-visible result saved by Cosmetics Recall Monitor. Typical price: $0.003. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• enriched-record: Charge when Cosmetics Recall Monitor adds match scoring, source evidence, or enrichment to a saved result. Typical price: $0.022. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• first-run-cap: Recommended first run budget cap. Typical price: $3.820. Start with the default small run, inspect the dataset, then raise maxItems or schedule recurring runs.

API example

curl-X POST "https://api.apify.com/v2/actors/zentrafoundry~cosmetics-recall-monitor/runs"\
+ -H"Authorization: Bearer $APIFY_TOKEN"\
+ -H"Content-Type: application/json"\
+ -d'{"maxItems":10,"sourceIds":["SAFETY-GATE","ICSMS"],"includeSourceUrls":true,"includeMatchReasons":true,"outputMode":"buyer-ready-records"}'

Recommended first run

{
"maxItems":10,
"sourceIds":[
"SAFETY-GATE",
"ICSMS"
],
"includeSourceUrls":true,
"includeMatchReasons":true,
"outputMode":"buyer-ready-records"
}

Sample output

Review a static sample output record before running the actor: https://zentraforge.store/external/actor-review/samples/cosmetics-recall-monitor.json

Recommended public tasks

[
{
"name":"First 10 qualified records",
"description":"Low-cost validation run for checking output quality and source fit.",
"input":{
"maxItems":10,
"sourceIds":[
"SAFETY-GATE",
"ICSMS"
],
"includeSourceUrls":true,
"includeMatchReasons":true,
"outputMode":"buyer-ready-records",
"actorSlug":"cosmetics-recall-monitor"
}
},
{
"name":"Daily monitoring feed",
"description":"Recurring small batch for new buyer-value records.",
"schedule":"Daily during local business hours",
"input":{
"maxItems":25,
"sourceIds":[
"SAFETY-GATE",
"ICSMS"
],
"includeSourceUrls":true,
"includeMatchReasons":true,
"outputMode":"buyer-ready-records",
"actorSlug":"cosmetics-recall-monitor"
}
}
]

Use cases

• Track new cosmetics recall opportunities without checking each source manually.
• Route qualified records into CRM, spreadsheets, or internal review queues.
• Monitor deadlines, buyer names, source links, and match reasons for faster triage.
• Schedule recurring runs to catch new signals while keeping first-run costs low.

Trust and compliance

• Uses EU Safety Gate alerts, EU ICSMS.
• Designed for public-source procurement and data-intelligence workflows.
• Keeps source URLs and source identifiers in output records for auditability.
• Does not require private credentials unless a source is explicitly configured for approved authenticated access.

Limitations

• Results depend on public-source availability, source uptime, and source update cadence.
• Public sources can revise records after publication; rerun scheduled tasks for fresh evidence.
• Scores and match reasons are decision-support signals, not legal, financial, procurement, or compliance advice.
• Large production runs can cost more than the default smoke run; start small, inspect output, then scale schedules.

FAQ

Can I run this without URLs? Yes. The default sample mode is designed to succeed without user-supplied URLs, and URL-backed runs can use startUrls when needed.

Can I schedule it? Yes. Use sinceLastRun, watchlistTerms, and optional webhookUrl to turn the actor into a recurring alert or report workflow.

How do I verify value before scaling? Run the recommended first-run input, review the sample output fields, then increase maxItems or schedule recurring runs after the dataset matches your use case.