I’d like to use the Webhook integration in Monitoring Views to hit a Webhook in Foundry, and I’m struggling to configure the appropriate egress (ingress?) policies to allow this. The endpoint would be one-direction (only from the monitoring view to the webhook, users should not be able to call it) and would not need to be accessible from outside of the Foundry environment. What would the network policy, source, and webhook need to look like in order to allow this internal(ish) integration?
You would want to configure a source that would be your foundry instance (i.e. .palantirfoundry.com). You would then want to allow egress to this domain on port 443. Your webhook would then be built on this data connection source.
This solved it, my issue ended up being not with the egress policy but with the endpoint I was configuring in the webhook. I had in my head that webhooks were similar to AWS’s API Gateway, but they don’t actually create endpoints, they just allow you to call existing endpoints. Once I updated my webhook to point to one of the public APIs, in this case the Apply Action endpoint, it worked correctly
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.