Overview
Zabbix is an open-source enterprise monitoring solution. Easyalert receives alerts from Zabbix via webhook media type, automatically creating incidents from trigger events.This integration works with Zabbix 5.0+ which supports native webhook media
types.
Requirements
- Zabbix 5.0 or higher (for Webhook media type support)
- Easyalert account and active tenant
- Admin privileges in Zabbix
Setup Instructions
1
Create Integration in Easyalert
- Go to Integrations page from left menu
- Click Add Integration button
- Select Zabbix as Source Type
- Enter a name (e.g.,
Zabbix Production) - Click Create to save
- Copy the generated Webhook URL
Example: https://api.easyalert.io/api/v1/webhooks/ingest/wh_abc123...
2
Create Media Type in Zabbix
Go to Administration → Media types → Create media type
3
Add Parameters
Click Add link to add each parameter one by one:
4
Add Webhook Script
Copy this script into the Script section:
5
Add Message Templates (Required)
Switch to Message templates tab and add these two templates:Problem:
Problem Recovery:
6
Configure Other Settings
7
Create Webhook User
Go to Administration → Users → Create user
Switch to Media tab and click Add:
8
Create Action
Go to Configuration → Actions → Trigger actions → Create actionAction Tab:
Operations Tab - Click Add:
Recovery Operations: Add same settings for resolved alerts.
Field Mapping
Easyalert automatically maps Zabbix fields:Severity Mapping
Status Handling
Recovery events (OK status) automatically resolve the corresponding incident.
Using Tags
Zabbix tags are used for routing in Easyalert.Where to Define Tags
Example Tags
Usage in Easyalert
In Escalation Routing:Test
After completing Zabbix setup, you can test manually:Troubleshooting
Alerts not being received
Alerts not being received
- Check if Media Type is active 2. Verify media is added to user 3. Check if Action is enabled 4. Review Zabbix action logs for errors
Wrong severity mapping
Wrong severity mapping
- Check if Zabbix sends numeric (0-5) or text severity 2. Configure appropriate severity mapping 3. View webhook samples to see actual values
Recovery events not resolving incidents
Recovery events not resolving incidents
- Verify recovery operations are enabled in Zabbix action 2. Check the
trigger_statusfield is included in payload 3. Ensure event_id matches between PROBLEM and OK events
Connection refused
Connection refused
- Check firewall/network settings 2. Verify Zabbix server can reach Easyalert API 3. Test connectivity with curl from Zabbix server
Best Practices
Include Trigger URL
Include Trigger URL
Add
{TRIGGER.URL} parameter to help responders quickly navigate to Zabbix
for more details.Configure Recovery
Configure Recovery
Enable recovery operations to automatically resolve incidents when the
problem clears.
Test with Low Severity
Test with Low Severity
Use Information or Warning severity triggers for initial testing to avoid
unnecessary escalations.
Organize with Host Groups
Organize with Host Groups
Use Zabbix host groups to organize hosts and include group info in tags for
routing.

