HTTP Request

Use an HTTP method to communicate with another application.

This node will output:

  • HTTP status code (e.g., 400)

  • HTTP response headers in JSON format

  • HTTP response body in JSON format

The HTTP request relies on variables for its operation.

Properties

Node Label — Type an informative name for the HTTP Request node. You can keep the system-provided default of "HTTP Request" if you wish.

Debug — Select Debug if you want to receive debug data when the node executes.

Debug View

When debug is enabled for an HTTP Request node, you can view detailed debug information in the Debug Runbook Flow dialog. The HTTP Request node provides a specialized Inspect tab that displays formatted, structured views of HTTP request/response data in a collapsible tree view format, with JSON data automatically formatted for readability.

The Inspect tab organizes HTTP debug data into the following sections:

  1. Error banner: When an error is reported, an error banner is displayed at the top of the tab using red/danger styling for immediate visibility.

  2. Request Section:

    • Request Overview: Displays HTTP method (GET, POST, PUT, DELETE, etc.) and full URL.

    • Request Headers: All HTTP request headers (collapsed by default).

    • Request Body: The request payload/body content (expanded by default).

  3. Response Section:

    • Response Status: HTTP status code with color-coded badge. Green (2xx), Yellow/Orange (3xx), Red (4xx/5xx).

    • Response Headers: All HTTP response headers (collapsed by default).

    • Response Body: The response payload/body content (expanded by default).

All sections, except for the error banner and request overview, can be expanded/collapsed individually. Each section is displayed only if data is available for it. Each section includes a copy button to quickly copy section content. For more information about debug views, see Runbook Debugging Features.

Authentication

Choose an existing authentication profile to communicate with a different application, or define a new one.

Endpoint

Specify the HTTP method and URI the request will use as its endpoint.

HTTP Headers

Define the HTTP headers for the request to use, including the expected media type (Content-Type Header) and content type (Accept Header). The default is application/json.

HTTP Payload

Click Include payload to define a payload to include in the request. This can use variables for referencing specific parameters.

Retry Until Ready

Define a Liquid template to query a status API until a ready response is received, along with a timeout value for stopping query retries. The number of HTTP node retries can be set as a variable.

Output

Show the parameters this node receives from the preceding node in the runbook.

Runbook Compatibility

Incident, Lifecycle, On-Demand, External (Webhook), Subflow