Note: is partnering and will be involved with Notion -

AlertOps and

AlertOps’ alert management system can be integrated with to receive and respond to all (predefined status mappings) alerts through email, SMS, push notification or phone alerts. AlertOps would ensure that the alert/job status would reach the appropriate team by using proper workflows, escalation policies and schedules. Based on your ruleset, incidents can be automatically opened and closed, depending on what kind of alert reports.

The above scenario and scope for integration is due to the fact that AlertOps has a very flexible and simple API/Webhook configuration feature that can be leveraged with' automation capabilities.

AlertOps - Inbound Integration

We can define rulesets in AlertOps so that can send out alerts to the AlertOps platform. AlertOps would ensure based on these notifications received, that it would always reach out and assign to the correct person/team by utilizing its escalation policies, schedules, and workflow features.

AlertOps provides Inbound Integrations to integrate with numerous monitoring, chat and ITSM tools. You can configure an inbound integration for

At a high level this is how the flow looks like, you define an API integration in the AlertOps platform by defining settings like Integration Name, Escalation rules, recipient users/groups. Once an integration is defined, a unique API URL is generated. This acts as webhook or the gateway through which notifications from reach AlertOps and thus an incident/alert is created correspondingly. The API can be defined with various settings like URL mappings, filters, escalations etc. as required. has to be added with a Webhook action to an Automation Bot.

To configure an Inbound Integration in AlertOps to receive alerts from,

  • Under 'Integrations' select 'Inbound Integrations', select the category 'API' and then select add 'Add API Integration'

  • There are numerous integration options available in AlertOps, select

  • Once you selected the integration, you can then specify basic settings like the integration name, escalation policy, names of the recipients/groups for which the alerts must be assigned to.

  • Once you click save, the API Integration will be created, and you will be given a unique URL which acts as the access point and needs to be configured at the source (in this case, to send alerts. You can find the integration you just created, and you can give advanced settings and define various configurations for the alerts to be received and processed. For example, you can define when to open and close alerts based on the payload obtained from the API call, filters etc.

  • Make a note of the API URL, which will be used in, so it calls a HTTP POST request to this URL with the body in JSON format containing the alert specific information. AlertOps automatically creates an alert when the status variable (status) contains 'triggered'. The incident will also be closed automatically when the status 'ok' is received from

  • You can similarly define URL mappings as you want, owing to the flexibility provided by AlertOps’ OpenAPI/Plug-and-Play integrations. You can provide other filters and match with regex expressions as well. You can also test the generated URL with the sample data provided.

Configuration of for the integration,

  • In you can create automation for a lot of scenarios. Based on what trigger you set for your automation, you will have to setup a webhook action to execute and POST information that is necessary to AlertOps. The trigger can be anything, and you will have to change the JSON Payload accordingly.

  • Select the automation bot for which you want to configure the webhook. Add an action of type Webhook. Method will be POST.

  • Paste the AlertOps Inbound Integration API URL in the URL field.

  • Select Content Type as JSON

  • In the Data payload section, make sure that the JSON contains the following fields mapped to corresponding output fields from the trigger. Remember these fields are mandatory for AlertOps! You can add the rest of the fields as per your needs and map accordingly in AlertOps.


  • Notice that you have a 'status' key with a value 'triggered'. This is necessary to be added for the trigger to open an alert in AlertOps. You can have another trigger/template and a webhook action to trigger an 'ok' status to close alert in AlertOps.

  • Save.

Thats it! You have configured an Webhook action for a trigger. Any trigger alert will be sent to AlertOps for incident management.

Message logs, alert specific information can be viewed in the “Inbound Log” section in AlertOps Dashboard. Alerts can be viewed in the ‘Alerts’ tab as well.

Alert Triggering Information:

AlertOps will automatically create an incident when a new alert is received from when the status contains "triggered".

If an alert with status "triggered" matches an existing Open Alert, AlertOps will recognize the new alert as a duplicate and ignore the alert.

The alert will be recorded in the Inbound Messages table as “Mapped Appended.”

AlertOps will automatically close the same incident when an alert with status contains "ok".


AlertOps Integration Guides

General Restful API Guide Help Guide

Did this answer your question?