WARN Layoff Notices Scraper: 8 States + New-Only Alerts avatar

WARN Layoff Notices Scraper: 8 States + New-Only Alerts

Pricing

from $0.56 / 1,000 warn notice returneds

Go to Apify Store
WARN Layoff Notices Scraper: 8 States + New-Only Alerts

WARN Layoff Notices Scraper: 8 States + New-Only Alerts

WARN layoff notices scraper for WARN Act layoffs and plant closures from 8 official state sources (TX, CA, WA, OR, MD, VA, NC, MI) in one schema. Filter by notice date, workers affected, closures only. Employer, headcount, city, county, dates, closure flag, source link. New-only mode for alerts.

Pricing

from $0.56 / 1,000 warn notice returneds

Rating

0.0

(0)

Developer

Detroit Web Agent - Open Data

Detroit Web Agent - Open Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

0

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

WARN Layoff Notices: layoff data plus employer contacts

WARN Layoff Notices Scraper: 8 States + New-Only Alerts

WARN Act layoff notices and plant closures from 8 US states (TX, CA, WA, OR, MD, VA, NC and MI) in one clean table, with a new-only alert mode for scheduled runs.

Free sample: download a CSV of real rows from recent runs of this Actor (up to 50 rows, refreshed weekly, no account needed).

Video walkthrough: Watch the 1-minute demo on YouTube

WARN Layoff Notices output preview: real run results as a table

One clean table of WARN Act layoff and closure notices from Texas, California, Washington, Oregon, Maryland, Virginia, North Carolina and Michigan: employer, workers affected, city, county, notice date, layoff date, closure flag and a link back to the state source. Schedule it and each run returns only the notices you have not seen yet.

  • What you get: one row per WARN notice, read from the official state publication, in a single schema across all 8 states.
  • Who it is for: recruiters and staffing firms, outplacement and benefits providers, B2B sales teams, journalists, investors and labor-market researchers.
  • What it costs: $0.00093 per notice delivered on the Apify free plan, which is $0.93 per 1,000 notices ($0.56 to $0.74 per 1,000 on paid Apify plans). No monthly fee, no run fee. Optional employer domain and phone enrichment (with your own Apollo key) is a separate $0.05 per enriched employer on the free and Bronze plans ($0.035 to $0.0425 on higher plans).
  • What you need: an Apify account. No state login, no API key.

One real row, from our run on Oct 16, 2026 (Michigan):

EmployerCityCountyStateWorkersNotice dateLayoff dateTypeClosure
Lear CorporationSterling HeightsMacombMI672026-10-082026-11-09Facility closure - Not reportedtrue
  • In short: WARN Layoff Notices (Apify actor transparent_meteorite/warn-layoff-alerts) returns WARN Act layoff and plant-closure notices from official state sources (Texas, California, Washington, Oregon, Maryland, Virginia, North Carolina, Michigan) as clean, deduplicated rows.
  • Who it is for: recruiters and staffing firms, outplacement and benefits vendors, B2B sales teams, journalists, investors and labor researchers.
  • Input: states (TX, CA, WA, OR, MD, VA, NC, MI), days back or an exact notice-date window, minimum affected workers, closures-only filter, only-new-since-last-run mode and webhook.
  • Output: employer, clean employer name, workers affected, size bucket, closure flag, layoff type, city, county, state, notice date, layoff date, days from notice to layoff, notice link, source state and source link.
  • Price: $0.00093 per notice ($0.93 per 1,000) on the Apify free plan, $0.00056 to $0.00074 on paid plans; optional employer enrichment with your own Apollo key at $0.05 per enriched employer ($0.035 to $0.0425 on Silver and higher plans). Pay per result, no subscription.
  • Limits: eight states today (other codes are skipped with a log note); data is only as fresh as each state publishes it.

Key facts

  • Actor name: WARN Layoff Notices
  • Actor ID: transparent_meteorite/warn-layoff-alerts
  • Store page: https://apify.com/transparent_meteorite/warn-layoff-alerts
  • Data source: official state WARN publications: data.texas.gov, California EDD, Washington ESD, Oregon HECC, Maryland Department of Labor, Virginia VEC (VirginiaWorks), North Carolina Commerce, Michigan LEO
  • Pricing model: pay per event (warn-notice $0.00056 to $0.00093, enriched-contact $0.035 to $0.05, by Apify plan)
  • Output formats: JSON, CSV, Excel, XML, HTML table, RSS (Apify dataset)
  • Access: Apify Console, REST API, JavaScript/Python clients, schedules, webhooks, Apify MCP server
  • Login or third-party API key needed: no, only an Apify account
  • Also known as: WARN notices scraper, WARN Act tracker, layoff data API, layoff alerts, mass layoff notices, plant closure notices
  • Maintainer: transparent_meteorite (independent developer)
  • Last updated: 2026-10-19

What is a WARN notice, and why the data is hard to use

The federal Worker Adjustment and Retraining Notification (WARN) Act requires most employers with 100 or more employees to give 60 days' written notice before a plant closing or a mass layoff. The notice goes to the state's dislocated-worker unit, and many states then publish those notices.

The catch is that every state publishes them differently. Texas uses an open-data portal. California posts a spreadsheet for the current quarter. Washington runs a searchable database. Oregon keeps a tracker. Maryland, Virginia and North Carolina publish web tables, and Michigan posts notices on a search page with a PDF per filing. Column names, date formats and layoff-type wording all differ, and none of them tells you which notices are new since you last looked.

This actor reads each official source, maps every notice to one schema, removes duplicates, and remembers what it already delivered to you. You get a table you can filter, schedule, export or push to a webhook, instead of eight browser tabs and a copy-paste routine.

Run in 30 seconds

  1. Open the prefilled run (free Apify account; it creates a saved task with a working input).
  2. Press Start. The input is small on purpose, so the first run is quick and costs a few cents at most.
  3. Open the Output tab, switch to Table view, download as CSV, Excel or JSON.

Prefilled input:

{
"states": [
"CA"
],
"daysBack": 60,
"onlyNewSinceLastRun": false,
"minLayoffCount": 0,
"maxResults": 3,
"webhookUrl": "",
"webhookBatchSize": 100
}

Ready-made presets by use case (each opens as a saved task you can edit):

Output fields

One row per notice. Fields a state does not publish come through as null, never as a guess.

FieldWhat it holdsExample
companyEmployer name exactly as filedLear Corporation
employer_cleanEmployer name without legal suffix, site names or datesLear
layoff_countWorkers affected, as filed67
size_bucket1-49, 50-99, 100-499 or 500+50-99
city, county, stateLocation of the layoffSterling Heights, Macomb, MI
notice_dateDate of the notice2026-10-08
layoff_dateFirst layoff or effective date2026-11-09
received_dateDate the state received it (where published)2026-10-08
notice_to_layoff_daysLead time between notice and layoff32
days_since_noticeAge of the notice when the run happened8
layoff_typeThe state's own type wordingFacility closure - Not reported
is_closuretrue for closure, shutdown or relocation; null where the state publishes no type (TX)true
notice_urlLink to the filed notice where the state publishes one (MI, VA, WA, OR)michigan.gov PDF
wdaLocal workforce development area (TX)North Central Texas WDA
source_state, source_urlWhich official source the row came fromMI, michigan.gov WARN notices page
scraped_atISO timestamp of the run2026-10-16T04:31:38.524Z
company_domain, company_phone, company_industry, enrichedFilled only when you add your own Apollo keynull unless enriched

Export as CSV, Excel, JSON, XML or an HTML table from the Output tab, read it from the API, or have each batch POSTed to a webhook.

Example output

These are real rows from this actor's own scheduled runs. Nothing below is edited except for column selection.

EmployerCityCountyStateWorkersNotice dateLayoff dateLayoff typeRun date
The Neil Jones Food Company dba TomatekFirebaughFresnoCA1162026-10-142026-12-14Layoff Temporary2026-10-19
ServiceNow, Inc.Santa ClaraSanta ClaraCA22026-10-132026-12-14Layoff Permanent2026-10-19
HealthEdge, d/b/a as UST HealthProofDetroitWayneMI532026-10-082026-12-01Permanent layoff - Operations transferred2026-10-16
Lear CorporationSterling HeightsMacombMI672026-10-082026-11-09Facility closure - Not reported2026-10-16
Dakkota Integrated Systems, LLCLansingClintonMI672026-09-092026-12-31Closure - Not available2026-10-16

One complete row as JSON (run of Oct 19, 2026):

{
"company": "The Neil Jones Food Company dba Tomatek",
"city": "Firebaugh",
"county": "Fresno",
"state": "CA",
"layoff_count": 116,
"notice_date": "2026-10-14",
"layoff_date": "2026-12-14",
"received_date": "2026-10-14",
"wda": null,
"layoff_type": "Layoff Temporary",
"notice_url": null,
"source_state": "CA",
"source_url": "https://edd.ca.gov/en/jobs_and_training/Layoff_Services_WARN",
"is_closure": false,
"employer_clean": "The Neil Jones Food Company",
"notice_to_layoff_days": 61,
"days_since_notice": 5,
"size_bucket": "100-499",
"scraped_at": "2026-10-19T11:30:09.665Z",
"company_domain": null,
"company_phone": null,
"company_industry": null,
"enriched": false
}

Notice how the same row tells you three things at a glance: the layoff is 61 days after the notice (the WARN minimum is 60), it is a temporary layoff rather than a closure, and the employer's clean name is ready for a CRM lookup.

Example inputs from real runs

Each input below was used in a real run of this Actor in October 2026. Paste one into the Input tab (JSON view) to start from it.

1. WARN notices in 7 states, last 120 days (that run returned 60 rows)

{
"states": [
"TX",
"CA",
"WA",
"OR",
"MD",
"VA",
"NC"
],
"daysBack": 120,
"maxResults": 60,
"onlyNewSinceLastRun": false,
"minLayoffCount": 0,
"minAffectedWorkers": 0,
"onlyClosures": false
}

2. Michigan WARN notices, new since last run (that run returned 10 rows)

{
"states": [
"MI"
],
"daysBack": 365,
"maxResults": 10,
"onlyNewSinceLastRun": true,
"minLayoffCount": 0,
"minAffectedWorkers": 0,
"onlyClosures": false
}

3. Washington plant closures with 20+ workers (that run returned 3 rows)

{
"states": [
"WA"
],
"daysBack": 365,
"onlyNewSinceLastRun": false,
"onlyClosures": true,
"minAffectedWorkers": 20,
"maxResults": 3,
"minLayoffCount": 0
}

4. Texas WARN notices, last year (that run returned 5 rows)

{
"states": [
"TX"
],
"daysBack": 365,
"maxResults": 5,
"onlyNewSinceLastRun": false,
"minLayoffCount": 0
}

5. California WARN notices, last 60 days (that run returned 5 rows)

{
"states": [
"CA"
],
"daysBack": 60,
"maxResults": 5,
"onlyNewSinceLastRun": false,
"minLayoffCount": 0,
"minAffectedWorkers": 0,
"onlyClosures": false
}

Input

InputWhat it doesDefault
states2-letter codes: TX, CA, WA, OR, MD, VA, NC, MI. Other codes are skipped with a log note["TX"]
daysBackNotices with a notice date in the last N days (1-365)365
noticeDateFrom, noticeDateToExact notice-date window, YYYY-MM-DD; overrides daysBackempty
minAffectedWorkersOnly notices affecting at least N workers (minLayoffCount is the same filter, kept for older tasks; the larger applies)0
onlyClosuresOnly closure, shutdown or relocation notices (needs a state that publishes a type, so TX rows are skipped)off
onlyNewSinceLastRunSkip notices already delivered in earlier runs, matched by employer + notice date + cityon
maxResultsHard cap on notices returned and charged in this run100
apolloApiKeyYour own Apollo.io key: adds employer domain, main phone and industry (company level only)empty
socrataAppTokenFree data.texas.gov app token, only for very frequent Texas pullsempty
webhookUrl, webhookBatchSizePOST delivered notices as JSON batches { source, count, records }empty / 100

Nothing is required: an empty input runs Texas for the last year with the defaults above.

Input recipes

Large layoffs only, Texas, last year:

{ "states": ["TX"], "daysBack": 365, "minAffectedWorkers": 100, "maxResults": 200 }

Exact date window, closures only, at least 50 workers:

{ "states": ["WA", "CA", "MI"], "noticeDateFrom": "2026-09-01", "noticeDateTo": "2026-09-30", "onlyClosures": true, "minAffectedWorkers": 50, "onlyNewSinceLastRun": false }

Weekly alert feed for all eight states into a webhook (schedule it weekly):

{ "states": ["TX", "CA", "WA", "OR", "MD", "VA", "NC", "MI"], "daysBack": 30, "onlyNewSinceLastRun": true, "webhookUrl": "https://your-endpoint.example/warn" }

With employer domain and phone (uses your own Apollo key):

{ "states": ["TX"], "daysBack": 90, "apolloApiKey": "YOUR_APOLLO_KEY", "maxResults": 50 }

Example

Input example

{
"states": [
"CA"
],
"daysBack": 60,
"maxResults": 5,
"onlyNewSinceLastRun": false
}

Sample output

Three real rows from a recent run of this Actor. Personal data is masked, some fields are left out and long values are shortened for readability.

[
{
"company": "JPMorgan Chase & Co.",
"city": "Plano",
"state": "TX",
"layoff_count": 244,
"notice_date": "2026-06-23",
"layoff_date": "2026-08-21",
"size_bucket": "100-499",
"source_state": "TX",
"source_url": "https://data.texas.gov/d/8w53-c4f6"
},
{
"company": "The Neil Jones Food Company dba Tomatek",
"city": "Firebaugh",
"state": "CA",
"layoff_count": 116,
"notice_date": "2026-10-14",
"layoff_date": "2026-12-14",
"size_bucket": "100-499",
"source_state": "CA",
"source_url": "https://edd.ca.gov/en/jobs_and_training/Layoff_Services_WARN"
},
{
"company": "ServiceNow, Inc.",
"city": "Santa Clara",
"state": "CA",
"layoff_count": 2,
"notice_date": "2026-10-13",
"layoff_date": "2026-12-14",
"size_bucket": "1-49",
"source_state": "CA",
"source_url": "https://edd.ca.gov/en/jobs_and_training/Layoff_Services_WARN"
}
]

Pricing

Pay per event. You pay only for notices delivered to your dataset.

EventPrice
WARN notice delivered$0.00093 (free plan); $0.00056 to $0.00074 on paid plans
Employer contact enriched (only with your Apollo key, and only when a domain or phone is found)$0.05
You pullYou pay
50 notices$0.15
1,000 notices$0.93 (free plan); $0.56 to $0.74 on paid plans
Every Texas notice of the past year (115 on Oct 5, 2026)$0.35
100 notices with enrichment found for all of them$5.30

Scheduled change: from Oct 30, 2026 the notice price is set to drop to $0.00093 per notice on the Apify free plan and $0.00056 to $0.00074 on paid Apify plans; enrichment stays $0.05 on the free and Bronze plans and drops to $0.035 to $0.0425 on higher plans. The Store page always shows the price in force.

With onlyNewSinceLastRun on (the default), a notice you already received is skipped and never charged again, so a weekly schedule only bills new filings. Use maxResults and the run's Maximum cost setting to cap any single run.

Apify's free plan includes $5 of monthly platform credit, which covers about 5,000 layoff notices with this actor (at $0.00093 per result, plus small platform usage). Paid Apify plans get the same data with no monthly cap; scheduled daily runs stay cheap because each run only returns new records.

What this actor does for you

  • Eight official state sources, one schema. TX, CA, WA, OR, MD, VA, NC and MI notices all come out with the same field names, so one spreadsheet, one CRM import or one dashboard works for every state.
  • Only-new mode for alerts. With onlyNewSinceLastRun on, a notice you already received is skipped and never charged again. A daily or weekly schedule becomes a true alert feed.
  • Filters that match how people search layoffs: a rolling window (daysBack) or an exact notice-date range, a minimum number of affected workers, and a closures-only switch.
  • Fields you would otherwise compute yourself: employer_clean (legal suffixes and dates stripped from the filed name), size_bucket (1-49, 50-99, 100-499, 500+), is_closure, notice_to_layoff_days and days_since_notice.
  • A link back to the source on every row (source_url), plus the filed notice itself (notice_url) where the state publishes one, so every number can be checked.
  • Webhook delivery in batches to n8n, Make, Zapier, Slack bridges or your own endpoint.
  • Clear run messages. When a run finds nothing new, or reaches your maximum cost, the log and run status say so instead of ending silently.
CheckThis actor
States covered8 (TX, CA, WA, OR, MD, VA, NC, MI)
Rows returned in a live test run (Oct 9, 2026)OR 188, CA 356, WA 150, MD 108, VA 1,132, NC 63
Michigan rows in a scheduled run (Oct 16, 2026)3 notices dated Sep 9 to Oct 8, 2026, with PDF links

Measured from this actor's own runs.

Use cases

  • Recruiting and staffing. A notice tells you which employer is releasing how many people, where, and on what date, about two months ahead. Filter by your metro's counties and by minAffectedWorkers, then plan outreach and job fairs before the layoff date.
  • Outplacement, benefits and career-transition services. Employers that file WARN notices have to plan for affected staff. A weekly only-new feed of employers above 50 workers is a ready prospect list, and notice_to_layoff_days shows how much time is left.
  • B2B sales and account monitoring. Watch your customer and pipeline accounts for closures and relocations. Match on employer_clean and push hits to Slack or your CRM with the webhook.
  • Commercial real estate and local economic development. is_closure plus city and county shows where facilities are closing and space may come to market.
  • Journalism. A clean, multi-state table makes it easy to answer "who is cutting jobs in our area this month" and to link back to the filed notice.
  • Investing and research. Track layoff counts by state, county, employer or size bucket over time. The schema is stable, so a monthly export lines up with the last one.
  • Workforce boards and nonprofits. Get every notice in your area the week it is published and route it to the rapid-response team.

State coverage

StateOfficial sourceUpdate cadenceFields
TXdata.texas.gov open datasetIrregular (state feed)employer, city, county, layoff count, notice date, layoff date, received date, workforce area
CAEDD current-quarter WARN report (xlsx)Weeklyemployer, city, county, layoff count, notice date, layoff date, received date, type
WAEmployment Security Department WARN databaseRollingemployer, city, layoff count, notice (received) date, layoff start, type, notice link
ORHECC rapid response trackerRollingemployer, city, layoff count, notice date, type, notice link
MDMaryland DLLR WARN page (current and prior year)Rolling, same week as filingemployer, city, county, layoff count, notice date, effective date, type
VAVirginiaWorks (VEC) WARN notices tableRolling, same week as filingemployer, city, layoff count, notice date, impact date, type, notice PDF link
NCNC Commerce Workforce WARN Summary ListUpdated every few daysemployer, city, county, layoff count, notice date, received date, effective date, type
MIMichigan LEO WARN notices pageAs LEO posts each noticeemployer, city, county, layoff count, notice date, layoff date, type, notice PDF link

Row counts depend on each state's own publication. Some state rows (for example Maryland) have a blank employee count at the source; those come through as null. Oregon's tracker also lists notices for multi-state employers, so some OR-sourced rows have a state outside Oregon; source_state always names the source.

Use it from code

Small real input: it returns only a couple of rows, so a test run costs very little (see Pricing). Set the APIFY_TOKEN environment variable to your token from Apify Console > Settings > API & Integrations.

Python (pip install apify-client)

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = {'states': ['CA'], 'daysBack': 60, 'maxResults': 2, 'onlyNewSinceLastRun': False}
run = client.actor("transparent_meteorite/warn-layoff-alerts").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["company"], item["layoff_count"], item["layoff_date"])

JavaScript / Node.js (npm install apify-client)

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
"states": [
"CA"
],
"daysBack": 60,
"maxResults": 2,
"onlyNewSinceLastRun": false
};
const run = await client.actor('transparent_meteorite/warn-layoff-alerts').call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl (runs the actor and returns the dataset items in one call)

curl -X POST "https://api.apify.com/v2/acts/transparent_meteorite~warn-layoff-alerts/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"states": ["CA"], "daysBack": 60, "maxResults": 2, "onlyNewSinceLastRun": false}'

Use from AI agents (MCP)

WARN Layoff Notices works as a tool for AI assistants through the official Apify MCP server. Add this server URL to any MCP client (Claude Desktop, Claude Code, Cursor, ChatGPT connectors, VS Code):

https://mcp.apify.com/?actors=transparent_meteorite/warn-layoff-alerts

Claude Desktop / Cursor config:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com/?actors=transparent_meteorite/warn-layoff-alerts",
"headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
}
}
}

Then ask in plain language, for example: "List WARN notices in Michigan from the last 30 days with at least 50 workers."

Send results to Google Sheets, Slack, Zapier, Make or n8n

  • Google Sheets: every run's dataset has a CSV export link: https://api.apify.com/v2/datasets/<DATASET_ID>/items?format=csv&clean=true (the dataset ID is on the run's Storage tab). In Sheets, =IMPORTDATA("<that link>") loads it. Anyone with the link can read that dataset, so share it carefully. To export to Google Drive automatically, use the Google Drive integration on the actor's Integrations tab.
  • Zapier: in the Apify app, use the trigger Finished Actor run (or Run Actor as an action) with transparent_meteorite/warn-layoff-alerts, then Fetch dataset items and pass the rows to Google Sheets, a CRM or Slack.
  • Make: the Apify app has Watch Actor Runs, Run an Actor and Get Dataset Items modules; connect them to any Make app.
  • n8n: install the Apify node (@apify/n8n-nodes-apify) and use Run an Actor and get dataset, or the On new Apify event trigger.
  • Clay: add an HTTP API column that calls the run-sync endpoint above.
  • Schedule and webhooks: create a Task with your input, add a Schedule in Apify Console, and either set webhookUrl in the input or add an Apify webhook for when a run finishes.

See the Apify integrations docs for setup steps.

Limitations

  • Eight states today (TX, CA, WA, OR, MD, VA, NC, MI). Other states are added as they publish usable public data.
  • Freshness is set by each state. We cannot deliver notices a state has not released; Texas in particular publishes irregularly.
  • California's public report covers the current quarter only, so older California notices are not in the feed.
  • Company names are as filed. They can include site names or dates; use employer_clean for matching.
  • Some fields are blank at the source, for example employee counts on some Maryland rows, or a layoff type in Texas. Those stay null.
  • Enrichment is company-level and needs your Apollo key. Large or oddly named employers do not always match.

Reliability

Last 30 days, measured from Apify run records (all runs, including our own daily health checks): 30 of 30 finished runs succeeded (100.0%), median run time 2.4 s (90th percentile 6.7 s). Aborted runs (0) are not counted.

Updated 2026-10-11 automatically every week from the run history. Report any failure on the Issues tab with the run URL.

More resources

Works well with

Other actors from Detroit Web Agent - Open Data that pair with this one:

FAQ

Quick answers about coverage, freshness, filtering and cost.

How do I get WARN layoff notices automatically?

Save your input as a Task, add a daily or weekly Schedule, and keep onlyNewSinceLastRun on. Each run returns only notices you have not received before, so the dataset (or your webhook) works as an alert feed with no repeats and no double charges.

Which states are covered?

Texas (TX), California (CA), Washington (WA), Oregon (OR), Maryland (MD), Virginia (VA), North Carolina (NC) and Michigan (MI). Pass any combination in states. There is no national WARN API: each state publishes its own way, often as PDFs or web tables, and each needs its own adapter. If you need another state, open an issue and tell us which.

Is there a WARN notice API?

This actor works as one. Call it from the Apify API (examples above) and get WARN notices from the official state sources as JSON, CSV or Excel, or connect it to an AI assistant through the Apify MCP server.

How current is the data?

Exactly as current as each state's publication. Maryland and Virginia usually post notices the same week they are filed; California's report covers the current quarter and is refreshed weekly. Texas is irregular: on Oct 5, 2026 the newest notice in the Texas feed was dated June 23, 2026, which is why the default window is 365 days. Your next run picks up new filings as soon as a state publishes them.

Can I see only plant closures?

Yes. Set onlyClosures to true. It keeps notices whose filed type says closure, shutdown or relocation. Texas publishes no type, so Texas rows are left out when this filter is on; every other covered state publishes one.

Can I filter out small layoffs?

Yes. Set minAffectedWorkers (for example 100). The older minLayoffCount input does the same thing; when both are set, the larger applies. size_bucket lets you group results afterwards.

Can I get employer contact info from a WARN notice?

Yes, with your own Apollo.io key in apolloApiKey. Each notice then gets the employer's website domain, main phone and industry from a company-level Apollo search. Messy filing names are cleaned first (for example a name with a site or a date in it is reduced to the employer). No personal emails are added. It uses your Apollo credits, and the $0.05 enrichment charge applies only when a domain or phone is actually found.

Is WARN data public?

Yes. WARN notices are public records published by the states. The actor reads the official state sources with no login. The data can still name employers and places, so use it in line with your own legal and privacy obligations.

What happens if a state site is down?

That state is skipped for the run with a clear log line, and the other states still deliver. You are charged only for notices that reach your dataset.

How do I avoid surprise costs?

Set maxResults (a hard cap on notices returned and charged) and the run's Maximum cost. When the cap is reached, the run keeps the rows it already has and the log says the limit was reached.

This Actor vs jungle_synthesizer/warn-layoffs-aggregator: this one adds a new-only alert mode plus notice-date, workers-affected and closures-only filters.

What the free plan gets you

Free plan: about 5,300 WARN layoff notices from your $5 monthly Apify credit (at $0.00093 each, today's price); default settings return about 5 rows. Employer contact enrichment is a separate opt-in charge ($0.05 each on the free plan). Need more? Upgrade your Apify plan or set a higher result limit in the input.


Built and maintained by Detroit Web Agent - Open Data (Detroit, Michigan). Questions, bugs or a field you need: open an issue on this Actor's Issues tab and we will reply there.


Feedback: if this Actor was useful, or if it fell short, an honest review on the Reviews tab helps other users decide. Problems or feature requests: please open an Issue and we usually reply within one business day.

Changelog

  • 2026-10-05: Listing rewrite, Texas source, real example input.
  • 2026-10-06: Added California, Washington and Oregon; new layoff_type and notice_url fields.
  • 2026-10-09: Console example switched to California, last 60 days; Output tab table view; video walkthrough.
  • 2026-10-09: Input sections, status messages, examples.
  • 2026-10-09: Branding: maintained by Detroit Web Agent - Open Data.
  • 2026-10-09: README free-credit note; clear log line and status when your Maximum cost per run is reached.
  • 2026-10-11: Closing log line points to the Issues tab; Reliability section added to this README.
  • 2026-10-13: Added noticeDateFrom/noticeDateTo, minAffectedWorkers, onlyClosures; new fields is_closure, employer_clean, size_bucket, notice_to_layoff_days, days_since_notice, scraped_at; clear message when a run finds no new notices.
  • 2026-10-13: Added a Run in 30 seconds section with a one-click prefilled run link, saved use-case presets and cross-links to pairing actors.
  • 2026-10-19: README rewritten: all eight states (including Michigan) listed consistently, real example rows from October 2026 runs, output field reference, FAQ and limits.
  • 2026-10-25: Listing refresh: new Store icon, README reorganised (overview, data fields, pricing, FAQ) and changelog tab added. No code change.

Volume tier pricing

Price per 1,000 events by Apify plan (paid plans get the lower rate automatically):

EventFreeBronzeSilverGold+
warn-notice$0.93$0.74$0.65$0.56
enriched-contact$50$50$42.5$35