> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Execution of Http Request

> GermainUX can execute HTTP or HTTPS requests manually, on a schedule, or through an automated trigger.

Components
[`Engine`](/main/germain-ux-engine)

Availability
2014.1 or later

GermainUX can execute HTTP or HTTPS requests manually, on a schedule, or through an automated trigger.

> **[Configure an HTTP Action](#configure-an-http-action)**
>
> Single request to an endpoint

> **[Configure an HTTP Scenario](#configure-an-http-scenario)**
>
> Multi-step API request workflows

> **[Configure Execution Notifications](#configure-execution-notifications)**
>
> Status alerts for requests

> **[Validate the Configuration](#validate-the-configuration)**
>
> Test before recurring runs

## Requests can be configured as:

| Type | Description |
| - | - |
| **HTTP Action** | A single HTTP or HTTPS request. |
| **HTTP Scenario** | A sequence of related requests representing an API, service, or business transaction. |

## Configure an HTTP Action

Use an HTTP Action when GermainUX needs to execute one request against an endpoint.

### Go to:

**GermainUX Workspace -> Left Menu → Settings → Wizards -> HTTP Action**

![Configure Execution of Http Request: Go to:](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-execution-of-http-request/image-20260825-052021.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=6858c5b7c7b0b6c17ee89c12f16f3a2a)

Configure the action, including:

* Action name
* URL and protocol
* HTTP method
* Headers
* Query parameters
* Request body, when applicable

> **Show all 11**
>
> * Authentication or credential reference
> * Timeout
> * Expected response or success criteria
> * Monitoring Node and Engine
> * Manual, scheduled, or event-driven execution

Save and deploy the action when the configuration is complete.

## Configure an HTTP Scenario

Use an HTTP Scenario when the workflow requires multiple requests—for example, authentication followed by one or more API transactions.

### Go to:

**GermainUX Workspace -> Left Menu → Settings -> Wizards -> HTTP Scenario**

Configure:

* The scenario name and target application.
* The Monitoring Node and Engine.
* Each HTTP or HTTPS request in its execution order.
* Authentication and credential references.
* Values that must be passed between requests.
* Response validations and failure conditions.
* Optional SLA thresholds.
* The execution schedule.

Save and deploy the scenario after testing its requests and dependencies.

## Schedule Execution

An HTTP Action or Scenario can run:

* Manually
* At a specific time
* At a recurring interval
* In response to an SLA, rule, insight, or automation condition

![Configure Execution of Http Request: Schedule Execution](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-execution-of-http-request/image-20240329-210903.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=eaac2d3bc122e8fcc26414341811a6d7)

See [Configure a Time Interval](/main/component-scheduling.md).

Select an Engine that can reach the target endpoint from the network location you want to test.

## Configure Execution Notifications

Use the following options to receive status notifications:

| Option | Behavior |
| - | - |
| **Notify on Success** | Sends a notification when the HTTP Action or Scenario completes successfully. |
| **Notify on Failure** | Sends a notification when the execution fails or does not meet its configured success criteria. |

Enable both options during initial testing. In production, enable the notifications required by your operational policies.

## Validate the Configuration

Before enabling recurring execution:

| Step | Action |
| - | - |
| 1 | Run the action or scenario manually. |
| 2 | Confirm that the selected Engine can reach the endpoint. |
| 3 | Verify authentication and credentials. |
| 4 | Review the response status, content, and duration. |
| 5 | Confirm that sensitive values are not exposed in logs or notifications. |
| 6 | Force a controlled failure and verify **Notify on Failure**. |
| 7 | Confirm that SLA evaluation and scheduling work as expected.  ![Configure Execution of Http Request: Validate the Configuration](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-execution-of-http-request/image-20260825-052147.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=3a93388e4a59bd3188007c2015e29d4b) |

## Get Help

> **[Contact GermainUX Support](/main/support.md)**
>
> The Germain Team can help you set this up.

> **Can't find what you need?**
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.