Forum Discussion
Hi @geliason,
@akidave’s suggestions will likely better suit your use cases, but here’s another option (with limitations):
When you create a triggered task to expose an endpoint for inbound calls, it provides both external and in-network endpoint URLs. You can provide the “Cloud URL” to the cloud partners without exposing your groundplex outside the network or having to manage an external load balancer. With that said, the Cloud URL has its limitations, so you will want to read the Support & Limitations section of the documentation before settling on this option.
For us: we do use the triggered-task Cloud URL capability for transactional activity with small payloads. However, we typically build pipelines to use the partner APIs to pull or push data on schedule or demand. We’ve also had cases where we used ours or our partner’s sFTP servers.