Private Statuspage Intercom Integration? | Community
Skip to main content
Answered

Private Statuspage Intercom Integration?

  • April 23, 2026
  • 3 replies
  • 88 views

Julie Edwards

We just signed up for statuspage and would like to keep our statuspage private and only expose it to users in the messenger. It looks like the integration only supports public pages. Does anyone know of a workaround? 

Best answer by Roy

Hello ​@Julie Edwards 👋 , 

 

To be straight with you, this is actually a limitation on the Statuspage side rather than Intercom. The native integration is designed for "Public" pages; once you toggle a page to "Private" or "Audience-Specific" in Atlassian, it requires a different level of authentication that the standard Messenger app doesn't currently support.

 

Regarding a few workarounds to get this sorted:

  • Custom Messenger App: You could build app using the Intercom Canvas Kit. This would allow your backend to fetch data via the Statuspage API (using your API key) and display it securely in the Messenger.
     

  • Fin AI Agent via Data Connectors: You can sync your system status to Fin. If a service goes down, Fin can digest that information and inform your logged-in customers directly during a conversation.
     

  • Restricted Access: It’s worth checking with Statuspage support if they can keep the UI "Private" while keeping the API "Active." However, usually, the native Intercom app needs that public endpoint to "see" the data.
     

A quick correction for you: Usually, just closing the page to visitors won't fix the native integration if the API also becomes restricted. The Custom Messenger App is your best bet for a truly "Private" setup that still works in the Messenger.

 

Don't hesitate to shout if you have more questions—I'm more than happy to help you find a proper solution to this.

 

Have a Londonful day ahead! 💂

 

Cheers,

Roy 🇬🇧

3 replies

Roy
Top Expert ✨
Forum|alt.badge.img+7
  • Top Expert ✨
  • Answer
  • April 26, 2026

Hello ​@Julie Edwards 👋 , 

 

To be straight with you, this is actually a limitation on the Statuspage side rather than Intercom. The native integration is designed for "Public" pages; once you toggle a page to "Private" or "Audience-Specific" in Atlassian, it requires a different level of authentication that the standard Messenger app doesn't currently support.

 

Regarding a few workarounds to get this sorted:

  • Custom Messenger App: You could build app using the Intercom Canvas Kit. This would allow your backend to fetch data via the Statuspage API (using your API key) and display it securely in the Messenger.
     

  • Fin AI Agent via Data Connectors: You can sync your system status to Fin. If a service goes down, Fin can digest that information and inform your logged-in customers directly during a conversation.
     

  • Restricted Access: It’s worth checking with Statuspage support if they can keep the UI "Private" while keeping the API "Active." However, usually, the native Intercom app needs that public endpoint to "see" the data.
     

A quick correction for you: Usually, just closing the page to visitors won't fix the native integration if the API also becomes restricted. The Custom Messenger App is your best bet for a truly "Private" setup that still works in the Messenger.

 

Don't hesitate to shout if you have more questions—I'm more than happy to help you find a proper solution to this.

 

Have a Londonful day ahead! 💂

 

Cheers,

Roy 🇬🇧


Julie Edwards
  • Author
  • New Participant
  • April 27, 2026

Thanks for the guidance, Rory! Appreciate it! 


  • New Participant
  • April 27, 2026

You’re right Statuspage integrations are mainly designed for public pages, so there isn’t a built-in way to keep it fully private just within the messenger. A common workaround is to restrict access using authentication or share updates directly through your app or Intercom messages instead of linking the page publicly.