The Alert Manager (Settings → Alert Manager) is Sentinel’s automation surface: when a chosen kind of alert lands, a rule fires — a signed webhook to your systems, or a drone response flight straight to the animal.
Settings → Alert Manager: the rules table and recent deliveries log

​
Building a rule

New rule walks through three steps:
1

Events

Pick which of the six event kinds fire the rule — cast and distress are preselected, the two where minutes matter — and scope it to one farm or all.
2

Action

Call a webhook — a JSON POST per event, optionally signed (X-STrack-Signature, HMAC-SHA256) and retried on failure. Or Launch a drone mission — either a saved planned mission, or fly to the animal’s last known location, hover for eyes-on, and return to base. A per-device throttle (default one notification per 5 minutes) keeps a beaconing tag from flooding the channel.
3

Review

Name the rule, read the plain-English summary of what it will do, and enable it.
The rule wizard: choosing events that fire the rule
Drone actions need the Drone missions plan feature, a drone base on the farm, and a recent position for the alerting animal to fly to.

​
Deliveries and testing

Every firing is logged under Recent deliveries — rule, event, status (sent / pending / failed with the error), HTTP response and time. Test on any webhook rule queues a synthetic delivery through the real dispatcher — same signing, same retries — so you can prove the receiving end works before a real cast does. Delivery runs on the ingest service; coverage of the alert stream — what fired, what fell through — is charted on Alert Automation.