WARN Layoff Notices: TX, CA, WA, OR, MD, VA and NC WARN Act data as a clean feed

Price per 1,000 notices	Free plan	Starter	Scale	Business
This Actor	$3.00	$3.00	$3.00	$3.00

Video walkthrough: Watch the 1-minute demo on YouTube

• 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) as clean, deduplicated rows.
• Who it is for: recruiters and staffing firms, outplacement and benefits vendors, journalists, investors and labor researchers.
• Input: states (TX, CA, WA, OR, MD, VA, NC), 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, city, county, state, notice date, layoff date, days from notice to layoff, source state and source link.
• Price: $0.003 per notice; optional employer contact enrichment with your own Apollo key at $0.05 per enriched contact. Pay per result, no subscription; Apify's free plan credit covers a first test.
• Limits: seven 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 data: data.texas.gov, California EDD, Washington ESD, Oregon HECC, Maryland DLLR, Virginia VEC, North Carolina Commerce
• Pricing model: pay per event (warn-notice $0.003, enriched-contact $0.05)
• 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, layoff data API, WARN Act tracker, layoff alerts, plant closure notices
• Maintainer: transparent_meteorite (independent developer)
• Last updated: 2026-10-07

Which Texas employers filed WARN layoff notices, how many workers are affected, where, and when, as rows you can filter, schedule and export.

The WARN Act requires employers to give 60 days' notice before a mass layoff or plant closing. Texas publishes those notices on its open-data portal; this actor turns them into a deduped feed, with optional employer domain and phone.

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):

• California layoff notices for recruiters
• Large Texas layoffs for outplacement

Why choose this over alternatives

• Seven official state sources in one schema: TX, CA, WA, OR, MD, VA and NC.
• Deduplicated across runs with an "only new" mode, so scheduled alerts only show notices you have not seen.
• Employer, workers affected, city, notice and layoff dates, and a link back to the state source.
• $0.003 per notice, pay per result.

Check	This actor
States covered	7 (TX, CA, WA, OR, MD, VA, NC)
Automated tests on the current build	106 passed, 0 failed
Rows returned in the live test run	OR 188, CA 356, WA 150, MD 108, VA 1,132, NC 63

Measured 2026-10-09 (source: this actor's own test suite and runs).

Sample output

Real rows from a run on Oct 5, 2026:

Employer	City	County	Workers	Notice date	Layoff date
JPMorgan Chase & Co.	Plano	Collin	244	2026-06-23	2026-08-21
KUEHNE + NAGEL (KN) 2026	Lewisville	Denton	90	2026-06-16	2026-06-29
SAKS GLOBAL (Neiman Marcus)	Dallas	Dallas	67	2026-06-12	2026-09-30
Alan Ritchey Incorporated	Irving	Dallas	232	2026-06-08	2026-09-14
Toshiba International Corporation	Houston	Harris	67	2026-05-29	2026-09-30

Over the year to Oct 5, 2026 the Texas feed holds 115 notices.

What you get

One row per notice:

Field	Example
company	JPMorgan Chase & Co.
layoff_count	244
city, county, state	Plano, Collin, TX
notice_date, layoff_date, received_date	2026-06-23, 2026-08-21, 2026-06-23
wda	North Central Texas WDA (local workforce board)
employer_clean, size_bucket	JPMorgan Chase, 100-499 (employer name without legal suffix/dates; 1-49, 50-99, 100-499, 500+)
is_closure	true / false from the filed type (closure, shutdown, relocation); null where the state publishes no type (TX)
notice_to_layoff_days, days_since_notice	59, 112 (lead time between notice and layoff; age of the notice at run time)
scraped_at	ISO timestamp of the run
layoff_type, notice_url	Large Layoff - 10 or more workers, link to the filed notice (OR, WA; null for TX and CA)
source_state, source_url	TX, https://data.texas.gov/d/8w53-c4f6
company_domain, company_phone, company_industry, enriched	Filled only when you add an Apollo key

Export as CSV, Excel or JSON, read it from the API, or have it POSTed to a webhook.

Quick start

Press Start with the prefilled form: up to 50 Texas notices from the last 365 days. That run costs $1 at most.

Large layoffs only:

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

Exact date window, closures only, at least 50 workers (state types: CA, WA, OR, MD, VA, NC):

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

Weekly alert feed into Slack, a CRM or a sheet (schedule it weekly):

{ "states": ["TX"], "daysBack": 30, "onlyNewSinceLastRun": true, "webhookUrl": "https://hook.us1.make.com/your-hook" }

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

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

Inputs

Input	What it does	Default
states	2-letter codes: TX, CA, WA, OR, MD, VA, NC	["TX"]
daysBack	Notices from the last N days (1-365)	365
noticeDateFrom, noticeDateTo	Exact notice-date window, YYYY-MM-DD, overrides daysBack	empty
minAffectedWorkers	Only notices affecting at least N workers (minLayoffCount is the same filter)	0
onlyClosures	Only closure, shutdown or relocation notices (needs a state that publishes a type; not TX)	off
onlyNewSinceLastRun	Skip notices already delivered in earlier runs, so schedules never pay twice	on
maxResults	Hard cap on notices returned and charged	100
apolloApiKey, socrataAppToken	Optional keys (employer domain/phone; higher Texas rate limit)	empty
webhookUrl, webhookBatchSize	POST new notices as JSON batches	empty / 100

If a run finds nothing new, the log and run status say why instead of ending silently.

Pricing

Event	Price
WARN notice delivered	$0.003
Employer contact enriched (only with your Apollo key, and only when a domain or phone is found)	$0.05

You pull	You pay
50 notices (the prefilled Start)	$0.15
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

With onlyNewSinceLastRun on (the default), a notice you already received is skipped and never charged again, so a weekly schedule only bills new filings.

Apify's free plan includes $5 of monthly platform credit, which covers about 1,500 layoff notices with this actor (at $0.003 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.

Use with the API, n8n, Make, Zapier, Clay or AI agents

API (returns the rows in one call):

curl -X POST "https://api.apify.com/v2/acts/transparent_meteorite~warn-layoff-alerts/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"states":["TX"],"daysBack":365,"minLayoffCount":50}'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("transparent_meteorite/warn-layoff-alerts").call(run_input={"states": ["TX"], "daysBack": 365})
for notice in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(notice["company"], notice["layoff_count"], notice["layoff_date"])

• n8n, Make, Zapier: use the Apify app's "Run Actor" step with actor transparent_meteorite/warn-layoff-alerts, or set webhookUrl to a catch-hook URL.
• Clay: add an HTTP API column that calls the run-sync endpoint above.
• AI agents (MCP): connect https://mcp.apify.com?tools=transparent_meteorite/warn-layoff-alerts to Claude, Cursor or any MCP client.

Use from AI agents (MCP, ChatGPT, Claude, Perplexity)

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: "Where can I get WARN Act layoff data as an API?"

Call it directly over HTTP (runs the actor and returns the dataset items in one request):

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

Python:

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("transparent_meteorite/warn-layoff-alerts").call(run_input={"states": ["TX"], "daysBack": 365, "maxResults": 10, "onlyNewSinceLastRun": false})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

The same actor works in n8n, Make, Zapier, LangChain, LlamaIndex and CrewAI through their Apify integrations.

Questions people ask

Where can I get WARN Act layoff data as an API? This actor pulls WARN notices from the Texas, California, Washington, Oregon, Maryland, Virginia and North Carolina state sources and returns them as JSON or CSV through the Apify API.

How do I get alerts for new layoffs? Schedule the actor daily with onlyNewSinceLastRun true and a webhookUrl; each run sends only notices you have not received before.

Which states are covered? TX, CA, WA, OR, MD, VA and NC. Any other state code is skipped and noted in the log.

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)

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}'

Send results to Google Sheets, 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.
• Schedule and webhooks: create a Task with your input, add a Schedule in Apify Console, and add a webhook if you want a call when a run finishes.

See the Apify integrations docs for setup steps.

State coverage

State	Official source	Update cadence	Fields
TX	data.texas.gov open dataset	Irregular (state feed)	employer, city, county, layoff count, notice date, layoff date, received date
CA	EDD current-quarter WARN report (xlsx)	Weekly	employer, city, county, layoff count, notice date, layoff date, received date, type
WA	Employment Security Department WARN database	Rolling	employer, city, layoff count, notice (received) date, layoff start, type, notice link
OR	HECC rapid response tracker	Rolling	employer, city, layoff count, notice date, type, notice link
MD	Maryland DLLR WARN page (current and prior year)	Rolling, same week as filing	employer, city, county, layoff count, notice date, effective date, type
VA	VirginiaWorks (VEC) WARN notices table	Rolling, same week as filing	employer, city, layoff count, notice date, impact date, type, notice PDF link
NC	NC Commerce Workforce WARN Summary List	Updated every few days	employer, city, county, layoff count, notice date, received date, effective date, type

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.

Use cases

• Recruiters and staffing firms: reach displaced workers' employers and regions as soon as a notice is published.
• Outplacement and benefits vendors: a feed of employers that must plan for affected staff.
• Journalists and researchers: one clean, deduplicated table across TX, CA, WA and OR instead of four different state formats.
• Investors and analysts: watch layoff and closure notices for the companies and counties you follow.
• Alerts: schedule it with onlyNewSinceLastRun and send new notices to Slack, email or a sheet.

New to Apify? Create a free account and run this Actor in under a minute. Some links are affiliate links.

Related actors

More tools from the same publisher that fit this workflow:

• SAM.gov Contract Opportunities: federal bids and RFPs from SAM.gov
• Federal Grants & Contracts Finder: Grants.gov and USAspending awards in one place
• OFAC Sanctions Screening: fuzzy-match names against OFAC, EU, UN and UK lists
• New Business Filings: newly registered LLCs and corporations
• SEC Form D Startup Funding Leads: recently funded startups from SEC Form D
• FMCSA New Motor Carrier Leads: new motor carriers with contact details

Use from AI agents: every actor here is callable through the Apify MCP server (mcp.apify.com) and our open-data-actors MCP endpoint.

FAQ

How do I get WARN layoff notices automatically?

Schedule this actor weekly with onlyNewSinceLastRun on. Each run returns only notices you have not seen, so you get an alert-style feed with no repeats.

Which states are covered?

Texas (TX), California (CA), Washington (WA), Oregon (OR), Maryland (MD), Virginia (VA) and North Carolina (NC). See the coverage table above for sources, cadence and fields. Oregon's tracker also lists notices for multi-state employers, so some OR-sourced rows have a state outside Oregon; source_state is always the source (OR). California's public report covers the current quarter only. Pass "states": ["TX","CA","WA","OR"] to pull all four. 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.

How current is the Texas WARN data?

It is exactly as current as Texas's open-data feed. On Oct 5, 2026 the newest notice in the feed was dated June 23, 2026, so Texas had not published new filings for over three months. That is why the default window is 365 days. The actor picks up new filings the day Texas publishes them.

Can I get employer contact info from a WARN notice?

Yes, with your own Apollo.io key. Each notice then gets the employer's website domain and main phone from a company-level Apollo search. We clean messy filing names first (for example "Spirit Airlines (DFW) May 2026" becomes "Spirit Airlines"). No personal emails are added.

What is a WARN notice?

Under the federal WARN Act, employers with 100 or more employees must give 60 days' written notice before a plant closing or mass layoff. States collect these notices and many publish them.

Is WARN data public?

Yes. WARN notices are public records published by the state. This actor reads the official Texas dataset (data.texas.gov, dataset 8w53-c4f6) with no login.

More questions

Is there a WARN notice API? This actor works as one: call it from the Apify API (examples above) and get WARN notices from official state sources as JSON or CSV.

Which states are covered? Texas, California, Washington and Oregon. Other state codes are skipped with a note in the log.

How fresh is the data? As fresh as each state publishes it. Some state feeds update more often than others, so check the notice dates in your results.

Can I filter out small layoffs? Yes. Set minAffectedWorkers (or the older minLayoffCount; the larger applies).

Can I get employer contacts? Optional: with your own Apollo API key the actor can add employer contacts. Pricing for that is shown in the Pricing section.

How this compares

WARN notices are public, and each state posts them in its own format (a dataset, a spreadsheet, web pages). This actor reads the official state sources and returns one schema, with deduplication and an "only new" mode. Commercial layoff trackers may cover more states or add their own research; this actor covers the seven states listed and only what those states publish.

Limitations

• Four states today (TX, CA, WA, OR, MD, VA, NC). Others are added as they publish scrapable public data.
• Data lag is set by Texas. See the freshness answer above; we cannot publish notices the state has not released.
• Company names are as filed. They can include site names or dates, e.g. "KUEHNE + NAGEL (KN) 2026".
• Enrichment is company-level and needs your Apollo key. It uses your Apollo credits, and large or oddly named employers do not always match.

Related actors

• FMCSA New Carrier Leads: new US trucking companies with email and phone, from the official FMCSA census.

Need another state or a field? Open an issue on the Issues tab and we reply quickly.

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

• Guide & examples: mamoo85.github.io/open-data-actors/warn-layoff-alerts.html
• Sample output and example input on GitHub (masked sample CSV): github.com/Mamoo85/apify-actor-samples/warn-layoff-alerts
• Workflow templates: n8n, Make, Zapier recipe

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.

Works well with

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

• Company News Monitor: follow the news coverage around the employers that file WARN notices.
• Company Enrichment by Domain: turn affected employers' domains into company rows with socials and public contact routes.
• Career Site Jobs API (Greenhouse, Lever, Ashby and more): see whether an employer that is laying off people is still hiring elsewhere.
• Workday Jobs Scraper: see which of the same employers are still hiring on Workday career sites.

What the free plan gets you

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

Need more than the data?

This actor is built by Detroit Web Agent, a small Detroit studio that builds websites, lead pages and simple data tools for small businesses. If you want these results turned into a working website, a landing page or a CRM import, or you need a field this actor does not cover yet, open an issue on the Issues tab or visit detroitwebagent.com.

---

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.