Mobile alerting with tracking & escalation for Acure



Acure is a leading all-in-one cloud-hosted AIOps observability and automation platform to increase your observability and automate remediation. There is a free version available, too.

SIGNL4 extends Acure and adds app-based mobile alerting and incident response including push, SMS text, voice calls, escalations and collaboration. The integrated duty planning helps you to schedule your team’s on-call duties and allows you to see who is on duty at any given time.

 How it Works

Acure uses webhooks to submit problem information to SIGNL4. You can simply configure this by using the provided script. Specifically the integration helps you with the following.

  • Forwards Acure events to SIGNL4 for mobile alerting
  • Uses HTTP requests / webhook to connect to your SIGNL4 team
  • Staff can acknowledge and take ownership for critical events that occur
  • Communicate within an alert to address a particular problem
  • Alerts are escalated in case of no response
  • On-call scheduling to alert the right people at the right time
  • Alerts closed in Acure will automatically close the alerts in SIGNL4, too


  • 24×7 IT operations with on-call staff
  • Critical IT alerting
  • Customer service hotline
  • Anywhere critical incidence response
  • On-call scheduling of IT / network teams


  • Significantly shorter response times for IT incidents, thus shorter mean time to repair (MTTR)
  • Ensures attention for critical alerts and minimizes false alerts
  • Clear responsibilities and transparent ownership of IT incidents
  • Collaboration with team members when assistance is needed

Problems detected in Acure are sent to SIGNL4 via HTTP request

Event categorization, routing and automated delivery

Persistent Notifications by push, text and voice call with Tracking, Escalation and Confirmation to Staff on Duty


You configure SIGNL4 alerting in the Acure web portal.


In the Acure portal under Actions -> My Scripts you add a new script like the one below. Here, {team-secret} needs to be replaced with your SIGNL4 team secret.

For closing alerts in SIGNL4 when the problem gets cleared in Acure you can modify the X-S4 parameters as described here.


-- SIGNL4 Webhook API:

-- Specify your SIGNL4 team secret here
local teamSecret = "team-secret"

local requestBody = {
    subject = subject,
    body = body
-- External ID and Status can be used to close an alert in case the problem is cleared in Acure
requestBody["X-S4-ExternalID"] = ""
requestBody["X-S4-Status"] = ""
requestBody["X-S4-Location"] = ""
requestBody["X-S4-SourceSystem"] = "Acure"

local args =
  uri = "" .. teamSecret,
  method = "POST",
  body = json.encode(requestBody),
  mediaType = "application/json"
local response = curl(args)
if (response.err ~= nil) then
  return -- Exit the script early if an error occurs

if ( == true then
  print(":( status code " ..

You can adapt the parameters according to your needs.



Now you can setup a Rule and an Action under Actions -> Rules&Actions. The Action calls the above SIGNL4 script and the Rule specifies the conditions and then calls the Action.

This is it. Now your SIGNL4 team gets an alert each time Acure detects a critical problem.

SIGNL4 can further increase the visibility of alerts through its Signals and Services section. Augmenting the color and icon of alerts will provide more relevant information at a glance without having to open the alert.


Change alert color and override title + text 

Override text, colors and titles are triggered by keywords set within the mobile app.

Related Integrations

Camunda BPM




Gimasi Service Button



IoT / IT Ops

ifm IO-Link

Industry 4.0 / IoT

Melrose Labs SMS

Industry 4.0 / IoT

PRTG Network Monitor

IoT / IT Ops


IoT / IT Ops



Ready for a free 30-days trial?