Connect OwlHound to Zapier, n8n and Make
Turn an outage into a ticket, a spreadsheet row or a phone call, without writing a server. One webhook address, a documented message, and an API for everything else.
Send alerts to Zapier (about two minutes)
- In Zapier create a Zap and choose Webhooks by Zapier → Catch Hook as the trigger. Copy the address it gives you.
- In your OwlHound dashboard settings paste that address into the webhook field, press Save, then Send test. Zapier receives a sample message with every field filled in.
- In Zapier press Test trigger, pick the sample, and add your action: a Slack message, a Google Sheets row, a Trello card, an SMS from your phone provider, and so on.
The same steps work for n8n (Webhook node) and Make (Custom webhook): any public https address that accepts a JSON POST will do. Private and internal addresses are refused.
The fields you can map
| Field | What it holds |
|---|---|
event | monitor.down, monitor.up, monitor.still_down, ssl.expiring, domain.expiring, seo.issue or alert. Use it in a Zapier Filter step to react only to outages. |
status | down, up, warning or info. |
monitor, url | The name and address of the site, when the alert is about one site. |
started, ended | Unix timestamps for an outage's start and end (ended appears on recovery). |
cause | Plain-language reason, such as "HTTP 503" or "DNS lookup failed". |
subject, body, text | The same wording as the email, ready to paste into a message. |
source | Always owlhound. |
Read data instead of waiting for alerts
Zapier's Webhooks → Custom Request step (and n8n's HTTP Request node) can call the OwlHound API with a read-only key: list your monitors with their 24-hour, 7-day and 30-day uptime, or fetch recent incidents. A common recipe is a daily schedule that reads /api/v1/monitors and writes the uptime figures into a spreadsheet for client reporting.
Ideas that work well
- Outage creates a ticket in your helpdesk, recovery closes it.
- Post "site down" to a client's Slack channel while you investigate.
- Append every incident to a Google Sheet for a monthly review.
- Call your on-call phone through your telephony provider when
eventismonitor.down.
An official OwlHound app in the Zapier directory is not available yet; the webhook and the API cover the same ground today.
Frequently asked questions
Can I send to more than one Zap?
One webhook address per account. Point it at a single Zap or n8n flow and branch from there.
Will my automation get duplicates?
Each outage sends one message when confirmed, optional reminders if you switch them on, and one when it recovers. Failed deliveries to your webhook are not retried; the email alert always goes out.
Does it cost extra?
No. Webhooks and the API are included on every plan; Zapier and similar tools have their own pricing.
Start watching your site in minutes
Free for up to 10 sites, no card. No installs and no passwords — we only check public pages.