US WARN Layoff Notice Aggregator & Delta Monitor

Aggregate US state WARN Act layoff & plant-closure notices into one normalized schema, and get a delta feed of exactly what changed since your last run: new notices, updated notices (employee count / effective date / type revised), and removed notices.

Every state publishes WARN filings in a different shape (Socrata, CSV, HTML, Excel) with different column names and layoff-type wording. This actor unifies them so you can monitor layoffs across states from a single, stable dataset — no logins, no API keys.

Who it's for

• RevOps & recruiting / staffing — catch fresh layoffs the day they're filed to source candidates or reach affected employers before competitors.
• Economic & labor-market researchers — build a clean cross-state layoff time series without hand-scraping each agency portal.
• Commercial real estate (CRE) & site selection — flag closures that free up facilities and shifts in regional employment.
• Investors & risk / supply-chain teams — track distress signals by company, county and sector.

Coverage

State	Source	Status
OR Oregon	Socrata data.oregon.gov (ijbz-jpx8)	Live — fully wired
TX Texas	Socrata data.texas.gov (8w53-c4f6)	Live — fully wired (current calendar year)
CA California	EDD WARN report (HTML/Excel)	Coming later
NY New York	NY DOL WARN (HTML)	Coming later
WA Washington	ESD WARN (Excel)	Coming later
WI Wisconsin	DWD WARN (HTML)	Coming later
IL Illinois	DCEO WARN (HTML/PDF)	Coming later
NJ New Jersey	NJ DOL WARN (HTML)	Coming later

Adding a state is a single config block ({ state, format, domain, datasetId, map }) in source.js, so coverage expands without touching the core logic. States marked "coming later" publish only HTML/Excel/PDF today; they are scaffolded config blocks and return no data until a parser is wired.

Example input — snapshot

{
  "states": ["OR", "TX"],
  "mode": "snapshot",
  "sinceDate": "2026-01-01",
  "maxResults": 100000
}

Example input — delta (scheduled monitoring)

{
  "states": ["OR", "TX"],
  "mode": "delta",
  "priorKvKey": "warn_last_snapshot"
}

In delta mode with priorKvKey, the actor diffs against the snapshot stored under that key and saves the current snapshot back to it — so a daily schedule emits only what changed. Alternatively pass the prior records directly as priorItems.

Output fields

state, company, city, county, notice_date, effective_date, employees_affected, layoff_type (layoff/closure/relocation), industry, region, notice_id, source_url, retrieved_at. Dates are normalized to YYYY-MM-DD.

In delta mode each row also carries change_type (new | updated | removed) plus old_* / new_* for employees_affected, effective_date and layoff_type.

Use as an MCP tool

This actor is callable by AI agents (Claude, Cursor, etc.) via mcp.apify.com. The clean, field-level output schema makes it a good chainable tool: an agent can pull a state's WARN notices, filter by company, county or headcount, and hand rows to an outreach, enrichment or analysis step.

FAQ

How do I monitor for new layoff notices? Run in delta mode on a schedule with a priorKvKey; each run emits only new / updated / removed rows.

Which states are live today? Oregon and Texas are fully wired via their keyless Socrata open-data APIs. California, New York, Washington, Wisconsin, Illinois and New Jersey are scaffolded and coming in a later version (their filings are HTML/Excel/PDF only).

What counts as an "updated" notice? The employee count, effective date, or layoff type changed versus the prior snapshot.

Do I need an API key? No. All sources are public and keyless.

How is it billed? Pay per result — one WARN notice (or one delta change row) = one dataset item.