Home / Integration plugins / Zabbix & SMSEagle integration
ZABBIX logo beside SMSEagle logo on a black banner

Zabbix SMS & Voice Alerts.

Fail-Safe Delivery Over Cellular.

An outage is exactly when Zabbix alerts matter most, and when email, push, or cloud-based notifications can fail. SMSEagle is an on-premises hardware SMS gateway that delivers Zabbix alerts as SMS and voice calls directly over the cellular network, independent of your internet uplink.

Flow diagram: Zabbix API sends events to an SMSEagle gateway device, which delivers an SMS to the user.

Benefits

Verified security badge: blue shield outline with a dark circle and white checkmark indicating protection and trust.

Internet-independent alerting

Zabbix detects infrastructure anomalies, but delivering those alerts usually depends on your internet connection, mail server, or a cloud SMS provider. If any of these fails, the notification never reaches you. SMSEagle sends alerts directly over the mobile network, so they get through even when your internet link is down.

Icon depicting a hand interacting with a circular timer/clock motif and a rectangular element, suggesting a user action with time or sequencing

Dedicated, standalone
hardware

Software-based alerting often runs on the same virtualized infrastructure (e.g. Proxmox or VMware) it is meant to protect. If that platform fails, your alerting can fail with it. SMSEagle is dedicated hardware with its own cellular connection, so your alerting gateway doesn’t share fate with the servers around it.

Communication tower emitting radio waves from a tall antenna structure

No cloud, full data control

SMSEagle runs on-premises, so alerts aren’t routed through third-party cloud SMS providers. Messages are sent directly from on-prem device over the cellular network to mobile carrier, keeping alert data off external SaaS platforms.

How it works?

1

Event Trigger

Zabbix detects a problem or threshold breach.

2

Communication

Zabbix sends a webhook request to SMSEagle over the local network.

3

Alert

SMSEagle sends an SMS alert directly to the on-duty IT team.

IT infrastructure diagram: Zabbix monitors servers, routers, web apps, and desktops; alerts go via SMS gateway to admins

Integrate in 10 minutes

Set up reliable alerting using Zabbix’s built-in webhook integration to securely connect with your SMSEagle gateway. 
No internet required, no per-message billing, and full data privacy.

Key features

Native integration

SMSEagle plugs into Zabbix as a standard alert media type – no custom development. Configure it once and every trigger, escalation, and acknowledgment flows through your gateway out of the box.

SMS and voice alerts that
get noticed

A silent text is easy to sleep through. SMSEagle delivers Zabbix alerts as SMS and as text-to-speech voice calls, so a ringing phone wakes the responder. Pair it with Zabbix escalation chains and recipient groups, and each severity level reaches the right people through the channel they’ll actually notice.

Professional presenter holding a tablet, pointing to mobile messaging and voice chat icons on the side panel.
Man with a beard typing on a smartphone while seated at a laptop; blue SMS speech bubble indicates texting activity.

Acknowledge alerts by
replying to the SMS

When a Zabbix problem fires, your on-call engineer shouldn’t have to find a laptop and log into the web UI just to confirm they’re on it. With SMSEagle’s two-way support, they reply to the alert SMS and the problem is acknowledged directly in Zabbix. Faster response, a clear audit trail of who reacted, and no need for VPN or dashboard access at 3 a.m.

Recipient and escalation groups

Not every alert should go to everyone, and a missed alert shouldn’t go nowhere. SMSEagle lets you define recipient groups so each PRTG sensor reaches the right team. Escalation groups ensure that if the first person doesn’t acknowledge, the alert moves on to the next responder. Combined with on-call shift schedules, notifications follow your real duty roster instead of a static phone number.

Manage Group dialog: title 'Manage Group' with group name 'escalation', two checked options, interval 4 minutes, STOP word 'stop', and Save/Cancel actions
Dialog: Add Monitoring Task form with fields for task name, parent task, host, and test settings.

Monitor Zabbix itself

Who watches the watcher? If your Zabbix server goes down, it can no longer send a single alert, and you may not find out until it’s too late. With SMSEagle’s built-in Network Monitoring, the gateway independently checks your Zabbix server and sends an SMS or voice call the moment it stops responding. Your monitoring platform finally gets a monitor of its own.

About SMSEagle

SMSEagle’s a hardware SMS gateway. It’s used for sending and receiving notifications directly via the cellular network. The device runs on-premise, which means all data’s stored locally .

How to set up the integration

SMSEagle Setup

  1. Create a new user in SMSEagle (menu Users > + Add Users, user access level: “User”).
  2. Grant API access to the created user:
  3. click Access to API beside the newly created user
  4. Enable APIv2
  5. Generate new token
  6. For text messages, add access permissions in section Messages for: Send SMS, Send MMS.
  7. For voice call alerting, add access permissions in section Calls for: Make a ring call, Make a TTS call, Make a TTS Advanced call.
  8. Save settings

Zabbix Setup

The configuration consists of a media type in Zabbix, which will invoke the webhook to send alerts to SMSEagle device through the Rest API.

  1. In the Administration > Media types section, import the media_smseagle.yaml.
  2. Open the newly added SMSEagle media type and replace all <PLACEHOLDERS> with your values.
    The following parameters are required:access_token – API access token created in SMSEagle
    url – actual URL of your SMSEagle device (for example: https://10.10.0.100 or https://sms.mycompany.com)
    type
    – type(s) of message(s) to send. Possible values: sms, mms, tts and tts_adv, respectively for SMS, MMS, TTS Voice Call (text-to-speech call) and Advanced TTS Voice Call (high-quality audio conversion).
    Allows multiple types, separated by commas (e.g. “sms,tts_adv”).

Other required parameters are message type specific. More information can be found on our APIv2 page.

3. in the Administration > Users click on a User, and add a new media called SMSEagle. Enter SMS recipient. Available recipient formats:

  • Phone number: phone_number
  • Contact in SMSEagle Phonebook: contact_id:c
  • Group in SMSEagle Phonebook:group_id:g

Multiple recipients can be separated by comma.

For more information, please see Zabbix documentation.

Zabbix Template (optional)​

If you would like to add a ready-to-use Zabbix template for monitoring your SMSEagle device in Zabbix:

  1. Extended template repository + instructions (Zabbix 7.0+)
  2. Simple template repository + instructions (Zabbix 6.0+)

Acknowledge Events via SMS (optional)

Beyond sending alerts, SMSEagle lets your team acknowledge or unacknowledge Zabbix events directly by replying with SMS – no need to log in to the Zabbix interface. This capability is built on the SMSEagle Webhooks feature.

How to configure it

  1. In SMSEagle webGUI > menu Webhooks, create a new rule and set the method to POST (Zabbix).
  2. Choose the action type the rule should handle:
    • Acknowledge (ACK) – an incoming SMS acknowledges the event. Expected SMS format: ACK [eventid] [optional message] (e.g. ACK 12345 Problem resolved).
    • Unacknowledge (NOACK) – an incoming SMS unacknowledges the event. Expected SMS format: NOACK [eventid] [optional message] (e.g. NOACK 12345 Re-opening issue).
    • Acknowledge / Unacknowledge (ACK/NOACK) – a single rule handles both actions, with the action determined automatically by the SMS prefix (ACK or NOACK).
  3. Enter the Zabbix API URL (for example: https://10.10.0.100/zabbix/api_jsonrpc.php).
  4. Select the authentication type:
    • API Token – recommended for Zabbix 6.4 and newer. Don’t have a token yet? See Generating a Zabbix API token below.
    • Login / Password – for Zabbix older than 6.4.
  5. Enter the authentication credentials and save the rule.

 

Generating a Zabbix API token

If you chose API Token authentication (Zabbix 6.4+), here’s how to create one in the Zabbix frontend:

  1. Go to Users → API tokens and click Create API token in the top-right corner.
  2. Fill in the token details:
    • Name – a descriptive label, e.g. SMSEagle ACK.
    • User – the Zabbix user the token will authenticate as. 
    • Expires at – clear it for a token that never expires.
  3. Click Add.
  4. Copy and save the Auth token value in a safe place before closing the page, then click Close.
  5. Paste this value into the API Token field of your SMSEagle webhook rule.

 

Where to see the result

Once an acknowledgment is sent, the updated status appears in the Zabbix interface in two places:

  • Monitoring → Problems – the Ack column changes to Yes.
  • Monitoring → Problems → Event details – the full acknowledgment history is shown, including the message text, timestamp, and the Zabbix user who performed the action.

How to Monitor Your Zabbix Server? (optional)

Zabbix is a perfect monitoring tool, but what if the Zabbix server hardware fails? Even the best hardware can experience failures. That’s where SMSEagle steps in with its cool tiny feature called Network Monitoring. SMSEagle can monitor IP addresses or TCP ports and instantly send an SMS or make a call when a failure is detected. This ensures you can always keep an eye on your monitoring server.

Explore SMSEagle Demo device

SMSEagle is a hardware & software solution that guarantees a swift delivery of your messages to designated recipients, whether it’s for notifications, alerts, or important updates.

After registering to a demo you get a remote access to our physical device NXS-9750.

  • 14-days free trial
  • Access to over 20 functionalities

What is hardware
SMS Gateway?

Learn more about
SMSEagle features