Skip to main content
kcronin
Gainsight Employee ⭐️
Gainsight Employee ⭐️
November 5, 2025
Release

Gainsight CC: Configure Secure API Connectors in Your Customer Communities

Related products:CC IntegrationsCC Product Updates
  • November 5, 2025
  • 9 replies
  • 457 views

Enhance your community experience via secure connections to other relevant applications. 

 

Secure API Connectors are now available, letting you bring data and actions from external systems like Salesforce, Aha! Ideas, Statuspage, or your own APIs into your community frontend via a secure server-side proxy.

 

This means you can bring valuable data and functionality from other platforms straight into your community experience without ever exposing sensitive credentials.

 

Here’s What’s New

  • Call external APIs directly from your community using a secure, server-side proxy
  • Safely store API keys and tokens with encrypted, server-side secrets management
  • Create custom connectors to integrate with your own or third-party systems
  • Reference credentials securely with {{ get_secret('name') }}
  • Bring real-time data or interactions into your community through HTML widgets
Leverage the Integrations page to set up Secure APIs. 

 

Secure API Connectors are available as part of the Integrations section in Customer Communities Control.

  • For existing customers, access is tied to the same permissions used for the Integrations area.
    • If you already have access to Integrations > Connectors or Secrets, you’ll see the new Secure API Connectors functionality automatically — no additional enablement required.
  • For new customers, the Connectors area will start as an empty slate, meaning you’ll need to create your first connector to begin using it.

No additional purchase or license activation is needed if your community already includes the Integrations module.

 

Set Up in Minutes

  1. Configure Secrets
    • Go to Customer Communities Control > Integrations > Secrets
    • Click Add New Secret, give it a name, and securely store your API key or token
  2. Create a Connector
    • Navigate to Integrations > Connectors
    • Click Create New Connector > Custom Connector
    • Define your API endpoint, authentication method, and parameters
  3. Add to Your Community
    • Use an HTML Widget to connect your page to the configured API
    • Display or send data securely — all handled through the backend proxy

Shoutout to the Beta Crew!

Big thanks to the crew of beta testers who put Secure API Connectors through its paces. Your feedback helped ​@marekkoszlak ​​​​and the rest of Gainsight’s Product and Development team polish the experience for communities everywhere.

 

👉 Check out the Release Notes for more information.

💬 Have a question for our team? Drop a comment below!

 

    9 replies

    Jef Vanlaer
    Helper ⭐️⭐️⭐️
    November 5, 2025

    Would be nice to see some example html widgets that use this functionality for inspiration...

    jvdc
    Expert ⭐️
    November 5, 2025

    Ah yes ​@Jef Vanlaer I was about to ask the same! Would like some see some customer examples, and not just the weather forecast :-)

    Helper ⭐️⭐️⭐️
    November 5, 2025

    Agreed, would love examples! :) 

    DannyPancratz
    VIP ⭐️⭐️⭐️⭐️⭐️
    November 5, 2025

    Add me to the list interested in examples. 

    Specific ideas: 

    • Zapier
    • Zendesk
    FYI: I am no longer active in this community
    G-lief
    Contributor ⭐️⭐️
    November 5, 2025

    My #1 (non-internal) request - GitHub .gist file integration. (also gitHub profile details integration) Possible?

    marekkoszlak
    Gainsight Employee ⭐️
    Gainsight Employee ⭐️
    November 7, 2025

    Thanks for the interest in concrete examples! Here are a few we’ve been exploring with Secure API Connectors:

    • Salesforce Cases (per logged-in user): show the user’s open/closed cases and let them submit a new one.
    • Aha! Ideas: submit a new idea as the signed-in user and list ideas created by them.
    • Statuspage: pull incidents to display a live status badge, whole page, or incident banner.

    All of these would run through our server-side proxy with secrets stored server-side, and with personalization guaranteed by context of signed-in user injected server-side as well.

    Here’s an example of a Connector that pulls list of Salesforce Cases for a Contact identified by logged in user’s email. The Connector can be then called from the Community frontend, to create a widget UI with the returned data. The same pattern will work with any other ticketing system that exposes the right APIs and auth - configure auth attributes in secrets, define the connector, and call it from an HTML widget.

     

    Contributor ⭐️
    August 14, 2026

    Hello, following up on your Salesforce Cases example above. I've got the Connector configured and "Test Connection" succeeds, but when I call it from an HTML Widget using window.WidgetServiceSDK.connectors.execute({ permalink: ..., method: "GET" }), the call never resolves or rejects — no network request fires, no error thrown, it just hangs. Would you be willing to share the exact widget-side HTML/JS you used for the Cases example? Want to make sure I'm not missing a setup step on the widget side.

    Jef Vanlaer
    Helper ⭐️⭐️⭐️
    November 7, 2025

    Thank you for the example, ​@marekkoszlak . I’m already getting a bit of a better feel for what’s possible with this functionality.

    jvdc
    Expert ⭐️
    November 10, 2025

    Hi ​@marekkoszlak thank you!

    Would you mind sharing how you setup the Ideas list?