An Outbound Integration allows you to send messages to an external system such as Salesforce, Remedyforce, ServiceNow, or JIRA.

Outbound Integrations can be found Under Integrations > Outbound Integrations from the Main Menu:

Things you can do with the AlertOps Outbound API are almost limitless when combined with Workflows and Escalation Rules:

  • Send whatever JSON packet is required by the external service.

  • Map any AlertOps standard field plus any custom fields you have defined.

  • In combination with Workflows, Escalation Rules and the Inbound APIs, build very powerful automations. For example, you can automatically close tickets in an external system like Service Now or JIRA when the AlertOps alert has been resolved.

  • Add status updates to an external system --  for example, when an owner has been assigned in AlertOps.

Outbound Integrations have two parts: The Service Detail, which includes security credentials, naming and the top level for any Methods:

Methods are the second part of an Outbound Integration. These are the individual actions triggered via API (Create, Update, Close, etc) that the integration supports.

You can use an outbound integration in one of two ways:

  1. Create a Workflow that automates invoking the Methods on alert events, such as Assignment, Close or when notifications are sent to users (Delivery Attempts). The Workflow is then added to a Escalation Rule.

  2. On demand. Manually invoke the Methods. The Methods can be added directly to the Escalation Rule

Configuring an Outbound Integration:

Outbound Integrations are effectively API Calls that can be configured to trigger via one of the above listed options. When you've created your Outbound Integration, you can then add methods.

Methods are essentially API Calls to trigger an action on a 3rd party system. These have all of the parts of a basic API Call: URI, Body, Headers, Request Data.

The other piece of an Outbound Integration is the Response Data. The Response Data allows you to update fields within your Alert based on the values returned by the 3rd party system. For example, update Ticket ID field once a ticket is created.

Did this answer your question?