Notifications of malfunctions, downtimes or other critical events can be triggered automatically or manually in SIGNL4.
The automatic triggering takes place through the connection to third-party systems, via which triggering events can then be received.
SIGNL4 offers various connector apps, APIs and interfaces for these connections. A very generic and therefore most used interface is the SIGNL4 webhook for incoming events.
The webhook is essentially based on a unique URL that is entered in the third-party system and is called by it via HTTP(s) when a new event is present that is to be transmitted to SIGNL4.
How is the webhook created?
A webhook can be created automatically when a new team is provisioned (one for your first team is, during your initial SIGNL4 registration) and consists of a unique secret in the URL. Each created webhook at its URL can be viewed and copied under Integrations -> Installed (link here). The URL is shown when you open the detail pane of the according webhook. You can copy this URL and insert it at the appropriate place in the third-party system. An example URL is
You can add a new webhook any time, through the Gallery tab under the Integrations menu. With the help of Distributions Rules, events received through the webhook can be delivered to one or multiple teams in SIGNL4, resulting in alerts being sent out.
Authentication and security
The webhook uses a unique key, the so-called secret, for authentication. This secret is also a fixed part of its URL.
Since the webhook is only accessible via TLS, the secret itself can never be read in plain text during data transmission (it is located in layer 7 of the OSI model, TLS encryption already takes effect from layer 4 of the OSI model).
It is not possible to delete data via the SIGNL4 webhook. It is only used for event creation and can modify existing alarms. The URL should nevertheless be treated as highly confidential and only made accessible to authorized persons.