May’d It

WORKFLOW / Supplier research

Create an FDA warning-letter review queue

Keep posting dates, issue dates and official letter links separate in a small supplier-research review queue.

5 saved observationsObserved October 18, 2026 UTCManual execution

REAL RECORDS / DATED EVIDENCE

Which published letter records need a human review?

Saved at 2026-10-18T13:05:18.735Z from build 1.0.1. This preview makes no live requests.

Selected fields from the saved bounded sample
Marcs Cms IdPosted DateLetter Issue DateHas Posted ResponseHas Posted Closeout
7345382026-10-132026-10-05falsefalse
7292232026-10-132026-09-11falsefalse
7301542026-10-132026-09-11falsefalse
7358592026-10-132026-10-02falsefalse
7251362026-10-132026-10-06falsefalse

FROM DATA TO A REVIEW QUEUE

Five practical steps

  1. Begin with the documented recent table window: read up to 25 source records and save five. Treat this as a workflow demonstration.
  2. Keep both postedDate and letterIssueDate. Use the former for publication discovery and the latter for the document’s chronology.
  3. Open the official letter and any linked response or closeout. A false posted-link flag does not establish that no response occurred.
  4. Join exact entity identifiers to your supplier master only after checking the company identity; a literal name match is a candidate, not a confirmed match.
  5. Keep a reviewed-on date and reviewer notes. Increase the source window deliberately for real research; this sample cannot provide complete supplier history.

Destination key: letterUrl. Keep an audit trail and preserve prior rows when a later sample is empty.

TWO WAYS TO START

Run in Apify or download the starter

Use Apify Console

  1. Open the Actor, switch to JSON input and paste the example below.
  2. Review current pricing, use your own account, and set a $0.05 maximum run charge.
  3. Run manually. Review SUMMARY and results before exporting CSV into your review sheet.
Open Actor on Apify ↗

Exact sample input

{
  "sortBy": "postedDate",
  "maxSourceRecords": 25,
  "maxResults": 5,
  "maxRunSeconds": 120
}

Download a repeatable runner

Save these three files in one folder. The Node.js 22+ starter needs no npm packages. Add your own Apify token through your environment; the downloads contain no credentials.

node run-workflow.mjs --run

Execution is explicit and can incur charges. The starter saves local CSV/JSON, checks run status and coverage, and supports resuming an existing run. Connect your own spreadsheet after reviewing the output. It does not enable a schedule or send notifications.

A SMALL, EXPLAINED START

What this sample would cost at listed event rates

$0.01505

5 results × $0.003 per result, plus $0.00005 Actor Start at the FREE-tier rates observed October 18, 2026. This is a modeled event charge, not a bill or a complete account-cost estimate. Platform/API/storage usage and plan rates may differ.

The runner requests a $0.05 maximum charge. A cap can stop collection early. Check current pricing ↗.

Keep the source’s meaning

  • The source window and result cap omit records, and records tied on posting date can move at the boundary.
  • The Actor reads table metadata, not letter bodies.
  • Do not infer present compliance, product safety, or supplier eligibility from these observations.

Read the full Actor guide for fields and scope. See the dated report for what this specific sample supports.