VoxiSMS turns a monitoring notification into an SMS by letting Zabbix, Nagios, or Prometheus send event data to Zapier or Make. The automation passes the recipient and message to VoxiSMS, and the connected Android phone sends it through its own SIM and mobile number.
The monitoring platform decides when to create the notification. VoxiSMS handles the final SMS delivery step through your connected Android phone.
Keep the monitoring logic where it already lives. The automation receives the event, shapes the message, and hands it to the Android sender.
Each platform exposes a different notification mechanism, but all three can hand event data to the same webhook-led automation.
| Monitoring tool | Notification method | Automation receiver | Delivery step |
|---|---|---|---|
| Zabbix | Custom webhook media type and alert action | Zapier Catch Hook or Make Custom webhook | VoxiSMS action |
| Nagios Core | Host or service notification command | Zapier Catch Hook or Make Custom webhook | VoxiSMS action |
| Prometheus | Alertmanager webhook receiver | Zapier Catch Hook or Make Custom webhook | VoxiSMS action |
Use the notification mechanism documented by your monitoring tool. These setup paths keep the implementation focused on moving a useful event payload into the SMS action.
Zabbix supports a custom webhook media type that can make HTTP requests. Use it to pass selected alert macros to the webhook URL created in Zapier or Make.
Nagios uses notification commands for host and service events. A command can POST the relevant Nagios macros to the receiving webhook before the automation builds the SMS.
Alertmanager routes alerts to receivers and includes a generic webhook receiver. Point that receiver at the Zapier or Make URL, then map the payload fields needed for the SMS.
Choose the automation builder your team already uses. Both paths receive the monitoring event before passing the recipient and message into VoxiSMS.
Choose Webhooks by Zapier as the trigger and use Catch Hook for a parsed request. Send a sample from the monitoring tool, map the fields, then add VoxiSMS as the action.
Zapier documents Catch Hook as a unique URL that accepts GET, PUT, or POST requests and exposes parsed fields to later Zap steps.
Start the scenario with Webhooks > Custom webhook, send a sample event so Make detects the fields, then map the recipient and message into the VoxiSMS module.
Make documents Custom webhooks as HTTPS URLs that external services can call to trigger a scenario.
Keep each text specific enough to identify the event without copying a full monitoring payload into the message.
| Trigger | Useful fields | Example message |
|---|---|---|
| Zabbix host event | host, event, time, detail URL | [Host] reported [event] at [time]. Check [approved detail URL]. |
| Nagios service notification | service, host, state, output | [Service] on [host] changed to [state] at [time]. [Short output]. |
| Prometheus alert | alert name, instance, status, runbook URL | [Alert name] is [status] for [instance]. Check [approved runbook URL]. |
| Backup check | job, system, result, time | Backup [job] on [system] finished with [result] at [time]. Review [approved URL]. |
| Certificate check | domain, remaining days, owner | Certificate for [domain] reaches its renewal window in [days] days. Owner: [team]. |
The VoxiSMS Android SMS gateway uses the mobile plan already active on the connected phone. The recipient sees that real mobile number, and VoxiSMS adds no per-message fee.
The monitoring tool creates the event, the webhook starts the automation, and the Android phone sends the final text.
Swipe horizontally to inspect each workflow step.
Use one controlled monitoring event and one recipient while you verify the route. Expand the workflow only after that message arrives with the expected details.
Install VoxiSMS from Google PlayInstall VoxiSMS on the Android phone whose mobile number should send the alert, then keep the device online and powered.
Use Zapier Catch Hook or Make Custom webhook and copy the generated URL into the monitoring tool's notification setup.
Trigger a controlled notification so the automation can expose the host, service, state, message, time, and detail-link fields.
Choose the Android device, set the intended team number, and build the SMS from only the fields that help the recipient identify the event.
Run the same controlled event again and check the received text, sender number, message variables, and approved destination link.
A controlled event should prove the webhook, field mapping, message, Android sender, and destination in one pass.
Clear answers about Zabbix, Nagios, Prometheus, webhooks, Android delivery, and message content.
Yes. Configure a Zabbix custom webhook media type to send selected alert fields to Zapier or Make, then use VoxiSMS as the SMS action. The connected Android phone sends the message from its own SIM and mobile number.
Use a Nagios host or service notification command to POST event fields to a Zapier Catch Hook or Make Custom webhook. The automation maps those fields into the VoxiSMS action.
Yes. Alertmanager has a generic webhook receiver. Point it at the Zapier or Make webhook URL, map the useful alert fields, and let VoxiSMS send the resulting text through the connected Android phone.
No. VoxiSMS adds no per-message fee. The Android device sends through the mobile plan already active on its SIM.
Keep it practical: name the host or service, state what changed, include the event time, and add one approved detail or runbook link when the recipient needs more context.
Connect one monitoring notification to Zapier or Make, pass it to VoxiSMS, and test the complete route through your Android phone.
