TriggerDeck
Download on the App Store Get Started
Download on the App Store Get Started
Webhook Setup 2 min read

Configure Zabbix Webhook

Import the TriggerDeck media type and route push notifications with UNIQUE_UID.

Overview

This setup wires one TriggerDeck server registration to one Zabbix media target so alerts can arrive as iOS push notifications.

Prerequisites

  • The alert-gateway is reachable from Zabbix over HTTPS.
  • APNs credentials are configured on the alert-gateway.
  • The iOS app has push permission and shows a UNIQUE_UID in the edit flow for the target server.
  • TriggerDeck supports Zabbix Server 6.0 LTS, 7.0 LTS, and 7.4.
  • Additional compatible versions are 6.2, 6.4, and 7.2; support for these versions is restricted and untested.
  • Patch versions follow the status of their minor line.

1. Enroll app-side push target

  1. Open TriggerDeck on iPhone.
  2. Add or edit the target server connection.
  3. Open the server edit flow.
  4. Wait until the push section shows Ready.
  5. Copy the displayed UNIQUE_UID.

2. Import TriggerDeck media type in Zabbix

  1. Download the YAML file that matches your Zabbix branch:
  2. Open Zabbix UI and go to the media type import screen:
    • Zabbix 6.0 LTS, plus Zabbix 6.2 and 6.4 with restricted, untested support: Administration -> Media types -> Import
    • Zabbix 7.0 LTS and 7.4, plus Zabbix 7.2 with restricted, untested support: Alerts -> Media types -> Import
  3. Start the import flow.
  4. Upload the downloaded YAML file.
  5. Confirm import.

Imported media type name is TriggerDeck. The imported webhook endpoint is https://app.triggerdeck.io/v1/webhooks/zabbix.

3. Add media entry with UNIQUE_UID in user profile

  1. Open Users -> <target user> -> Media -> Add.
  2. Set Type to TriggerDeck.
  3. Set Send to to the copied UNIQUE_UID.
  4. Save and keep media enabled.

The same user can have multiple media entries for different TriggerDeck server registrations, because each server gets its own UNIQUE_UID.

4. Attach to action

Ensure your action sends both problem and recovery operations through this imported TriggerDeck media type so the mobile app can represent the event lifecycle consistently.

5. What to expect after setup

  • If UNIQUE_UID is outdated, pushes may not arrive.
  • If you reconnect the app or move to a new device, update the media entry with the latest UNIQUE_UID.
  • If pushes stop unexpectedly, open the app, confirm status is Ready, and re-test with a fresh event.

6. What does not happen

The webhook integration does not:

  • upload customer API tokens
  • replace direct browsing from the iOS app