Customizing the HTTP Action Template

Download this manual as a PDF file

This section describes how to customize the automation action template included in the HTTP Action Type PowerPack to create automation actions that meet your organization's specific requirements.

Use the following menu options to navigate the SL1 user interface:

  • To view a pop-out list of menu options, click the menu icon ().
  • To view a page containing all of the menu options, click the Advanced menu icon ().

Customizing the HTTP Action Type Automation Action

The HTTP Action Type PowerPack includes an automation action template that uses the "Make an HTTP Request 2.0" action type to send an HTTP request to a third-party system.

After you edit the action and trigger the event policy, SL1 will trigger the request and add a new event log to the respective device on the Event Console page.

To edit the "HTTP Action Template" automation action included in the PowerPack:

  1. Go to the Action Policy Manager page (Registry > Run Book > Actions).

  1. Locate the "HTTP Action Template" automation action, and then click its wrench icon (). The Editing Action page appears.

  1. In the Action Policy Editor page, supply a value in each field.
  • Action Name. Specify a new name for the action policy.
  • Action State. Select whether the policy can be executed by an automation policy (enabled) or cannot be executed (disabled).
  • Description. Type a detailed description of the action.
  • Organization. Select the organization to associate with the action policy.
  • Action Type. Select the type of action that will be executed. The HTTP Action Type PowerPack uses the Make an HTTP Request (2.0) Action Type.
  • Execution Environment. Select from the list of available Execution Environments. The default execution environment is System.
  • Action Run Context. Select Database or Collector as the context in which the action policy will run.

  1. In the Input Parameters field, you can change the values of the following parameters:

  • credential_id. The ID of a SOAP/XML credential the action policy should use to make the HTTP request. If you want the credential to be determined by the "dynapp_guid" parameter or if you are using the "url_override" option, the value of this parameter should be "0".
  • dynapp_guid. The Dynamic Application GUID with a credential the action policy should use to make the HTTP request. If you are using the "url_override option", this parameter should be empty.
  • url_override. The URL of the webhook created from your third-party system.
  • relative_url. Typically, the string appended to the end of the URL in the associated credential before making the request. You can use this parameter if you do not need to use authentication or other options in a SOAP/XML credential.

    • NOTE: If you use the "relative_url" option and do not specify a payload, the action will perform a GET request. If you use this option and specify a payload, the action will perform a POST request.

  • payload. This parameter is sent in the body of the request and appears in the user interface to which the HTTP request is sent.

    • NOTE: You can substitute this field with any Run Book Variables. For more information on Run Book Variables, see Run Book Variables.

  • command_label. This optional parameter is used to label the response to the HTTP request in the Event Actions Log. If you leave this parameter empty, the response to a request will be labeled with the URL that was used to make the request.

  1. Click Save As.