# BODACC Alerts: New French Companies & Insolvencies (`accountable_eel/france-bodacc-alerts`) Actor France BODACC alerts: new company registrations, insolvency proceedings, business sales and deregistrations by département (75 for new companies in Paris), keyword or SIREN. Monitor BODACC notices for a SIREN, only new ones, to Slack, Discord or Telegram. Export business sales to Google Sheets. - **URL**: https://apify.com/accountable_eel/france-bodacc-alerts.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Lead generation, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 bodacc announcement returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 ## BODACC Alerts: New French Companies & Insolvencies Every new French company registration, insolvency proceeding (redressement, liquidation), business sale or deregistration published in the BODACC, the French state's official commercial bulletin. Filter by département, keyword or SIREN, and monitor it on a schedule so each run returns only the notices published since the last one. Official state open data (DILA, Etalab Licence Ouverte 2.0). No proxy, no API key. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `keywords` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. 2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~france-bodacc-alerts/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"keywords":[""]}' ``` 3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required. For an alert, schedule the actor daily with "Only return notices new since the last run" on, and add a Discord, Slack or Telegram link under "Send alerts to". Accounts filings (dépôts des comptes) are not offered on purpose: they are very high volume. ### Input ```json { "keywords": [ "" ] } ``` Optional. One keyword per line. A notice is kept when the company name or its declared activity contains one of them. Leave empty to get every notice in the families and window you choose. Accepted formats: boulangerie, logiciel, transport. ### Output Every row carries the notice fields (`id`, `familyLabel`, `publishedOn`, `siren`, `companyName`, `legalForm`, `activity`, `address`, `judgmentNature`, `judgmentDate`, `noticeUrl`) plus `isNew` and `firstSeenAt` when monitoring is on. `activity`, `judgmentNature` and `judgmentDate` are read from the bulletin's own JSON fields and are null when the bulletin does not publish them. | query | found | status | announcementCount | announcements | searchSummary | monitorStatus | truncated | notifyErrors | id | family | familyLabel | noticeType | publishedOn | siren | companyName | legalForm | activity | address | postcode | city | departement | region | court | judgmentNature | judgmentDate | noticeUrl | matchedKeyword | isNew | firstSeenAt | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | | true | OK | | \ | | | | | | | | \ | | | | | | | | | \ | | \ | \ | | | | \ | | 1970-01-01T00:00:00.000Z | ### Example runs For French company-formation and insolvency monitors. Change the field named in each note. **1. New companies in Paris (who: local lead-gen)** — change `departements` ```json { "families": "creation", "departements": ["75"], "sinceDays": 7 } ``` **2. France insolvency alerts (who: credit-risk watch)** — change `families` / turn on monitoring ```json { "families": "collective", "onlyNewSinceLastRun": true } ``` **3. Business sales by keyword (who: M\&A / asset buyer)** — change `keywords` (confirm `vente` live before relying on it) ```json { "families": "vente", "keywords": ["restaurant"], "sinceDays": 14 } ``` ### Pricing - **BODACC announcement returned**: $4 per 1,000 notices Plus a $0.01 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged. ### Use it from Clay, n8n, Make, or an AI agent This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~france-bodacc-alerts/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"keywords":[""]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~france-bodacc-alerts/run-sync-get-dataset-items?token=`, Body Content Type `JSON`, JSON Body `{"keywords":[""]}` (swap in an expression from an earlier node for a real value). **Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~france-bodacc-alerts/run-sync-get-dataset-items?token=`, Body `{"keywords":["{{search}}"]}`, mapping the row's search into the `keywords` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "BODACC new companies and insolvency alerts" — the agent will find and run this actor. # Actor input Schema ## `keywords` (type: `array`): Optional. One keyword per line. A notice is kept when the company name or its declared activity contains one of them. Leave empty to get every notice in the families and window you choose. Accepted formats: boulangerie, logiciel, transport. You're only charged for the ones we actually find — a miss costs nothing. ## `families` (type: `string`): Which kinds of BODACC notice to return. Accounts filings (dépôts des comptes) are left out on purpose: they are very high volume and not what this feed sells. ## `departements` (type: `array`): Optional. Two-digit département codes, e.g. 75 (Paris), 69 (Rhône), 2A (Corse-du-Sud). Empty means all of France. ## `sirens` (type: `array`): Optional. Nine-digit SIREN numbers of companies you already know. Only notices for these companies are returned. ## `sinceDays` (type: `integer`): 1 to 60. Notices published in the last N days. For a daily schedule, keep this at 3 so a weekend or a late publication is never missed. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Up to 2,000. Caps how many notices you get (and pay for) in one run. ## `onlyNewSinceLastRun` (type: `boolean`): On: only notices not returned by a previous run of the same watchlist are returned and charged. Run this on a schedule as an alert. Off: every matching notice is returned every time. Notices not seen for 60 days are forgotten. ## `deltaName` (type: `string`): Optional. Name this search's monitoring memory so you can tell two schedules apart, or keep one memory across an input change. Leave empty to derive one from your filters. ## `notifyUrl` (type: `string`): Optional. After the notices are billed, each NEW notice is posted here as one message: company, SIREN, city, judgment nature and the BODACC link, with a NEW NOTICE badge. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot/sendMessage?chat_id=. Any other URL receives JSON. Messages are free, and a message that fails never fails the run (the row's notifyErrors says why). Stored encrypted, never logged or written to the results. ## `notifyFormat` (type: `string`): Leave on "Detect from the link": discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON. Pick one only to override that. ## `maxNotificationsPerRun` (type: `integer`): Up to 100. Above this, one "+N more" message says how many more notices are in the run's dataset, so a busy first run never floods the channel. 0 sends only that one summary message. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each notice found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "keywords": [ "" ], "families": "creation", "departements": [], "sirens": [], "sinceDays": 3, "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "maxResults": 100, "onlyNewSinceLastRun": false, "deltaName": "", "notifyFormat": "auto", "maxNotificationsPerRun": 20, "columns": [ "announcementCount", "announcements", "searchSummary", "monitorStatus", "truncated", "notifyErrors", "id", "family", "familyLabel", "noticeType", "publishedOn", "siren", "companyName", "legalForm", "activity", "address", "postcode", "city", "departement", "region", "court", "judgmentNature", "judgmentDate", "noticeUrl", "matchedKeyword", "isNew", "firstSeenAt" ], "expandRows": true, "maxConcurrency": 1, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "" ], "departements": [], "sirens": [], "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/france-bodacc-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": [""], "departements": [], "sirens": [], "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/france-bodacc-alerts").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 '{ "keywords": [ "" ], "departements": [], "sirens": [], "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/france-bodacc-alerts --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/france-bodacc-alerts" } } } ``` 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 ` 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/Ppe4TVR97r2u705dg/builds/HDqAfCdrDd0rTq56o/openapi.json