# Registry Events Tracker — New Companies & Dissolutions (FR+UK) (`aspiring_barricade/registry-events-tracker`) Actor

Fresh company registry events as sales signals: new registrations, dissolutions, modifications and insolvency proceedings for France (BODACC) and the UK (Companies House). Filter by event type, region, sector and date window, with dedup and a new-only alert mode. Official open data.

- **URL**: https://apify.com/aspiring\_barricade/registry-events-tracker.md
- **Developed by:** [Joachim Pouchain](https://apify.com/aspiring_barricade) (community)
- **Categories:** Developer tools, Automation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

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

## Registry Events Tracker — New Companies, Dissolutions & Director Changes (FR + UK)

A fresh **business registration tracker** for **France** and the **UK**. Instead of a static directory, this actor returns a **stream of registry events** — **new companies**, **dissolutions**, modifications and **insolvency** proceedings — straight from official open data (**BODACC** for France, **Companies House** for the UK). Filter by event type, region, sector and date window, deduplicate, and use **new-only** mode for clean **sales signals**: *"which companies just got created or changed in my area this week."*

This is **lead generation France UK** at the source: official registries, not a scraped contact list.

### What it does

- **New company alerts** — fresh incorporations (FR + UK).
- **Dissolutions, modifications & insolvency** — radiations, changes and *procédures collectives* (FR).
- **Filters** — event type, region (FR department / UK town), sector (UK SIC code), and a lookback window.
- **New-only alert mode** — return only events not seen in previous runs (per alert key) — perfect for daily prospecting.
- **Dedup** — no repeated rows across runs.

### Output fields

| Field | Meaning |
|-------|---------|
| `country` | `FR` or `UK` |
| `event_type` | `new_company`, `dissolution`, `modification`, `insolvency`, `accounts_filing` |
| `event_date` | Publication / incorporation date |
| `company_name`, `company_id` | Name + SIREN (FR) / company number (UK) |
| `registry` | `RCS (BODACC)` or `UK Companies House` |
| `sector_code(s)` | SIC codes (UK); `null` for FR (BODACC carries no NAF) |
| `region`, `region_code` | Department / town + code / postcode |
| `status`, `detail` | Event family + sub-type |
| `source_url` | Official record link |

### Why this one

- **An event flux, not a static lookup.** Built for prospecting on fresh signals, with a **new-only** alert mode that competitors' static scrapers don't offer.
- **FR + UK unified** in one normalized schema (SIREN ↔ company number, same fields).
- **Official open data** — BODACC (DILA) and Companies House — with cache + retry/backoff.
- **Agent- & n8n-ready** — one clean event per row; schedule it for daily lead alerts.

### Input

```json
{
  "country": "FR",
  "event_types": [],
  "window_days": 7,
  "new_only": false,
  "max_items": 50
}
```

| Field | Type | Description |
|-------|------|-------------|
| `country` | string | `FR`, `UK` or `BOTH`. |
| `event_types` | array | `new_company`, `dissolution`, `modification`, `insolvency`, `accounts_filing`. Empty = all (FR). UK = `new_company` only. |
| `window_days` | integer | Events from the last N days. Default 7. |
| `region` | string | FR department number (e.g. `75`) or UK town (e.g. `London`). |
| `sic_codes` | array | UK sector filter (e.g. `62012` software development). |
| `new_only` | boolean | Only events new since the last run. |
| `alert_key` | string | Namespace for new-only history. |
| `max_items` | integer | Max events returned/charged. Default 50. |

### Output

Real FR insolvency event and UK new-incorporation event:

```json
{
  "country": "FR",
  "event_type": "insolvency",
  "event_date": "2026-06-28",
  "company_name": "LUXART-RENOV",
  "company_id": "841918410",
  "registry": "RCS (BODACC)",
  "sector_code": null,
  "region": "Aisne",
  "region_code": "02",
  "status": "Procédures collectives",
  "detail": "Avis initial",
  "source": "BODACC — DILA (bodacc-datadila.opendatasoft.com)",
  "source_url": "https://www.bodacc.fr/pages/annonces-commerciales-detail/?q.id=id:A202601212046",
  "timestamp": "2026-06-29T10:43:29.368Z"
}
```

```json
{
  "country": "UK",
  "event_type": "new_company",
  "event_date": "2026-06-22",
  "company_name": "VALE & VOYAGER LTD",
  "company_id": "17293246",
  "registry": "UK Companies House",
  "sector_code": "46900",
  "sector_codes": ["46900", "47910", "70229", "79901"],
  "region": "Manchester",
  "region_code": "M40 8WN",
  "status": "active",
  "detail": "ltd",
  "source": "UK Companies House (api.company-information.service.gov.uk)",
  "source_url": "https://find-and-update.company-information.service.gov.uk/company/17293246",
  "timestamp": "2026-06-29T10:43:30.355Z"
}
```

### Use cases

- **Sales prospecting** — reach newly-formed companies the week they register (FR + UK), filtered to your sector/region.
- **Distress / restructuring leads** — track French *procédures collectives* (insolvency) as they're published.
- **Market intelligence** — measure formation and dissolution rates by region and sector.
- **AI agents / n8n** — schedule daily with `new_only: true` for a deduplicated lead feed.

### Pricing

Pay-per-result: target **$0.004 per event** (~$3–5 / 1,000), plus Apify platform usage. `max_items` and `new_only` keep scheduled runs cheap.

### Categories

`Developer tools`, `Automation`, `Agents`, `Business`.

### Setup & notes

- **France (BODACC)** works with **no key** — the default run returns events out of the box.
- **UK (Companies House)** needs a free API key. Set it as a **secret environment variable** `COMPANIES_HOUSE_API_KEY` on the actor. Without it, `country: UK`/`BOTH` reports the UK part as unavailable; FR still works.
- UK currently covers **new incorporations** (Companies House advanced-search). FR covers creations, dissolutions, modifications, insolvency and account filings.
- FR BODACC announcements don't carry a NAF/sector code, so `sector_code` is `null` for France.
- Official registry data, **not a legal opinion**.

# Actor input Schema

## `country` (type: `string`):

FR (France, BODACC), UK (Companies House) or BOTH.

## `event_types` (type: `array`):

Filter: new\_company, dissolution, modification, insolvency, accounts\_filing. Empty = all (FR). UK supports new\_company only.

## `window_days` (type: `integer`):

Only events from the last N days.

## `region` (type: `string`):

FR: department number (e.g. 75 for Paris). UK: a location/town (e.g. London).

## `sic_codes` (type: `array`):

UK only: filter new incorporations by SIC code (e.g. 62012 for software development).

## `new_only` (type: `boolean`):

Return only events not seen in previous runs (persisted per alert key). Perfect for scheduled lead alerts.

## `alert_key` (type: `string`):

Namespace so different saved searches keep separate new-only history.

## `max_items` (type: `integer`):

Maximum events returned/charged per run.

## Actor input object example

```json
{
  "country": "FR",
  "event_types": [],
  "window_days": 7,
  "sic_codes": [],
  "new_only": false,
  "alert_key": "default",
  "max_items": 50
}
```

# 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 = {
    "window_days": 7,
    "max_items": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("aspiring_barricade/registry-events-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 = {
    "window_days": 7,
    "max_items": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("aspiring_barricade/registry-events-tracker").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 '{
  "window_days": 7,
  "max_items": 50
}' |
apify call aspiring_barricade/registry-events-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=aspiring_barricade/registry-events-tracker",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/OXK1HAAu1EJWzO4iz/builds/cSbfDzyYEJfBadhoD/openapi.json