Food Supplements Recall Monitor

Monitor EU Safety Gate alerts and return product, brand, risk, authority, market, source URL, and business-action fields.

What this Actor does

What it does

• Processes configured public sources or user-provided records for focused food supplements recall monitoring.
• Emits structured rows with source references, stable identifiers, confidence, warnings, and run summary fields.
• Supports sample-mode runs so Apify Store QA and first-time users can inspect output without depending on live third-party availability.

What it does not do

• Does not scrape private, login-only, paywalled, or access-restricted data unless the user provides approved credentials for a source they control.
• Does not guarantee every field is available from every source; missing or blocked fields are returned as warnings or nulls.
• Does not make legal, financial, compliance, procurement, medical, safety, or regulatory decisions.

Who this is for

Marketplaces, sellers, importers, distributors, catalog teams, and compliance operators use this actor when they need focused food supplements recall output instead of a broad generic scraper or manual checking.

Buyer outcomes

• Catch food supplements recall product-risk signals before manual checks miss catalog or marketplace exposure.
• Prioritize review with product, brand, risk type, authority, affected market, severity, dates, and source URL.
• Route source-backed decision-support alerts into compliance, catalog, seller, or importer workflows.

Data sources

Sources monitored

• EU Safety Gate alerts

Input

• sourceMode: use sample for a smoke run or configured official recall/safety source modes.
• startUrls: official alert, authority, recall, market-surveillance, or product-safety URLs when URL-backed lookup is supported.
• sourceIds: approved official recall, safety, medical-device, or compliance source identifiers.
• maxItems: bounded number of alert records to return.
• sinceLastRun: emit only new or updated safety alerts when scheduled.
• watchlistTerms: brand, product type, model, marketplace category, hazard, country, or authority keywords.
• webhookUrl: optional destination for compliance, catalog, seller, or importer review.

How it transforms the input

• Input: official safety alert, recall, product-risk, medical-device, market-surveillance, or authority record.
• Transformation: normalize product, brand, risk, authority, affected market, severity, dates, and evidence fields.
• Output: source-backed alert record with recommended business action and decision-support context.

Output

The actor returns recall and safety alert records with product, brand, risk type, authority, affected market, severity, dates, source URL, and recommended business action.

Family-specific fields to expect:

• alertId: Official alert or recall identifier.

• productName: Affected product name.

• brand: Brand or manufacturer when available.

• category: Product category.

• hazard: Hazard, defect, or risk description.

• riskLevel: Severity or risk level used for triage.

• country: Affected country or market.

• authorityAction: Recall, withdrawal, warning, corrective action, or authority note.

• sourceUrl: Official alert record URL.

• recordId: Stable record ID for exports, dedupe, and downstream joins.

• title: Human-readable record title for review and export.

• 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 Food Supplements 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 Food Supplements 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 Food Supplements 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 Food Supplements 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~food-supplements-recall-monitor/runs" \
+  -H "Authorization: Bearer $APIFY_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"maxItems":10,"sourceIds":["SAFETY-GATE"],"includeSourceUrls":true,"includeMatchReasons":true,"outputMode":"buyer-ready-records"}'

Demo run

Recommended first run

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

Sample output

Sample status: sample_unavailable at https://zentra.nimblique.studio/external/actor-review/samples/food-supplements-recall-monitor.json. No fake sample is published; run a bounded real sample refresh before using examples in promotion.

Recommended public tasks

[
    {
        "name": "Review 10 safety alert matches",
        "description": "Low-cost validation run for checking product, brand, risk, authority, and source fields.",
        "input": {
            "maxItems": 10,
            "sourceIds": [
                "SAFETY-GATE"
            ],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "food-supplements-recall-monitor"
        }
    },
    {
        "name": "Daily recall and safety review",
        "description": "Recurring batch for new official recall, safety, or compliance-risk alerts.",
        "schedule": "Daily during local business hours",
        "input": {
            "maxItems": 25,
            "sourceIds": [
                "SAFETY-GATE"
            ],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "food-supplements-recall-monitor"
        }
    }
]

Example use cases

• Monitor food supplements recall recalls and safety alerts without checking authority portals manually.
• Route high-risk product, brand, market, or category matches to compliance and catalog teams.
• Keep source URLs and authority context attached for review.
• Support marketplace, importer, seller, or distributor triage with decision-support signals.

Trust and compliance

• Uses EU Safety Gate alerts.
• 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.
• Recall, safety, and compliance outputs are decision support only, not legal or regulatory advice.

Reliability and QA

• Prefilled Apify Store QA input runs in sample mode and should finish within the automated quality window.
• Empty input is handled with deterministic sample or diagnostic output instead of a crash.
• Demo/sample runs suppress buyer-value charges while still writing representative dataset rows.
• Production runs use bounded maxItems, source references, warnings, and run summaries so blocked or changed targets are visible.

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, medical, safety, or regulatory advice.
• Large production runs can cost more than the default smoke run; start small, inspect output, then scale schedules.

Legal and responsible use

Use this Actor only for public data or data you are authorized to process. You are responsible for complying with applicable laws, marketplace terms, robots policies, privacy rules, and source-specific limits.

Support

Open an issue on the Actor page with the run ID, input summary, expected result, and observed result. Do not include secrets, cookies, auth headers, or private account data.

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.