All ideas

New Portal layout is blocked inside the Intercom Messenger app

What happened? The official Sleekplan app cannot load inside Intercom Messenger Home when the Sleekplan portal layout is set to New Portal. Intercom displays: “embed-627633497.sleekplan.app refused to connect.” The same integration works when the portal layout is changed to Flat or Boxed. Where in Sleekplan did it happen? Area: Public Portal & Widget → Portal → Layout Platform: Web Browser or device: Google Chrome on macOS Integration: Official Sleekplan app for Intercom Messenger Home How can we reproduce it? Connect the official Sleekplan integration to Intercom. Set the Sleekplan portal layout to New Portal. Add the Sleekplan Feedback section to Intercom Messenger Home. Open the section in the Intercom Messenger preview. Observe the “refused to connect” error. Change the Sleekplan portal layout to Flat or Boxed and reload the preview. Observe that the embedded Feedback section now loads successfully. What did you expect to happen? The New Portal layout should load inside the official Intercom Messenger app in the same way as the Flat and Boxed layouts. What happened instead? When New Portal is enabled, the embed response includes: X-Frame-Options: SAMEORIGIN This prevents Intercom from displaying the Sleekplan page inside its cross-origin iframe. After changing the layout to Flat, the same embed URL no longer returns X-Frame-Options and loads successfully inside Intercom. Anything else that may help? Reinstalling the Sleekplan Intercom integration did not resolve the problem. Confirmed workaround: use the Flat or Boxed portal layout. The response also appears to use different runtimes: New Portal: nginx/Nuxt response with X-Frame-Options: SAMEORIGIN Flat: SleekplanApp response without X-Frame-Options Tested on 24 July 2026.