# UK Flood Warnings: Live Alerts and River Levels by Area (`accountable_eel/uk-flood-warning-monitor`) Actor

Live UK flood warnings, flood alerts, and river monitoring station levels from the Environment Agency real-time API. Monitor flood risks by coordinates or area with change alerts.

- **URL**: https://apify.com/accountable_eel/uk-flood-warning-monitor.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Developer tools, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 flood record 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

## UK Flood Warnings: Live Alerts and River Levels by Area

**Get live UK flood warnings, alerts, and river monitoring station levels by coordinates or area from the Environment Agency.**

Used by property developers, insurers, infrastructure teams, logistics operators, and local authorities to track active flood alerts, severe warnings, and rising river levels in real time. Features an automated monitoring mode that flags only new warnings or water level changes since your previous run.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `locations` 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~uk-flood-warning-monitor/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"locations":["51.5074, -0.1278"]}'
   ```
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.

### Input

```json
{
  "locations": [
    "51.5074, -0.1278"
  ]
}
```

Coordinates in 'lat, lon' format, e.g. '51.5074, -0.1278' (London). Or leave empty to use the Latitude/Longitude settings below. Area names like 'Kingston' are also accepted. Accepted formats: 51.5074, -0.1278, Kingston, Thames.

One combined lookup runs per call. The actor fetches active flood warnings across the designated zone and river telemetry stations with live water level readings. Missing values are null, never 0 or empty strings.

### Output

One row per flood record (active flood warning or river monitoring station), for example:

| query | found | status | searchSummary | recordCount | warningCount | stationCount | monitorStatus | records | recordType | recordId | title | severity | severityLevel | riverOrSea | areaName | county | town | waterLevel | waterLevelUnit | typicalRangeLow | typicalRangeHigh | levelStatus | warningMessage | operationalStatus | lat | lon | updatedAt | sourceUrl | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 51.5074, -0.1278 | true | OK | <search run> | <records returned> | <warnings returned> | <stations returned> | <monitoring status> | \<all records (full list)> | <record type> | <record id> | \<name / area> | <severity> | <severity level> | <river or sea> | \<catchment / ea area> | <county> | <town> | <water level> | <level unit> | <typical range low> | <typical range high> | <level status> | \<warning message / advice> | <operational status> | <latitude> | <longitude> | <updated at> | <source url> | <is new> | <first seen at> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged. `waterLevel` is `null` on flood warnings, and `severity` is `null` on monitoring stations.

### Pricing

- **Flood record returned**: $3 per 1,000 flood-records

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.

### Limits

- **Coverage**: Covers England rivers and coastal flood warning areas published by the UK Environment Agency. Scotland (SEPA) and Wales (NRW) operate separate monitoring networks.
- **Refresh rate**: Environment Agency telemetry stations typically publish readings every 15 minutes.
- **Dry weather**: When no flood warnings or alerts are active nationwide, warning results will be empty; station water levels continue to report normally.

### Example runs

Paste any of these into the Input tab and press Start. All three run keylessly with no external account required.

**Central London 15km radius (live flood warnings and river levels)**

```json
{
  "locations": ["51.5074, -0.1278"],
  "radiusKm": 15,
  "recordType": "all",
  "maxItems": 20
}
```

**Thames river level stations only (Kingston upon Thames area)**

```json
{
  "lat": "51.4150",
  "lon": "-0.3089",
  "radiusKm": 10,
  "recordType": "stations",
  "maxItems": 10
}
```

**Scheduled flood monitor (only returns new warnings or changed river levels)**

```json
{
  "locations": ["51.5074, -0.1278"],
  "radiusKm": 20,
  "recordType": "all",
  "onlyNewSinceLastRun": true,
  "deltaName": "london-flood-watch"
}
```

### 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~uk-flood-warning-monitor/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"locations":["51.5074, -0.1278"]}'
```

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

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "uk flood warnings api" — the agent will find and run this actor.

# Actor input Schema

## `locations` (type: `array`):

Coordinates in 'lat, lon' format, e.g. '51.5074, -0.1278' (London). Or leave empty to use the Latitude/Longitude settings below. Area names like 'Kingston' are also accepted. Accepted formats: 51.5074, -0.1278, Kingston, Thames. You're only charged for the ones we actually find — a miss costs nothing.

## `lat` (type: `string`):

Latitude in decimal degrees (e.g. 51.5074 for London). Overridden if coordinates are given in the main Locations input.

## `lon` (type: `string`):

Longitude in decimal degrees (e.g. -0.1278 for London). Overridden if coordinates are given in the main Locations input.

## `radiusKm` (type: `integer`):

Search radius in kilometres around the specified coordinates (default: 15 km).

## `recordType` (type: `string`):

Choose whether to fetch active flood warnings, river monitoring stations with water levels, or both.

## `minSeverity` (type: `string`):

Filter flood warnings by minimum severity: Level 1 (Severe Flood Warning), Level 2 (Flood Warning), Level 3 (Flood Alert).

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

Maximum number of records to return per run (default: 20).

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

On: only flood warnings or river level readings that are new or have changed since your last run are returned and charged for — ideal for recurring schedules and alerts. Off: returns all matching records every time.

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

Optional name for this search's monitoring memory so you can distinguish multiple scheduled runs. Leave empty to auto-derive from coordinates and radius.

## `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 flood-record found gets its own row instead of being grouped under its location. You're still only charged once per location, 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.

## Actor input object example

```json
{
  "locations": [
    "51.5074, -0.1278"
  ],
  "lat": "51.5074",
  "lon": "-0.1278",
  "radiusKm": 15,
  "recordType": "all",
  "minSeverity": "all",
  "maxItems": 20,
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "searchSummary",
    "recordCount",
    "warningCount",
    "stationCount",
    "monitorStatus",
    "records",
    "recordType",
    "recordId",
    "title",
    "severity",
    "severityLevel",
    "riverOrSea",
    "areaName",
    "county",
    "town",
    "waterLevel",
    "waterLevelUnit",
    "typicalRangeLow",
    "typicalRangeHigh",
    "levelStatus",
    "warningMessage",
    "operationalStatus",
    "lat",
    "lon",
    "updatedAt",
    "sourceUrl",
    "isNew",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 1
}
```

# 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 = {
    "locations": [
        "51.5074, -0.1278"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/uk-flood-warning-monitor").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 = {
    "locations": ["51.5074, -0.1278"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/uk-flood-warning-monitor").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 '{
  "locations": [
    "51.5074, -0.1278"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/uk-flood-warning-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/uk-flood-warning-monitor"
        }
    }
}
```

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/BljyEqiyohOQxvVX0/builds/3i477KDk7gLEpuf24/openapi.json
