📉 WARN Layoff Monitor — New Mass-Layoff & Closure Alerts

Catch mass layoffs and plant closures the moment they're filed. Under the federal WARN Act, employers must publicly notice large layoffs and closures in advance — and states publish them. This actor polls those public feeds, returns company, location, employees affected, and notice/effective dates, and runs on a schedule to alert you to NEW notices via Slack, email, or webhook.

No login, no anti-bot — every source is a public state record.

---

Why WARN notices are a signal

A new WARN filing is a trigger event for several buyers:

• 🧑‍💼 Recruiters / staffing — qualified talent is about to hit the market in a known location.
• 🤝 Sales / competitive — a competitor (or a competitor's customer) is in distress.
• 🏦 M&A / distressed-asset / restructuring — early signal of a company under pressure.
• 🧰 Outplacement / benefits / services — the affected employer is an active buyer.

WARN data is sold by paid aggregators; this actor builds the same feed from the public state sources, priced pay-per-event.

---

States & sources (validated)

State	Source	Format
TX	Texas TWC WARN dataset (Socrata)	clean JSON
IN	Indiana DWD "Current WARN Notices"	HTML table

More states (CA, OH, NY, WA…) are on the roadmap — the actor uses per-state adapters so coverage grows without breaking your runs. (CA EDD publishes a biweekly Excel report; it's next.)

---

Output (one record per notice)

state · source · company · city · county · employees_affected · notice_date · effective_date · layoff_type (LO/CL where available) · industry · naics · wda · record_id · source_url · is_new · scraped_at

Export to JSON, CSV, Excel, HTML, or RSS — or pull via the Apify API into your CRM, Clay, n8n, or ATS.

---

How to use it

1. Click Try for free.
2. Pick your states and a lookback window (default 30 days).
3. (Optional) set Min employees affected, a keyword, or layoff type.
4. Click Start, then open the Dataset tab.
5. For a live feed: turn on Monitor mode, add a Schedule (e.g. daily), and a Slack/email/webhook.

Quick start

{ "states": ["TX", "IN"], "lookbackDays": 30, "minEmployees": 50 }

Daily monitor

{ "states": ["TX", "IN"], "monitorMode": true, "alertOnNewNotice": true, "slackWebhookUrl": "https://hooks.slack.com/services/…" }

---

Pricing (pay-per-event)

Event	What it covers	Suggested price
lot-scraped	each notice returned	~$3–4 / 1,000
monitor-run-completed	each scheduled watch run	~$0.05 / run
new-lot-detected	each newly-appearing notice	~$0.02 / notice
alert-delivered	each Slack/email/webhook alert	~$0.005 / alert

(Final prices are set on the actor's pricing page.)

---

Notes

• Public state records (employer-level) — no consumer personal data. Review each agency's terms; your use is your call.
• Coverage grows — adapters are per-state; request a state via an issue.
• No double-counting — monitor mode remembers seen notices (per state + filter scope) and emits each once.