# Layoff Tracker: WARN Notices from 7 States (`scrapemint/layoff-warn-tracker`) Actor

Mass layoff and plant closure notices filed under the WARN Act, usually 60 days before the layoff, from California, Texas, Washington, Virginia, Colorado, Maryland and Tennessee in one feed. Company, city, workers affected, layoff date. Schedule it for alerts. No key, no proxy. Pay per notice.

- **URL**: https://apify.com/scrapemint/layoff-warn-tracker.md
- **Developed by:** [Ken M](https://apify.com/scrapemint) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Layoff Tracker: WARN Notices from 7 States

Know about layoffs and closures before they happen. Under the federal WARN Act, an employer planning a mass layoff or plant closing must file a notice with the state, usually **60 days ahead**. This actor reads those notices from state labor agencies and returns them in one feed: **company, location, workers affected, layoff date, closure or layoff**.

Covered: **California, Texas, Washington, Virginia, Colorado, Maryland and Tennessee.**

Put it on a daily schedule and each run returns only notices you have not seen. No key, no login, no browser, no proxy: every source is the state's own official publication.

### Who uses it

- **Recruiters and staffing firms:** experienced people coming onto the market, by employer and city, weeks in advance
- **Outplacement and career services:** every notice is a company that needs you now
- **B2B sales:** a closing site means lost accounts; a layoff means budget changes
- **Investors and analysts:** early read on which employers are cutting, where and how deep
- **Journalists and researchers:** a clean, dated record across states

### What you get

One row per notice:

| Field | Example |
|---|---|
| `company` | `Covenant Aviation Security, LLC` |
| `state`, `city`, `county`, `address` | `CA`, `San Francisco`, `San Francisco`, street address where published |
| `employeesAffected` | `1279` |
| `noticeType`, `permanent` | `Layoff` / `Closure` / `Relocation`, `true` / `false` |
| `noticeDate`, `receivedDate` | the date on the notice, and when the state received it |
| `layoffDate`, `daysUntilLayoff` | when the layoff takes effect, and how far away that is |
| `industry`, `reason` | where the state publishes them |
| `major`, `majorReasons` | 100+ workers or a closure |
| `noticeUrl` | the notice letter itself (Washington) |
| `source` | the official page the row came from |

### Examples

- **Daily layoff alerts, all states:** defaults, on a daily schedule
- **Only big ones:** `minEmployees: 100`
- **Closures only:** `noticeTypes: ["Closure"]`
- **Watch specific employers:** `companies: ["Amazon", "Intel", "Kaiser"]`
- **California and Washington tech hubs:** `states: ["CA", "WA"]`
- **A year of history:** `onlyNew: false`, `lookbackDays: 365`

### Pricing

| Event | Price | When |
|---|---|---|
| `warn_notice` | $0.01 | a layoff or closure notice |
| `major_warn_notice` | $0.03 | one affecting 100 or more workers, or a full closure |

A run with no new notices returns nothing and costs nothing.

### Coverage, stated plainly

There is no national WARN database: every state publishes its own way, and some make it impossible to read automatically. This actor includes a state only when its official source can be read reliably with a plain request.

| State | Source | Notes |
|---|---|---|
| California | EDD spreadsheet, updated twice a week | includes county, address and industry |
| Texas | TWC dataset on data.texas.gov | **published with a delay of up to several months** |
| Washington | ESD WARN database | includes a link to each notice letter |
| Virginia | Virginia Works CSV | |
| Colorado | CDLE real-time sheet | includes industry and reason |
| Maryland | Labor department table | |
| Tennessee | TDLWD reports page | type (closure/layoff) not published |

Not included: New York and Illinois publish only through interactive dashboards; Florida, Arizona, Michigan, Utah and Kansas refuse automated requests. Other states may be added as their sources allow.

If a state's site is down on a run, the others still return and the run summary names the one that failed.

# Actor input Schema

## `states` (type: `array`):

Two-letter codes from: CA, TX, WA, VA, CO, MD, TN. Empty for all seven.

## `lookbackDays` (type: `integer`):

Notices the state received or published within this many days.

## `minEmployees` (type: `integer`):

Skip notices affecting fewer workers.

## `companies` (type: `array`):

Only notices whose company name contains one of these, e.g. Amazon, Intel, Kaiser.

## `noticeTypes` (type: `array`):

Closure, Layoff or Relocation. Empty for all. Texas and Tennessee do not publish the type.

## `onlyNew` (type: `boolean`):

On: each run returns only notices earlier runs (with the same filters) have not. For alerts on a schedule. Off: every notice in the window.

## `maxNotices` (type: `integer`):

Stop after this many, newest first. Any cut off are returned by the next run.

## Actor input object example

```json
{
  "states": [],
  "lookbackDays": 14,
  "minEmployees": 0,
  "companies": [],
  "noticeTypes": [],
  "onlyNew": true,
  "maxNotices": 50
}
```

# Actor output Schema

## `notices` (type: `string`):

Company, state, city, county, address, workers affected, closure or layoff, permanent or temporary, notice, received and layoff dates, days until layoff, industry, reason, major flag, notice link.

## `summary` (type: `string`):

Notices per state, and any state that could not be read on this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "lookbackDays": 14,
    "maxNotices": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapemint/layoff-warn-tracker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "lookbackDays": 14,
    "maxNotices": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapemint/layoff-warn-tracker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "lookbackDays": 14,
  "maxNotices": 50
}' |
apify call scrapemint/layoff-warn-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapemint/layoff-warn-tracker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xgaDe1sG3U1SeZOOa/builds/f39vBfkEv24fRSYyd/openapi.json