Alerts
Create Your First Alert
Build a first alert with a clear scope, a single trigger condition, and a destination email.
Start with one simple alert. Add complexity later.
What every alert needs
- Destination: who receives the email.
- Scope: which locations it covers.
- Trigger: what NOTAM condition should fire it.
Recommended first alert
- Email to the operational inbox.
- Limited to the primary airports you monitor.
- Triggered by one condition, such as closed runway or unavailable fuel.
This makes validation simple. If the alert is noisy, you know exactly what to tune.
Naming
Alert names are optional but recommended. Good names make the alert list scannable:
Core hubs runway closuresNight shift fuel watchAlternates restricted aerodrome
Configuration advice
Avoid combining too many conditions in the first alert. Do not mix dozens of ICAOs, narrow time windows, affected elements, and lifecycle logic until you know the simpler version works.
You can pause an alert to keep its configuration without receiving emails. You can also duplicate an existing alert as a starting point for a new one.
Next step
Continue with Targeting and Filters.