Konverso agents call external APIs for tool integrations, but the cloud infra they run on rotates egress IPs. Route those outbound calls through two fixed EU IPs with one env var, keeping the whole pipeline EU-sovereign.
# Konverso agent integration env var
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
import requests
r = requests.get(
"https://api.partner.eu/data",
headers={"Authorization": "Bearer .."}
)
Konverso is European and built on Scaleway, but when its agents call external APIs, the cloud infra's rotating egress breaks IP-based trust.
Konverso agents integrate with external tools and APIs that often enforce IP allowlisting. The cloud infrastructure they run on assigns dynamic egress IPs, so a call that passed a whitelist at noon can be blocked by midnight.
Konverso offers European data residency for the platform itself, but when agents call a third-party API, the outbound leg depends on the cloud infrastructure's egress. If that egress rotates or leaves the EU, the residency promise doesn't cover the full path.
Konverso's strength is no-code: you build agents without writing infrastructure code. That means you also can't set up VPC connectors, Cloud NAT, or routing tables to pin an outbound IP. You need an application-level solution.
A typical Konverso agent connects to multiple tools: CRMs, ticketing systems, knowledge bases, and partner APIs. Each call rides a different rotating IP, so there's no single, predictable address to whitelist or audit.
"Your Konverso agent called us from an IP we've never seen. It's blocked."
You need a fixed address your partners can trust, not a rotating cloud pool they have to chase.
Konverso agent
HTTPS Proxy
(Static EU IP)
Partner API
Every outbound call your Konverso agents make for tool integrations, API lookups, or data syncs leaves from the same pair of EU addresses. Two IPs with automatic failover, no VPC networking to configure.
requests or fetch, setting HTTPS_PROXY is all it takes.
Building Konverso agents that integrate with external APIs behind IP allowlists, who need a fixed outbound address without writing infrastructure code.
Using Konverso for EU-regulated data workloads who need agent outbound calls to stay within European infrastructure, end to end.
Connecting Konverso agents to partner platforms (CRMs, SaaS APIs) that enforce strict IP allowlisting and need one predictable address.
Accountable for where their Konverso agents send data, who want a documented EU egress rather than rotating cloud IPs.
Set HTTPS_PROXY in your Konverso agent's integration environment. Outbound HTTPS calls from tool functions then leave through your fixed EU IP.
If your Konverso agent's tool integration uses Python requests, setting HTTPS_PROXY is all you need.
# env var in your Konverso integration environment
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
PARTNER_API_TOKEN=your_token
import os
import requests
# requests honours HTTPS_PROXY from the environment
r = requests.get(
"https://api.partner.eu/data",
headers={"Authorization": f"Bearer {os.environ['PARTNER_API_TOKEN']}"},
)
print(r.status_code) # 200, from your fixed EU IP
In Node, pass the proxy explicitly with https-proxy-agent.
// env var set in your integration environment
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
const { HttpsProxyAgent } = require('https-proxy-agent');
const agent = new HttpsProxyAgent(process.env.HTTPS_PROXY);
// Every request leaves through your fixed EU IP
const res = await fetch('https://api.partner.eu/data', {
headers: { 'Authorization': 'Bearer ..' },
agent,
});Two IPs, no infrastructure to manage
Your account comes with two static IP addresses (for example 51.xx.xx.10 and 51.xx.xx.11). Whitelist both on your partner API. If one proxy node is briefly unavailable, traffic shifts to the other. No VPC, no Cloud NAT to babysit.
📖 Want the longer version? Worked examples, error handling, and other languages are in the Python SSL Proxy Guide, Node.js Guide, and the rest of the docs.
Konverso keeps your data in Europe. OutboundGateway keeps the outbound leg in Europe too.
The proxy runs in EU data centres, so your Konverso agents' outbound tool calls leave from European infrastructure, matching Konverso's own EU data residency commitment.
Because TLS passes straight through, the proxy never decodes your agents' API tokens, tool payloads, or conversation data. It forwards encrypted bytes; it doesn't read them.
Agent tool-call traffic doesn't bounce through US infrastructure on its way to a partner API, keeping the full data path inside the EU.
When a reviewer asks where your Konverso agents call from, the answer is two fixed EU addresses, not a list of rotating cloud IPs.
Two addresses to register, with automatic failover. No rotating cloud pool to chase.
One env var in your integration code. No VPC, no Cloud NAT, no routing tables. Works inside the no-code platform's runtime.
Konverso keeps data in the EU; OutboundGateway keeps the outbound leg in the EU too. Full data-path sovereignty.
CRMs, ticketing, knowledge bases, partner APIs: anything over HTTPS goes through the same pair.
TLS passthrough means the proxy can't read your traffic. Tokens, payloads, and conversation data stay private.
Starting from €29/month. Flexible plans for every scale. Cancel anytime.
Stop letting dynamic cloud egress break your agents' tool calls, and complete the EU sovereignty circle. Put your agents' outbound traffic behind one stable, GDPR-conscious EU address.
€29/month starter plan • 7-day refund policy • Direct founder support
Konverso is a no-code platform that runs on cloud infrastructure (Scaleway), so the egress IP your agents use for tool calls depends on the cloud infra's dynamic pool. Konverso doesn't expose a native static-IP setting for outbound calls. OutboundGateway fills that gap: one HTTPS_PROXY env var gives your agent integrations a fixed pair of EU IPs.
Set HTTPS_PROXY as an environment variable in the integration runtime where your agent's tool code executes. If your tool functions use requests (Python) or fetch with https-proxy-agent (Node.js), the library picks it up automatically. No VPC or networking-layer configuration needed.
Yes. Konverso offers European data residency for the platform itself, but when agents call external APIs, the outbound leg depends on the cloud infra's egress. OutboundGateway routes those calls through EU data centres owned by an EU company, so the full data path, from Konverso to the partner API, stays within EU jurisdiction.
Happy to talk through how a two-IP EU egress fits your Konverso agent setup, whether it's a CRM integration, a knowledge base lookup, or a partner API call.
Contact Our Founders →