US WARN Layoff Monitor 🇺🇸 (plant closings & mass layoffs)
Pricing
from $3.50 / 1,000 notice founds
US WARN Layoff Monitor 🇺🇸 (plant closings & mass layoffs)
Every new US WARN Act layoff and plant-closing notice from state workforce agencies, normalized to one clean schema: company, location, employees affected, notice and layoff dates. Filter by state, keyword and size; monitor mode alerts on only-new notices with a Slack digest.
Pricing
from $3.50 / 1,000 notice founds
Rating
0.0
(0)
Developer
Tagada Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
US WARN Layoff Monitor
Track US layoffs and plant closings the day the notice is filed. Under the WARN Act, employers must give advance notice of mass layoffs and closures to their state, and each state publishes those notices. This actor reads them straight from the state workforce agencies and returns every notice as one clean row: the company, where it is, how many jobs are affected, and the notice and layoff dates. Every state uses different columns and file formats; this actor normalizes them all to the same schema so you can work with one dataset instead of fifty.
No API key. You only pay for notices you actually get back.
Who uses this
- Recruiters and staffing firms reaching soon-to-be-available talent before anyone else does.
- Outplacement and career-transition providers finding affected employers the week the notice lands.
- Investors and analysts reading layoffs as a distress and macro signal, company by company.
- B2B sales and RevOps watching for accounts in change, and for new prospects in a region.
- Journalists and researchers who want the raw WARN record as tidy data.
What you get
One record per WARN notice:
| Field | Description |
|---|---|
company | Employer named on the notice |
state / stateCode | Which state filed it |
city, county, address, zip | Where the layoff happens, as detailed as the state publishes |
affectedEmployees | Number of jobs affected |
noticeDate | Date the notice was filed |
effectiveDate | Date the layoff or closure takes effect |
layoffType | Layoff, closure, temporary furlough etc., as the state classifies it |
industry | Industry or NAICS, where the state provides it |
sourceUrl | The state page the record came from |
isNew | In monitor mode, whether the notice is new since the last run |
Covered states
California, New Jersey, Maryland, Indiana, Alaska, South Dakota and the District
of Columbia, with more states being added. Leave the states input empty to
pull them all, or pick a subset.
Input examples
Recent layoffs in California and New Jersey affecting 50+ people:
{"states": ["CA", "NJ"],"sinceDays": 30,"minAffected": 50}
Everything filed in the last week, all states:
{"sinceDays": 7}
Scheduled monitor that posts new manufacturing layoffs to Slack:
{"keywords": ["manufacturing"],"sinceDays": 3,"monitorMode": true,"webhookUrl": "https://hooks.slack.com/services/XXX/YYY/ZZZ"}
How monitor mode works
Turn on monitorMode and schedule the actor (daily is typical). The first run
records what is already published as a baseline. Every run after that returns,
and charges for, only notices that are new since the previous run, and posts
them to your webhook if you set one. A daily run costs you a handful of new
notices, not the whole archive each time.
Pricing
Pay per event, no subscription. Users on higher Apify plans get automatic discounts.
| Event | Price | When |
|---|---|---|
| Run started | $0.005 | Flat, once per run |
| Notice found | $0.005 | Per new/matched WARN notice returned with its data |
| Digest sent | $0.03 | Monitor mode only, per Slack/webhook digest actually posted |
A thousand notices costs $5, platform usage included. In monitor mode the persistent seen-set means you are never billed twice for the same notice, so a quiet scheduled run only pays the small run fee.
FAQ
Where does the data come from? Each state's own workforce-agency WARN page. These are public records the states are required to publish.
Why only these states? Every state publishes in a different format, from clean spreadsheets to hand-maintained web pages, so each one is added deliberately once its feed is normalized reliably. The list grows over time.
How complete is each notice? As complete as the state publishes. Some states give a full address and industry code; others give only company, count and date. Missing fields are left empty rather than guessed.
Do I need an API key or account? No. Nothing to set up.
How far back can I go? Set sinceDays to a large number, or to 0 for each
state's full published history. A daily monitor only needs a few days.
WARN Act notices, layoff data, mass layoff monitor, plant closing notices, WARN notice scraper, layoff tracker, state WARN database, workforce reduction alerts, layoff leads, distressed company signal.