> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/networking/on-premises-proxy.md).

# On-Premises Proxy

The On-Premises Proxy integration lets you connect Harmony workflows to internal systems that are not publicly accessible on the internet. By routing HTTP requests through a secure tunnel, you can automate workflows that interact with on-premises services, private APIs, and internal tooling - without exposing those systems directly to the public internet.

You can set up multiple proxy instances per account, each pointing to a different internal target, so your workflows can reach any number of private services.

***

### How It Works

When a workflow contains an HTTP Request block configured to use an on-premises proxy, Harmony routes the outbound request through a lightweight proxy agent installed in your internal network. The agent forwards the request to the target service and returns the response back to the workflow - all through a secure tunnel.

This means your internal services never need to accept inbound connections from the internet. The proxy agent initiates the outbound connection, keeping your network perimeter intact.

***

### Prerequisites

Before setting up the integration, make sure you have:

* Access to the Harmony Integrations settings page with permission to add integrations
* A server or host inside your internal network where you can install and run the proxy agent
* Network access from that host to the internal target service you want to reach
* Outbound access from that host to Cloudflare on port 7844 (TCP and UDP), which the proxy agent uses for its tunnel. No inbound ports need to be opened
* Administrator rights on that host to install the proxy agent as a service

***

### Setting Up the On-Premises Proxy Integration

#### Step 1 - Add the Integration

1. In Harmony, go to **Settings** and open the **Integrations** page.
2. Find **On-Premises Proxy** under **SaaS Applications** (or search for it by name) and click its card. If an instance already exists, click **+ Create instance**.
3. Enter an **Instance name** so you can identify which internal system it points to (required).
4. Enter the **Target Address** (see Step 3) and click **Connect**.

You can repeat this process to add multiple instances - each one can point to a different internal target service.

#### Step 2 - Install and Configure the Proxy Agent

After you click **Connect**, the window stays open and shows **Installation Instructions** for the proxy agent, which is the Cloudflare tunnel connector (`cloudflared`). Run both commands on a machine that has network access to your target service:

1. **Download & install Cloudflare**: a PowerShell command that installs `cloudflared` on Windows. For other operating systems, use the **Download Cloudflare manually** link.
2. **Install the Harmony connector**: a `cloudflared service install` command that contains your instance's token. Use the copy button to copy the full command.

On Windows, run both commands in a PowerShell window opened as administrator. On Linux or macOS, run the second command with `sudo`.

The agent then establishes its secure tunnel back to Harmony.

#### Step 3 - Configure the Target

The **Target Address** is the internal service that the proxy forwards requests to. Enter it with its scheme and an optional port, for example `http://10.0.1.100:8080`. The integration supports both **HTTP** and **HTTPS** targets. For HTTPS targets, the proxy agent does not validate the target's certificate, so services with a self-signed or internal certificate work without extra configuration. The **Target Address** cannot be changed after the instance is created; to point to a different service, create a new instance.

***

### Using the Proxy in Workflow HTTP Request Blocks

Once your on-premises proxy instance is set up and the agent is running, you can use it inside any workflow that needs to communicate with that internal system.

1. Open or create a workflow in Harmony.
2. Add or select an **HTTP Request** block.
3. Select your instance in the block's **On-premises proxy** field. In the newer workflow builder, turn on **On-prem routing** and select the instance under **On-prem proxy**.
4. Enter only the path of the request (for example, `/api/v1/resource`) in the URL field. Harmony appends it to the instance's **Target Address**. Configure the method, headers, and body as you would for any HTTP request. File uploads, OAuth 2.0, AWS Signature V4, and integration authentication are not available when a request is routed through the proxy.

When the workflow runs, Harmony sends the HTTP request through the secure tunnel to the proxy agent, which forwards it to the internal service and returns the response for the next steps in your workflow.

***

### Managing Multiple Proxy Instances

Because each proxy instance is configured independently, you can maintain separate instances for different environments or systems - for example, one instance for an internal ERP system and another for a private data warehouse. Each instance appears by name in the HTTP Request block's integration selector, making it straightforward to choose the right tunnel for each workflow.

To review or remove an instance, return to **Settings** and open the **Integrations** page, then click the **On-Premises Proxy** card. Click the delete (trash) icon next to an instance to remove it.

***

### Supported Protocols

| Target Type                                      | Supported |
| ------------------------------------------------ | --------- |
| HTTP                                             | Yes       |
| HTTPS                                            | Yes       |
| HTTPS with a self-signed or internal certificate | Yes       |

***

### Considerations

* The proxy agent must be running and connected for workflows using that instance to execute successfully. If the agent is offline, HTTP Request blocks routed through it will fail.
* Each proxy instance is scoped to a single internal target. To reach multiple internal services, create a separate instance for each.
* For HTTPS targets, the proxy agent does not validate the certificate on the connection between the agent and the internal target. Make sure the network path between them is trusted.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.harmony.io/integrations/networking/on-premises-proxy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
