Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

Setting Up the On-Premises Proxy Integration

Step 1 - Add the Integration

  1. In Harmony, go to Settings and open the Integrations page.

  2. Locate On-Premises Proxy in the integrations list and click Add.

  3. Give the instance a descriptive name so you can identify which internal system it points to.

  4. Follow the on-screen prompts to complete the initial configuration.

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 adding the integration, you will receive the configuration details needed to set up the proxy agent on your internal host. Install the agent on a machine that has network access to your target service, then apply the provided configuration so the agent can establish its secure tunnel back to Harmony.

Step 3 - Configure the Target

When configuring an instance, specify the internal target that the proxy should forward requests to. The integration supports both HTTP and HTTPS targets. If your internal service uses HTTPS with a self-signed or internal certificate, you can enable TLS bypass to allow the proxy to connect without certificate validation.

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. In the block's connection settings, choose your on-premises proxy instance from the available integrations.

  4. Configure the request URL, method, headers, and body as you would for any HTTP request - the proxy handles routing the traffic to your internal target automatically.

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, update, or remove an instance, return to Settings and open the Integrations page, then locate the relevant On-Premises Proxy entry.

Supported Protocols

Target Type
Supported

HTTP

Yes

HTTPS

Yes

HTTPS with TLS bypass

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.

  • TLS bypass skips certificate validation for the connection between the proxy agent and the internal target. Use this only when your internal certificate chain is not resolvable by the agent host, and ensure the network path is otherwise trusted.

PreviousCisco Meraki

Last updated

Was this helpful?