QuotaGuard and Zoho Deluge Integration Guide

Two ways to use this guide: Setting up the integration yourself? Follow the setup steps below. Working with an AI coding agent? Share this page and use the instructions below to help it configure the integration, verify the connection and troubleshoot issues.

To let your agent set up and test the connection, provide the required proxy connection details through its secure credential mechanism rather than sharing your QuotaGuard account password. Review any changes it proposes.

QuotaGuard Static IPs let your Zoho applications reach APIs and services that require IP allowlisting. This guide covers Deluge scripts across the Zoho suite (CRM, Creator, Flow, and the rest of Zoho One) and explains the one extra piece Zoho needs compared to other platforms.

Why Zoho Requests Get Blocked

Deluge scripts run inside Zoho’s cloud, and their outbound invokeUrl calls originate from Zoho’s shared infrastructure rather than from IP addresses you control. When the API you’re calling restricts access by source IP, those requests are rejected:

  • 403 Forbidden from corporate firewalls and WAFs
  • Access denied from banking APIs and payment gateways
  • Blocked requests from any partner that maintains an IP allowlist

Your code and API keys are fine. The target service is blocking requests because they arrive from IPs it doesn’t recognize.

The Zoho Constraint

On most platforms, you point your HTTP client at the QuotaGuard proxy and you’re done. Zoho doesn’t give you that option:

  • Deluge’s invokeUrl has no proxy setting.
  • Zoho’s managed environment can’t run our QGTunnel helper, which needs a long-running process alongside your app.

So Deluge cannot send traffic through QuotaGuard directly. The working pattern is a small relay function that you host outside Zoho.

The Relay Pattern

Deluge invokeUrl --> your relay function --> QuotaGuard proxy --> target API

Your Deluge script calls the relay’s URL, passing the real target URL in a header. The relay forwards the request through QuotaGuard, so the target API sees one of your two static IPs. The response comes back to Deluge as the invokeUrl result.

We publish a ready-to-use relay for AWS Lambda, including setup steps and a Deluge invokeUrl example:

python/lambda-relay in quotaguard/static-examples

It’s a single Python file you paste into a Lambda function in the AWS console. It uses only libraries already present in the Lambda runtime, so there is nothing to package, and it’s protected by a secret key that you set as an environment variable. The same pattern can be implemented in a Google Cloud Function if you prefer GCP; adapt the Lambda-specific event and response handling to that platform.

Setup summary (details in the example’s README):

  1. Sign up for QuotaGuard and find your proxy connection details and both assigned IPs in the dashboard.
  2. Create the Lambda, paste in the code, and set the QUOTAGUARDSTATIC_URL and RELAY_KEY environment variables.
  3. Give the Lambda a Function URL with auth type NONE; the relay’s RELAY_KEY check protects it. Call it from Deluge with X-Relay-Key and X-Target-URL headers. Use the existing Deluge invokeUrl example.
  4. Add both static IPs to the target API’s allowlist. Both are active simultaneously, so allowlist both.

Choosing regions: create the Lambda in the AWS region closest to you, and pick the matching QuotaGuard region when you sign up. Your two static IPs stay the same regardless of how much traffic you send.

QuotaGuard Static or QuotaGuard Shield

Use the Static relay linked above, or deploy the Shield relay for TLS between the relay and the proxy:

Relay setting QuotaGuard Static QuotaGuard Shield
Environment variable QUOTAGUARDSTATIC_URL QUOTAGUARDSHIELD_URL
Proxy URL from your dashboard http://username:password@<host>:9293 https://username:password@<host>:9294
Relay-to-proxy connection HTTP TLS-encrypted HTTPS

Deploy the matching relay code: the Static example constructs an http:// proxy URL, while the Shield example preserves the URL’s scheme. Changing only the port or environment variable does not convert the Static relay to TLS. Deluge still calls the relay’s HTTPS Function URL with the same X-Relay-Key and X-Target-URL headers.

For an HTTPS target, both products tunnel the relay-to-target TLS session without decrypting it at the proxy; Shield additionally encrypts the relay-to-proxy connection, including proxy credentials. Use an https:// target URL to protect the proxy-to-target connection too.

The shared Static IP with no HTTP proxy guide explains the relay pattern for other platforms.

What This Covers (and What It Can’t)

The published relays handle HTTP(S) calls from Deluge or other custom code where you control the URL being invoked. They return the response as UTF-8 text; binary downloads need different response handling. Both forward the method, body, Content-Type, and Authorization headers. The Shield relay also forwards Accept and headers prefixed with X-Fwd-: for example, X-Fwd-X-Api-Key: abc reaches the target as X-Api-Key: abc.

It cannot change where Zoho’s built-in integrations connect from. If a Zoho app talks to an external service through a native connector rather than your Deluge code, that traffic goes out from Zoho directly and can’t be routed through QuotaGuard. Check which of your IP-restricted connections run through Deluge before planning the allowlist.

Testing

Point X-Target-URL at https://ip.quotaguard.com. It returns the IP your request came from, which should be one of the two static IPs shown in your dashboard. A match to either assigned IP is valid; observing both addresses is not required. Allowlist both assigned IPs at the destination. Once that checks out, switch the target to the real API.

Troubleshooting

Add detailed: true to invokeUrl to inspect the returned HTTP status, headers, and body.

  • Relay returns 403 with Forbidden: check that X-Relay-Key matches the function’s RELAY_KEY. Target APIs can also return 403, so check which service rejected the request.
  • Relay returns 400 with Missing X-Target-URL header: supply X-Target-URL with the full target URL, including https://.
  • Function logs a KeyError: set the environment variable named in the error. The matching proxy URL variable is required at startup, and RELAY_KEY is required when handling a request.
  • Call times out: the relay READMEs set the Lambda timeout to 30 seconds instead of the 3-second default. Zoho documents a 40-second invokeUrl response limit, so increasing Lambda’s timeout alone does not extend Deluge’s wait.

If you run into anything odd during setup, contact support and include the error you’re seeing.


Ready to Get Started?

Get in touch or create a free trial account

Back to top ↑

Copyright © 2009 - 2026 QuotaGuard. All rights reserved.