AppFoundry marketplace — evaluating third-party integrations

General Discussion
1

When evaluating AppFoundry integrations, always verify how they handle authentication.

We evaluated a third-party WFM integration and discovered it required a ‘Client Credentials’ OAuth grant with org-wide admin permissions. From a security architecture perspective, this grants the integration unrestricted access to every user, queue, and recording in the org. We built our own integration using the Java SDK with scoped permissions instead.

// Scoped OAuth client for minimal access
ApiClient client = ApiClient.Builder.standard()
    .withAccessToken(scopedToken)
    .withBasePath("https://api.mypurecloud.com")
    .build();
2

For digital channels specifically, many AppFoundry chatbot integrations require access to the Web Messaging deployment configuration.

If you are evaluating a third-party bot vendor, ensure they support Genesys Cloud’s Open Messaging API rather than requiring direct access to your Messenger deployment. Open Messaging keeps the vendor at arm’s length from your infrastructure.