Make ・ HHS OCR ・ breach digests

How to use HHS Healthcare Data Breach Change Scraper in Make

HHS Healthcare Data Breach Change Scraper (taroyamada/data-breach-disclosure-monitor) runs inside Make through Apify's official module. For overnight portal checks, prefer trigger Watch Actor Runs, then Get Dataset Items, and map disclosure digests into Sheets or Slack. Short proof runs can use Run an Actor with sync only when they fit Make's plan timeout. Listing: $10.00 / 1,000 healthcare breach change rows ($0.01 per successfully delivered new or changed public HHS breach disclosure row).

Open HHS Healthcare Data Breach Monitor Input on Apify Store

Last updated: 2026-10-30 (Asia/Tokyo). Integration steps verified on Apify docs the same day.

What this scenario does

Make watches finished runs of the HHS OCR Breach Portal monitor, then exports source-linked disclosure digests (affected-entity counts, incident types, change evidence). It tracks newly published portal disclosures. It does not query Google News and does not accept article URL lists.

PieceRole
Make Apify moduleOfficial Apify app on Make (docs.apify.com/platform/integrations/make)
Actortaroyamada/data-breach-disclosure-monitor — public HHS OCR breach digests
First proof inputlookbackDays 30; minIndividualsAffected 500; datasetMode all
Useful fieldsEntity name, state, individuals affected, incident type, change evidence, source links

Connect Apify to Make

Steps below match Apify's Make integration doc read on 2026-10-30.

  1. In a Make scenario, search the module bar for Apify and add a module.
  2. Open Connection. Prefer OAuth. Or paste an Apify API token from Console Settings → API & Integrations.
  3. Save the connection.

Asynchronous path (scheduled portal checks)

  1. Start the Actor from Apify Console, a schedule, or another scenario with the input below.
  2. In Make, add trigger Watch Actor Runs for taroyamada/data-breach-disclosure-monitor.
  3. Add Get Dataset Items. Map Dataset ID from the trigger's default dataset variable.
  4. Map entity, state, individuals affected, and source URL fields into Google Sheets, Slack, or your SIEM webhook.

Suggested first input:

{
  "lookbackDays": 30,
  "entityKeywords": "",
  "stateFilter": "",
  "minIndividualsAffected": 500,
  "maxBreachesInEvidence": 50,
  "watchTerms": "",
  "requestTimeoutSeconds": 45,
  "delivery": "dataset",
  "datasetMode": "all",
  "notifyOnNoChange": false,
  "snapshotKey": "hhs-breach-monitor-snapshots",
  "dryRun": false
}

Synchronous path (short proofs only)

  1. Add Run an Actor. Select the same Actor. Set Run synchronously to Yes only when you expect the run to finish inside Make's plan timeout.
  2. If the run may exceed the timeout, use the async path above instead (Apify documents a hard sync timeout that varies by Make plan).
  3. Add Get Dataset Items using the Run module's default dataset ID, then map the same fields.

Make's listed Apify actions also include Run a Task, Scrape Single URL, and Make an API Call; searches include Get Dataset Items. Triggers: Watch Actor Runs and Watch Task Runs.

Not this path

Related pages

Actor facts on this page come from this site's published listing pages. Integration steps come from Apify's public docs read on 2026-10-30 (Asia/Tokyo): Make, Zapier, n8n. Confirm live Store input and pricing before you run.