# Spain BORME Alerts: New Company Acts by Province (`accountable_eel/spain-borme-alerts`) Actor

Spain BORME alerts: monitor new company incorporations, capital increases, officer appointments and dissolutions by Spanish province or keyword. Webhook alerts to Discord, Slack or Telegram.

- **URL**: https://apify.com/accountable_eel/spain-borme-alerts.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.25 / 1,000 company act 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

## Spain BORME Alerts: New Company Acts by Province

Every new Spanish company act (incorporation, capital increase, officer appointment, dissolution, extinction, or by-law change) published in the BORME (Boletín Oficial del Registro Mercantil). Filter by province, act type, or keyword, and monitor on a schedule so each run returns only the company acts published since the last one.

Official Spanish state open data from the Agencia Estatal Boletín Oficial del Estado (BOE). No proxy, no API key needed.

### Who uses this

- **Lead generation & B2B sales teams:** Discover brand-new companies registered in Madrid, Barcelona, Valencia, and across Spain within hours of publication.
- **Credit risk & legal teams:** Monitor insolvency proceedings, capital reductions, and dissolutions of Spanish entities.
- **M\&A & investment analysts:** Track capital increases, transformations, and corporate restructuring acts.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `provinces` 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~spain-borme-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"provinces":["MADRID"]}'
   ```
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 acts new since the last run" enabled, and add a Discord, Slack, or Telegram webhook link under "Send alerts to".

### Input

```json
{
  "provinces": [
    "MADRID"
  ]
}
```

Optional. Spanish provinces to monitor, e.g. MADRID, BARCELONA, VALENCIA, SEVILLA. Leave empty to monitor all of Spain. Accepted formats: MADRID, BARCELONA, VALENCIA.

### Output

Each delivered row represents one official company act:

- `companyName`: Name of the Spanish company (e.g. `INVERSIONES TECNOLOGICAS MADRID SL`).
- `actType`: Primary act type (e.g. `Constitución`, `Ampliación de capital`, `Disolución`).
- `actTypes`: All act types identified in the entry.
- `province`: Spanish province of the mercantile registry.
- `publicationDate`: Official publication date (YYYY-MM-DD).
- `entryNumber`: Sequential BORME inscription entry number.
- `bormeId`: Official bulletin ID (e.g. `BORME-A-2026-210-28`).
- `capitalEur`: Declared or resulting capital in EUR (null when not stated).
- `operationsStartDate`: Declared start of commercial operations.
- `corporatePurpose`: Declared corporate purpose (`Objeto social`).
- `registeredOffice`: Registered address (`Domicilio social`).
- `registryData`: Mercantile registry volume, folio, sheet, and inscription data.
- `sourceUrl`: Link to the official BORME bulletin text page on BOE.
- `pdfUrl`: Link to the official gazette PDF on BOE.
- `isNew`: Boolean flag indicating whether this act is new to this watchlist.

Note: In accordance with privacy rules, personal names of individuals (such as appointed officers and administrators) are omitted from output fields.

| query | found | status | searchSummary | actCount | monitorStatus | truncated | notifyErrors | acts | actId | entryNumber | companyName | province | publicationDate | bormeId | actType | actTypes | capitalEur | operationsStartDate | corporatePurpose | registeredOffice | registryData | sourceUrl | pdfUrl | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| MADRID | true | OK | <search run> | <acts returned> | <monitoring status> | <more results were available> | <alert delivery errors> | <all company acts> | <act id> | <borme entry number> | <company name> | <province> | <publication date> | <borme bulletin id> | <primary act type> | <all act types> | \<capital (eur)> | <operations start date> | <corporate purpose> | <registered office address> | <mercantile registry inscription data> | <borme bulletin text link> | <official gazette pdf link> | \<is this act new?> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

### Limits

- **Business days:** BORME publishes Monday through Friday (excluding Spanish national holidays). When run on weekends or holidays, the actor automatically scans back to the latest published edition.
- **Volume:** Use `maxItems` and province filters to control dataset size.

### Example runs

**1. New company incorporations in Madrid (lead generation)**

```json
{
  "provinces": ["MADRID"],
  "actTypes": ["Constitución"],
  "daysBack": 1,
  "maxItems": 20
}
```

**2. Daily new incorporations across Catalonia (monitoring)**

```json
{
  "provinces": ["BARCELONA", "GIRONA", "LLEIDA", "TARRAGONA"],
  "actTypes": ["Constitución"],
  "onlyNewSinceLastRun": true,
  "daysBack": 2,
  "maxItems": 50
}
```

**3. Dissolutions & liquidations alert (credit risk watch)**

```json
{
  "provinces": [],
  "actTypes": ["Disolución", "Extinción"],
  "onlyNewSinceLastRun": true,
  "daysBack": 3,
  "maxItems": 100
}
```

### Pricing

- **Company act returned**: $2.5 per 1,000 acts

Plus a $0.00005 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~spain-borme-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"provinces":["MADRID"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~spain-borme-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"provinces":["MADRID"]}` (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~spain-borme-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"provinces":["{{search}}"]}`, mapping the row's search into the `provinces` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "borme spain company scraper" — the agent will find and run this actor.

# Actor input Schema

## `provinces` (type: `array`):

Optional. Spanish provinces to monitor, e.g. MADRID, BARCELONA, VALENCIA, SEVILLA. Leave empty to monitor all of Spain. Accepted formats: MADRID, BARCELONA, VALENCIA. You're only charged for the ones we actually find — a miss costs nothing.

## `actTypes` (type: `array`):

Optional. List of act types to filter by (e.g. Constitución, Ampliación de capital, Disolución, Extinción, Cambio de domicilio social). Leave empty for all acts.

## `keywords` (type: `array`):

Optional. One keyword per line. An act is kept when the company name or declared corporate purpose contains one of them. Leave empty for all companies.

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

1 to 30. How many recent publication editions of BORME to scan. Default 1 (the latest published BORME edition).

## `maxItems` (type: `integer`):

Up to 1,000. Caps how many company acts you get (and pay for) in one run.

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

On: only acts not returned by a previous run of the same watchlist are delivered and charged. Run this on a schedule as an alert. Off: every matching act is returned every time.

## `deltaName` (type: `string`):

Optional. Name this search monitoring memory so you can tell two schedules apart. Leave empty to derive one from your filters.

## `notifyUrl` (type: `string`):

Optional. After acts are billed, each NEW act is posted here as one message with company name, act type, province, capital and links. Stored encrypted, never logged.

## `notifyFormat` (type: `string`):

Leave on Detect from the link for automatic webhook detection. Pick one to override.

## `maxNotificationsPerRun` (type: `integer`):

Up to 100. Above this, one +N more message says how many more acts are in the run dataset.

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

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `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 act 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
{
  "provinces": [
    "MADRID"
  ],
  "actTypes": [
    "Constitución"
  ],
  "keywords": [],
  "daysBack": 1,
  "maxItems": 20,
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "notifyFormat": "auto",
  "maxNotificationsPerRun": 20,
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "searchSummary",
    "actCount",
    "monitorStatus",
    "truncated",
    "notifyErrors",
    "acts",
    "actId",
    "entryNumber",
    "companyName",
    "province",
    "publicationDate",
    "bormeId",
    "actType",
    "actTypes",
    "capitalEur",
    "operationsStartDate",
    "corporatePurpose",
    "registeredOffice",
    "registryData",
    "sourceUrl",
    "pdfUrl",
    "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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "provinces": [
        "MADRID"
    ],
    "actTypes": [
        "Constitución"
    ],
    "keywords": [],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/spain-borme-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 = {
    "provinces": ["MADRID"],
    "actTypes": ["Constitución"],
    "keywords": [],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/spain-borme-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 '{
  "provinces": [
    "MADRID"
  ],
  "actTypes": [
    "Constitución"
  ],
  "keywords": [],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/spain-borme-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/spain-borme-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 <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/7wvCEb929Wj17YLaa/builds/gc0mjX6EgMvNCega1/openapi.json
