Skip to main content

📅 Look-ahead awareness

The alarm evaluates daily forecast data for up to 14 days ahead, so you can prepare before adverse conditions arrive.

📍 Location-enriched

Every payload carries precise coordinates alongside city and district identifiers, making geo-routing effortless.

⚠️ Targeted violations

Only metrics that actually breach your configured thresholds appear in violations — no noise, no guesswork.
1

Identify the monitoring point 🔍

Use registrationId or recipientId to look up which of your assets or customers this alarm concerns — pair it with city / district for a quick human-readable summary.
2

Triage violations ⚠️

Iterate over violations and map each metric to your internal risk policies. A single alarm can bundle multiple metrics (e.g. simultaneous heavy rain and strong gusts), so evaluate each entry independently.
3

Trigger downstream automation 🤖

Use forecasts[].time to schedule time-boxed actions — for example, send a heads-up notification at T-3h before the first threshold breach, and escalate if value keeps climbing across consecutive slots.