Mobile alerting with tracking & escalation for Crosser



Crosser an Industrial IoT platform for easy integration and automation of connected devices. Pairing this powerful IoT platform with SIGNL4 can enhance your daily operations with an extension to your mobile team in the field or on the shop floor.

 How it Works

All it takes to pair Crosser and SIGNL4 is an HTTP Request action in Crosser Cloud that calls the SIGNL4 webhook to trigger the alert.

 Integration Capabilities

  • Alert service engineers via mobile push, text and voice
  • Staff can acknowledge and take ownership for critical events that occur
  • Alerts are escalated in case of no response
  • Communicate within an alert to address a particular problem
  • Alert on critical device states
  • Two-way integration to interact or set the device state


  • Industrial IoT
  • Industry 4.0
  • IoT Service Alerting
  • IoT Device Management
  • Finance, Security, IT, Healthcare, Manufacturing, Utility, Oil and Gas, Agriculture, etc.

How To Integrate

Integrating SIGNL4 with Crosser

In our example we create a sample flow that receives OPC UA data, processes them and then generates an alert in SIGNL4.

SIGNL4 is a mobile alert notification app for powerful alerting, alert management and mobile assignment of work items. Get the app at

In order to show the concept in a simplified way we also use a data generator that is capable to generate sample data. This makes it easy to simulate alerts.


A SIGNL4 ( account

A Crosser ( account

Integration Steps

1. Create the Data Generator

Logon to the Crosser portal and go to Flows. Here you can add a Data Generator action. This one simulates random event data in certain intervals.

2. Date Aggregation (Optional)

The next step in the flow is the aggregation. This is optional but since it is a powerful feature we show it here. The idea is to read events over a certain period of time and then aggregate the data. In our case we are interested in the average temperature.

3. Property Mapper

The idea of the Property Mapper is to assemble the message data we would like to send to SIGNL4. SIGNL4 requires JSON data.

The property:

body.Message: “Temperature too high.”

will become this in JSON:

{“Message”: “Temperature too high.”}

Besides the property mapping we can also add conditions here. We can do so in the Common section of the Property Mapper.

We add the following Message Filter:

agg.average > 10

Which means that the average temperature must be greater than 10 in order to proceed with the flow.

4. Make it JSON

The next step is to JSONify the properties and values. In order to do so you can just add the JSON action and keep all the default properties there.

5. Send SIGNL4 Alert

Last but not least we add our SIGNL4 action. This is an HTTP Request. The URL is your SIGNL4 webhook with your team secret:

The method (Verb) is Post (HTTP Post) and Body remains empty. This is because we have assembled the JSON body in the steps above.

6. Test It

This is it. You can now connect your flow to a node (Connect Node -> Select or create a Sandbox node), save your flow and now sample data is being generated and you should receive SIGNL4 alerts on your phone.

You can find a sample script in GitHub:

Alert Optimization

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.


Assemble your SIGNL4 team today!


Related Integrations


Industry 4.0 / IoT / IT Ops

PTC ThingWorx

IoT / IT Ops


Business / IoT


Industry 4.0 / IoT / IT Ops

Google IoT Core

Industry 4.0 / IoT