# WARN Layoff Notices: Layoff Data + Employer Contacts (`transparent_meteorite/warn-layoff-alerts`) Actor

Fresh WARN Act layoff notices: employer, headcount, city, notice and layoff dates. Deduped across runs, with optional employer domain + phone enrichment. Export to CSV, JSON, or webhook. Pay per result. Texas live, more states on request.

- **URL**: https://apify.com/transparent\_meteorite/warn-layoff-alerts.md
- **Developed by:** [Matthew Michels](https://apify.com/transparent_meteorite) (community)
- **Categories:** Lead generation, Jobs
- **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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

![WARN Layoff Notices: layoff data plus employer contacts](https://api.apify.com/v2/key-value-stores/9BAn0msnxToXlD9TO/records/warn-banner.png)

## 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` and, when enrichment is on, `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

| Field | What it does |
|---|---|
| `states` | States to pull. Adapter exists for `TX` today; unknown states are skipped (logged) |
| `daysBack` | Notices with a notice\_date in the last N days (default 30) |
| `onlyNewSinceLastRun` | Skip notices returned before (deduped by employer + date + city) |
| `minLayoffCount` | Only notices affecting at least N workers |
| `maxResults` | Hard cap per run |
| `apolloApiKey` | Optional. Turns on employer domain + phone enrichment |
| `socrataAppToken` | Optional. Dodge Socrata shared-pool throttling |
| `webhookUrl` / `webhookBatchSize` | Optional. POST batches of notices to your endpoint |

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

```json
[
  {
    "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.

# Actor input Schema

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

Which states to pull. Today an adapter exists for: TX. Unknown states are skipped with a log note.

## `daysBack` (type: `integer`):

Only notices with a notice\_date within the last N days.

## `onlyNewSinceLastRun` (type: `boolean`):

Skip notices already returned in a previous run (by company + date + city). On for a clean recurring feed.

## `minLayoffCount` (type: `integer`):

Only notices affecting at least this many workers. 0 = no minimum.

## `maxResults` (type: `integer`):

Hard cap on notices returned this run.

## `apolloApiKey` (type: `string`):

If set, each notice is enriched with the employer's domain + phone via Apollo company search (company-level, not personal email). Can also be set via APOLLO\_API\_KEY env var. Costs Apollo credits per notice.

## `socrataAppToken` (type: `string`):

Free Socrata token to avoid shared-pool throttling. Or set SOCRATA\_APP\_TOKEN env var.

## `webhookUrl` (type: `string`):

If set, delivered notices are POSTed here as JSON in batches: { source, count, records: \[...] }.

## `webhookBatchSize` (type: `integer`):

Records per webhook POST.

## Actor input object example

```json
{
  "states": [
    "TX"
  ],
  "daysBack": 30,
  "onlyNewSinceLastRun": true,
  "minLayoffCount": 0,
  "maxResults": 1000,
  "webhookUrl": "",
  "webhookBatchSize": 100
}
```

# 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 = {
    "states": [
        "TX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("transparent_meteorite/warn-layoff-alerts").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 = { "states": ["TX"] }

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

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

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

```

## CLI example

```bash
echo '{
  "states": [
    "TX"
  ]
}' |
apify call transparent_meteorite/warn-layoff-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=transparent_meteorite/warn-layoff-alerts",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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