TriggerDeck
Download on the App Store Get Started
Download on the App Store Get Started
Product Tour 2 min read

Configure Notifications

Connect iOS permission, per-server push readiness, and the Zabbix webhook setup needed for APNs delivery.

Start inside the app

TriggerDeck keeps push readiness visible from two places:

  • Settings, where the operator can verify iOS authorization and whether the alert-gateway is reachable
  • the server edit flow, where the app shows the per-server registration state and exposes the UNIQUE_UID

This split matters because push is optional and intentionally separate from direct browsing. Operators should first confirm the app is ready locally before an administrator finishes the server-side Zabbix steps.

Flow shown on screenshot

Settings push status

Open Settings and focus on the Push Notifications block where authorization and Alert Gateway state are shown together. This frame should explain what the app can verify locally before any server-side Zabbix configuration starts.

Use the server-specific UNIQUE_UID

Every configured server has its own push identity. The docs should show that the operator copies the UNIQUE_UID from the correct server edit flow instead of treating push setup as one global device setting.

Flow shown on screenshot

Server-specific push identity

Open Edit Current Server and show the UNIQUE_UID with push status and copy hint in one cropped frame. This screenshot should make it explicit that push identity belongs to the selected server, not to a global app-level setting.

Finish the routing in Zabbix

The mixed user/admin docs path should then walk through the Zabbix-side configuration:

  1. import the shared TriggerDeck media type
  2. create a user media entry with the copied UNIQUE_UID
  3. attach that media type to the relevant action path

Flow shown on screenshot

Zabbix media type import

In Zabbix web UI, navigate to media types and show the TriggerDeck YAML import action area. Keep the import context and dialog controls visible to document the exact handoff from app readiness to server-side routing setup.

Flow shown on screenshot

Zabbix user media entry with UNIQUE_UID

Open user media configuration in Zabbix and show media type selection with the Send to field populated by a scrubbed UNIQUE_UID. This frame should explain the final routing link between a specific server registration and Zabbix alert delivery.

Explain the trust boundary clearly

  • Browsing data still comes directly from the iPhone to Zabbix.
  • The alert-gateway is only for push routing.
  • Reinstalling the app or changing registrations can require updating the UNIQUE_UID in Zabbix.