Ninox

### App
Ninox

### Summary:
o support for Ninox Private Cloud custom base URL

### Details:
Hi Pipedream team,

I'm trying to connect the Ninox integration to my Ninox Private Cloud instance, which runs under a custom domain (reinhardt.ninoxdb.de) instead of the public api.ninox.com.

The "Update connection to Ninox" dialog only has a single "api_key" field, with no option to specify a custom base URL or subdomain. My Private Cloud API key is therefore rejected, since requests appear to always go to api.ninox.com.

Could you tell me:
1. Is there currently a way to point the Ninox integration at a custom Private Cloud base URL?
2. If not, is this something you could add, or is there a recommended workaround (e.g. a generic HTTP request step) for authenticating against a Ninox Private Cloud instance?

Thanks in advance for your help.

Best regards,
Michael Fuchs
Reinhardt GmbH

### Screenshots:
No screenshots included

Start by locating the Ninox integration and its “Update connection to Ninox” dialog, then trace how the api_key is defined and where requests use api.ninox.com. Done means a Ninox Private Cloud custom base URL can be configured and requests use it without breaking the public API path.

Written by the indexing model from the issue text.