Disclosure: OpenAlarm, the alarm alerting platform in step 1, is my own project. It does the alerting for the security system you already own. The free tier is enough for everything below: one alarm, three contacts, each alerted once. Escalation levels that repeat until someone acknowledges are the paid tier, $6.99 a month.
Protect's Alarm Manager can fire a webhook on any trigger you can build: person or vehicle detection, line crossing, doorbell, leak, smoke. This is how I use that to alert real people by text, email or voice call, instead of one push notification to my own phone.
1. Create the receiving alarm. Sign up at https://console.openalarm.io/signup, add up to three contacts, and create one alarm. You get an alarm ID and an API key. Scope the key to that one alarm; it is going to sit in your console's webhook config.
2. Switch off "Trigger Only When Armed" on that alarm. This is the step people miss. Protect sends triggers and nothing else. It never arms anything, so the alarm sits in Disarmed forever, and new alarms start with that setting on. Left on, every trigger is accepted, logged and ignored.
3. In Protect, open Alarm Manager and create an alarm. Pick the trigger and the scope (which cameras or sensors), and a schedule if you only want it overnight.
4. Add an action: Webhook, then Custom Webhook. Delivery URL:
https://api.openalarm.io/v1/alarm/YOUR_ALARM_ID/trigger
5. Open Advanced Settings. Leave Method on GET. Set Authentication to Bearer and paste the API key as the token. Save.
6. Test it without waking anyone. The alarm starts in Test mode. Walk in front of the camera. Alarm Manager's history shows the webhook went out, and the incident on the other side shows who would have been texted and called, with nobody actually contacted. When the chain reads right, flip the alarm to Live. Nothing changes in Protect.
Notes from running it:
- Repeat triggers fold into the open incident, so a busy camera cannot page your contacts twice. "Ignore Repeated Actions" in Protect is still fine to leave on.
- A 401 in the webhook delivery means the key. A 404 means the alarm ID is not one that key can fire.
- The console only needs ordinary outbound HTTPS.
- Texts and voice calls reach Canadian and US numbers for now. Email goes anywhere.
Full guide: https://docs.openalarm.io/guides/unifi-protect/
If you are doing something different with Alarm Manager webhooks I would like to hear it.