Skip to content
HonkWatch
PricingLocationsHonk RadarHelpAPI Log inGet started
All help topics

Getting started

  • Getting started
  • How checks work

Monitors

  • Which monitor to use
  • Website monitor
  • API monitor
  • Keyword monitor
  • Ping monitor
  • Port monitors (TCP and UDP)
  • DNS monitor
  • SSL certificate monitor
  • Domain expiry monitor
  • Third-party services
  • Page load monitor
  • Heartbeat monitor (cron jobs)
  • Maintenance windows
  • Incidents

Alerts

  • Setting up alerts
  • Email alerts
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • PagerDuty
  • ntfy
  • Webhooks
  • Zapier

Phone and desktop app

  • The phone and desktop app
  • App alerts not arriving

Status pages

  • Status pages
  • Status page on your own domain

Team and account

  • Team members
  • Plans and limits
  • API keys and the API
  • Your account

Troubleshooting

  • A monitor says down but my site works
  • I did not get an alert
  • Allowing our checks through a firewall
  • Questions and answers

Help / Alerts

Zapier

A Zapier channel passes each alert to a Zap. From there you can send it on to any app Zapier connects, such as a spreadsheet, a ticket system or a chat app HonkWatch does not cover.

What you need first

  • A Zapier account that can use Webhooks by Zapier. Check your Zapier plan if you are not sure.
  • A confirmed HonkWatch account. Until you confirm your own email address, alerts can only go to that address by email.

Make a Zap with a Catch Hook

If these steps do not match what you see, follow Zapier's own guide, Trigger Zaps from webhooks.

  1. In Zapier, make a new Zap.
  2. For the trigger, choose Webhooks by Zapier, then the event Catch Hook.
  3. Copy the webhook URL Zapier gives you. It starts with https://hooks.zapier.com/hooks/catch/.
  4. Leave the Zap open. You will come back to it after sending a test.

Add it in HonkWatch

  1. Open Alerts and go to Add a channel.
  2. Under Where should alerts go?, choose Zapier.
  3. Paste the Catch Hook URL into Send to.
  4. If you like, fill in Label (optional) with what the Zap does.
  5. Tick the events to send: Down, Back up, Certificate expiring and Slow.
  6. Press Add channel.

Send a test and finish the Zap

  1. In the channel list on Alerts, press Send test on the Zapier row.
  2. Back in Zapier, test the trigger. Zapier should find the request, with event set to test and a monitor called "Test monitor".
  3. Add the action you want, using the fields from the test, such as the monitor name, the event and the detail.
  4. Turn the Zap on.

What we send

Zapier gets the same JSON as a webhook channel. The main fields are:

FieldWhat it holds
eventdown, up, ssl, slow, dns or test. Maintenance windows that tell people when they start and end send maintenance_start and maintenance_end, with a maintenance object instead of monitor.
atWhen the alert was made, in UTC.
detailThe reason in plain words.
urlThe monitor's page in HonkWatch.
monitorThe monitor's id, name, type, target and status.

To act only on some events, add a Filter step in the Zap on the event field, or untick events on the channel.

Using your API key instead

Zapier, Make and n8n can also subscribe to alerts with your API key from Settings, without adding a channel here. See API keys and the API.

If it does not work

  • You see "Use the Catch Hook URL from Zapier (hooks.zapier.com)". Only Catch Hook URLs that start with https://hooks.zapier.com/ are accepted. Copy the URL from the Catch Hook trigger again.
  • Zapier finds no request when you test the trigger. Press Send test again in HonkWatch, wait a few seconds, then test the trigger again in Zapier.
  • Recently sent shows failed. Zapier refused the request. The Zap may have been deleted. Make a new Catch Hook, add its URL as a new channel here, and remove the old channel.
  • Recently sent shows sent, but the action did not run. Check that the Zap is turned on, and look at its run history in Zapier.
← Webhooks The phone and desktop app →

Still stuck? Email [email protected] and say which guide you were following.