• /
  • EnglishEspañolFrançais日本語한국어Português
  • Inicia sesiónComenzar ahora

HTTP Get

preview

We're still working on this feature, but we'd love for you to try it out!

This feature is currently provided as part of a preview program pursuant to our pre-release policies.

This page provides a comprehensive reference for HTTP Get available in the workflow automation actions catalog. These actions enable you to perform HTTP GET request operations.

Prerequisites

Before using HTTP actions in workflow automation, ensure you have:

  • Target API endpoint URLs.
  • Any required authentication credentials (API keys, tokens, etc.).
  • Understanding of the API request/response formats.

Sugerencia

HTTP actions support secret syntax for any header value, allowing you to securely pass sensitive data like API keys. See secrets manager for more information.

Automatic request headers

All HTTP requests performed by Workflow Automation automatically include the following headers:

Header

Format

x-abuse-info

Request sent by a New Relic WorkflowAutomation. {runId}
where {runId} is the workflow run ID

User-Agent

NewRelic/WorkflowAutomation (region={region}; https://newrelic.com ; support@newrelic.com)
where {region} is the New Relic region

Request web data

Perform an HTTP GET call to retrieve data from an API endpoint.

Importante

If you need to pass sensitive data to an input, for example an Api-Key header, you can use values stored via the secretsManagementCreateSecret NerdGraph mutation.

Example

{
"inputs": [
{
"key": "headers",
"value": "{\"Api-Key\": \"${{ :secrets:NR_API_KEY }}\"}"
}
]
}

Input Field

Optionality

Type

Description

url

Required

String

The target URL for the request. The scheme must be included: https://example.com. See using workflow inputs for dynamic values.

urlParams

Optional

Map

The query parameters to append to the URL. Takes a stringified JSON object.

headers

Optional

Map

The headers to add to the request. Takes a stringified JSON object.

selectors

Optional

List

The selectors to get only the specified parameters as output.

Selectors

Purpose: Extract specific data from the API response.

Structure:

  • name: The variable name to store the extracted value
  • expression: JSONPath or expression to parse the response
  • Use responseBody | fromjson to parse JSON responses
  • Chain additional filters using dot notation (e.g., .abbreviation)

Output Field

Type

Description

responseBody

String

The body of the response.

statusCode

Int

The status code of the response.

success

Boolean

Status of the request.

errorMessage

String

Failure reason as message.

Workflow definition

Input

Output

name: httpGetTest
steps:
- name: query
type: action
action: http.get
version: 1
inputs:
url: ${{ .workflowInputs.url }}
urlParams: ${{ .workflowInputs.urlParams }}
headers: ${{ .workflowInputs.headers }}
selectors: ${{ .workflowInputs.selectors }}
{
"inputs": [
{
"key": "url",
"value": "https://example.com"
},
{
"key": "urlParams",
"value": "{\"foo\": \"bar\"}"
},
{
"key": "headers",
"value": "{\"baz\": \"bat\"}"
},
{
"key": "selectors",
"value": "[{\"name\": \"responseBody\", \"expression\": \".responseBody\"}, {\"name\": \"statusCode\", \"expression\": \".statusCode\"}]"
}
]
}
Success case:
{
"responseBody": "<!doctype html>\n<html>...</html>\n",
"statusCode": 200,
"success": true
}
Failure case:
{
"errorMessage": "An unexpected error failed to call http get endpoint.",
"success": false
}
Copyright © 2025 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.