Available starting with FlowX.AI 5.6.0
Overview
Proxy connections let you route data source traffic through an intermediary proxy server. Instead of configuring proxy settings on each data source individually, you create reusable proxy connection resources in Integration Designer and attach them to one or more data sources. This is useful in environments where outbound traffic must pass through a corporate proxy, or when you need to route API calls through a specific gateway for security or compliance reasons.Key features
HTTP and HTTPS
Support for both HTTP and HTTPS proxy protocols
Basic authentication
Optional user and password authentication for proxy servers that require credentials
Test connectivity
Validate proxy configuration before saving with the built-in test function
Reusable across data sources
Create a proxy once and attach it to multiple RESTful System data sources
Managing proxy connections
Proxy connections are managed from the Proxy Connections section in Integration Designer. To access the proxy list:- Open FlowX Designer and navigate to your project.
- In the left sidebar, expand Integrations.
- Click Proxy Connections.
| Column | Description |
|---|---|
| Name | The proxy connection name |
| Description | Optional description of the proxy’s purpose |
| Type | HTTP or HTTPS |
| Edited by | User who last modified the proxy |
| Edited at | Date and time of last modification |
Adding a proxy connection
Open the proxy creation form
From the Proxy Connections list, click the + button at the top of the page.
Configure basic information
| Field | Required | Description |
|---|---|---|
| Name | Yes | A unique name for the proxy connection |
| Description | No | Purpose or context for this proxy |
| Proxy Type | Yes | Select HTTP or HTTPS |
| Proxy Host | Yes | The proxy server hostname or IP address. Supports ${param} for configuration parameters. |
| Proxy Port | Yes | The proxy server port number. Supports ${param} for configuration parameters. |
Set auth type
Select an Auth Type from the dropdown:
- NO_AUTH
- BASIC
No authentication required. The proxy accepts connections without credentials.
Test the proxy connection
Click Test Connection to validate the configuration. The system attempts to connect through the proxy and reports success or failure.
If the test succeeds, the proxy is ready to use. If it fails, verify the host, port, and credentials.
Using proxies with data sources
Proxy connections can be attached to RESTful System data sources. When a proxy is attached, all API calls made through that data source are routed through the proxy server.Attaching a proxy to a data source
Open a RESTful System data source
Navigate to the data source configuration in Integration Designer. This works for both new and existing RESTful System data sources.
Select a proxy connection
Choose a proxy from the Select Proxy Connection dropdown. The list shows all available proxy connections in the current project.If no proxies exist, the dropdown shows a Create option that takes you to the proxy creation form.
Example: route a CRM integration through a corporate proxy
In this scenario, your organization requires all outbound API traffic to pass through a corporate proxy server before reaching external services. You have a RESTful System data source that connects to a CRM API and need to route its traffic through the proxy.Create the proxy connection
Go to Integrations → Proxy Connections and click +. Configure:
Click Test Connection to verify, then click Create.
| Field | Value |
|---|---|
| Name | Corporate Proxy |
| Description | Routes traffic through the corporate proxy gateway |
| Proxy Type | HTTPS |
| Proxy Host | proxy.corp.example.com |
| Proxy Port | 8443 |
| Auth Type | BASIC |
| User | svc-flowx |
| Password | •••••••• |
Attach the proxy to a data source
Go to Integrations → Data Sources and open your CRM data source (RESTful System type).Toggle Connect through Proxy to ON and select Corporate Proxy from the dropdown. Save the data source.
Proxy in cURL commands
When a proxy is active on a RESTful System data source, the cURL command preview in the runtime console reflects the proxy configuration. Without proxy:Configuration reference
| Property | Type | Required | Description |
|---|---|---|---|
| Name | string | Yes | Unique name for the proxy connection |
| Description | string | No | Optional description |
| Proxy Type | HTTP | HTTPS | Yes | The proxy protocol |
| Proxy Host | string | Yes | Proxy server hostname or IP. Supports ${param} syntax. |
| Proxy Port | number | Yes | Proxy server port. Supports ${param} syntax. |
| Auth Type | NO_AUTH | BASIC | Yes | Authentication method |
| User | string | When Basic | Proxy auth user |
| Password | string | When Basic | Proxy auth password |
Limitations
The following proxy types and authentication methods are not supported in this release:| Not supported | Notes |
|---|---|
| SOCKS4 / SOCKS5 | Only HTTP and HTTPS proxy types are available |
| PAC URL | Proxy auto-configuration URLs are not supported |
| Client credentials auth | Only No Auth and Basic Authentication are available |
| mTLS | Mutual TLS authentication for proxy servers is not supported |
| MCP Server data sources | MCP connections use their own inline proxy configuration |