WARN Layoff Alerts

Fresh WARN layoff notices the week they're filed: which employer is cutting jobs, how many workers, where, and the dates. Deduped across runs, so a daily or weekly schedule only ever shows you new ones. Optional Apollo enrichment tacks on the employer's domain and phone.

Built for recruiters and staffing firms (a pile of about-to-be-available workers), outplacement and RPO vendors, commercial real estate, and anyone who watches where a market is softening.

What you get (one row per notice)

company, state, city, county, layoff_count, notice_date, layoff_date, received_date, wda, source_state, source_url

company_domain, company_phone, company_industry, enriched

Heads up on coverage (the honest part)

There is no national WARN API. States publish WARN their own way. Texas has a clean public feed and it's wired up and verified here. Other states post HTML tables or PDFs that each need their own adapter, so they're not in yet. If you need a specific state, open an issue and we'll prioritize it. So today this is a Texas WARN feed with the plumbing to grow.

Enrichment (optional)

Set apolloApiKey and each notice gets the employer's domain and phone from an Apollo company lookup (we clean the messy filing name first, e.g. Spirit Airlines (DFW) May 2026 to Spirit Airlines, which roughly 6x'd match rate in testing). We deliberately keep this to company-level signal. Personal/decision-maker email on big WARN employers is hit-or-miss, so we don't pretend otherwise. Enrichment costs Apollo credits and bills a separate event per enriched notice.

Input

Output

Export the Apify dataset as JSON / CSV / Excel, pull it from the dataset API, or set webhookUrl for batched { source, count, records: [...] } POSTs.

Example output

One row per notice (sample, enrichment on):

[
  {
    "company": "Spirit Airlines",
    "state": "TX",
    "city": "Dallas",
    "county": "Dallas",
    "layoff_count": 217,
    "notice_date": "2026-05-30",
    "layoff_date": "2026-07-29",
    "received_date": "2026-05-31",
    "wda": "Dallas County",
    "source_state": "TX",
    "source_url": "https://data.texas.gov/d/8w53-c4f6",
    "company_domain": "spirit.com",
    "company_phone": "+19543587000",
    "company_industry": "airlines/aviation",
    "enriched": true
  }
]

Pricing

Pay per result. One charge per new notice (deduped, so a schedule never bills twice for the same one), plus a small separate charge only when enrichment actually adds a domain or phone.

Where the data comes from

State WARN filings, public record. Texas: data.texas.gov dataset 8w53-c4f6. No gated or personal-consumer data.

FAQ

How do I get new WARN layoff notices automatically?

Schedule it daily or weekly with onlyNewSinceLastRun on. Each run returns only notices filed since the last one, so you get a clean feed of fresh layoffs with no repeats.

Which states have WARN data?

Texas is wired up and verified today. There's no national WARN API, so other states each need their own adapter. Open an issue for a state you need and we'll prioritize it.

Can I get employer contact info from a layoff notice?

Yes, with enrichment on (apolloApiKey). Each notice gets the employer's company domain and phone. We keep it to company-level signal on purpose, since personal email on big WARN employers is unreliable.

How fresh are the layoff notices?

As fresh as the state publishes. Texas updates its feed regularly, and the dedup means a daily run surfaces new filings the day they land.

Who buys WARN layoff data?

Recruiters and staffing firms (a pool of soon-to-be-available workers), outplacement and RPO vendors, commercial real estate watching a softening market, and sales teams tracking distressed accounts.