Integrate with your favorite tools using a custom webhook. Configuring a custom endpoint will allow you to send notifications to your preferred apps, even if they aren’t on the list of preconfigured options.

Custom endpoints offer the advantage of allowing you to customize the message body too.

Adding a custom endpoint

Allow firewall access

Set up your systems to receive notifications from log alerts can only be sent on ports 80 & 443. If you try setting another port in your endpoint, the alert will NOT be sent.

If you need to, whitelist the relevant IPs in your firewalls. These depend on the region where your account is hosted:

Region slug Whitelisted IP
Create a verification token (Best practice but optional)

The IP range is used by all customers and should be used together with a verification token.

If you decide to open a port on your firewall for a custom endpoint, we strongly advise that you add a verification token in the JSON payload of the custom endpoint and verify that the token exists on the receiving end.

It is best to restrict external access only to this specific endpoint.

Here’s an example of a JSON payload for an alert that includes a verification token:

"token": "<SomeSecurityToken>",
"alert_title": "{{alert_title}}",
"alert_description": "{{alert_description}}",
"alert_severity": "{{alert_severity}}",
"alert_event_samples": "{{alert_samples}}"
Add the endpoint
  1. To add a new custom endpoint, click Add endpoint.
  2. Specify the URL, method, and headers.
  3. For POST/PUT methods, you can add a payload with a message.

Some endpoints require a particular attribute/payload. For example, Microsoft Teams.

Configure a custom endpoint

Test the endpoint (Optional)

Click Run the test to test your endpoint. shows if the message was successfully sent.

Check that the message arrived at the target endpoint.

Save the endpoint

Save your endpoint.