Skip to main content

Overview

Zabbix has no standardized webhook format. The integration uses a webhook media type that builds aciona.me’s canonical payload from the event macros.

Prerequisites

  • Zabbix with admin permission to create media types and actions.
  • A service created in aciona.me and linked to a team with an active schedule.

1. Create the alert source in aciona.me

Under Alert sources, create a source of type Zabbix. Copy the URL and the token.

2. Create the media type

Under Administration → Media types → Create media type:
  • Type: Webhook
  • Parameters:
Adjust the deeplink domain to your Zabbix. Validate the script in a test environment before applying it in production.

3. Create the action

Under Configuration → Actions → Trigger actions, create an action whose operation sends the notification through the aciona.me media type.
The action must fire on PROBLEM and RECOVERY. Zabbix already does this by default — just confirm there is no condition filtering it to PROBLEM only. Without the recovery event, incidents never close on their own.

4. Test

Force a trigger to fire (or use a test trigger) and confirm the incident in the dashboard. Then let the trigger return to normal and confirm the automatic resolution.

How fields are translated

State

value takes precedence over status.

Severity

Service

The service hint comes from {HOST.NAME}. Either create services in aciona.me matching your hosts’ visible names, or set a default service on the source.

Required fields

triggerId and name are required. Without them the request is rejected with 400.

Troubleshooting

The action is filtered to PROBLEM only. Remove the condition so it also fires on RECOVERY.
trigger_id or event_name are missing from the media type parameters. Check the configured macros.
Check the Zabbix server logs (the script logs at levels 3 and 4). Confirm the server has outbound HTTPS to ingress.aciona.me.