If icon
Return icon
Send icon
Schedule icon

Environmental Disaster Early Warning System

Reusable Kestra workflow for monitoring rainfall, soil moisture, and water-level signals and generating configurable early-warning alerts.

Categories
AIInfrastructure

Environmental Disaster Early Warning System

This Blueprint evaluates rainfall intensity, soil moisture, and water-level measurements against configurable warning and critical thresholds. It classifies conditions as HIGH, MODERATE, or NORMAL risk and can optionally notify an emergency contact through Twilio SMS.

How it works

  1. Provide environmental measurements and warning thresholds as workflow inputs.
  2. Compare rainfall, soil moisture, and water levels against critical thresholds.
  3. Generate a HIGH RISK alert if any critical threshold is reached.
  4. Otherwise, classify the situation as MODERATE if any warning threshold is reached.
  5. Report NORMAL CONDITIONS when all indicators remain below warning thresholds.
  6. Optionally send an SMS notification when high risk is detected and SMS is enabled.
  7. Run the assessment automatically every hour using the schedule trigger.

What you get

  • Configurable measurements and warning and critical thresholds.
  • Separate HIGH, MODERATE, and NORMAL risk assessment paths.
  • Human-readable alert messages containing the environmental measurements.
  • Optional Twilio SMS notifications for high-risk conditions.
  • An hourly schedule trigger for recurring risk assessments.

Who it's for

  • Teams monitoring flood and heavy-rainfall risks.
  • Environmental monitoring and disaster-response teams.
  • Operators tracking river, reservoir, and water-level conditions.
  • Teams exploring soil-moisture indicators for landslide risk monitoring.
  • Infrastructure and community safety monitoring initiatives.

Why orchestrate this with Kestra

Kestra organizes the assessment into reusable workflow tasks, supports configurable inputs, and routes execution through conditional branches. The schedule trigger supports recurring assessments, while the optional notification task integrates the workflow with Twilio. This makes the assessment easier to adapt, operate, and extend as monitoring needs evolve.

Prerequisites

The risk assessment can run without Twilio credentials when SMS is disabled.

Secrets

To enable SMS notifications, configure these Kestra secrets:

  • TWILIO_ACCOUNT_SID
  • TWILIO_AUTH_TOKEN
  • TWILIO_FROM_NUMBER
  • ALERT_PHONE_NUMBER

Set enable_sms to true only after the required secrets and phone numbers have been configured.

Quick start

  1. Import the Blueprint into your Kestra namespace.
  2. Set the rainfall, soil-moisture, and water-level inputs for your scenario.
  3. Adjust the warning and critical thresholds to match your monitoring needs.
  4. Run the flow manually to inspect the resulting risk assessment.
  5. Configure the required Twilio secrets and enable SMS if notifications are needed.
  6. Review the hourly schedule trigger before using it for recurring assessments.

How to extend

  • Connect rainfall, soil-moisture, and water-level inputs to real monitoring systems.
  • Adjust thresholds for local environmental conditions and validated operating procedures.
  • Add persistence or reporting tasks to retain assessment history.
  • Integrate additional notification channels for relevant response teams.
  • Add location metadata and escalation rules for monitored areas.

Links

Share this Blueprint
See How

New to Kestra?

Use blueprints to kickstart your first workflows.