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
For prerequisites, see HTTP actions.
Automatic request headers
All HTTP requests performed by Workflow Automation automatically include the following headers:
Header | Format |
|---|---|
|
|
|
|
GET 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 | Type | Description |
|---|---|---|
url | String | Required. The target URL for the request. The scheme must be included: |
urlParams | Map | Optional. The query parameters to append to the URL. Takes a stringified JSON object. |
headers | Map | Optional. The headers to add to the request. Takes a stringified JSON object. |
selectors | List | Optional. 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 valueexpression: JSONPath or expression to parse the response- Use
responseBody | fromjsonto parse JSON responses - Chain additional filters using dot notation (e.g.,
.abbreviation)
Output | 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 |
|---|---|---|
| | |