Framer chat integration
Connect Framer to the same authenticated host page used by your web and mobile clients.
Embed component setup
Insert an Embed component, select HTML and paste this launcher. Set its height so the link remains visible, then publish and test the resulting page.
<!-- Framer Embed component HTML -->
<a href="https://chat.example.com/chat" target="_blank" rel="noopener">
Open your account’s chat
</a>Build the chat page
Your team hosts https://chat.example.com/chat, implements the authenticated backend ticket endpoint, then installs the module-loader example on that page. Authenticate the user there with your application’s own sign-in. Never put a server key or mint token in a platform block or URL.
Allowed origin and renewal
Save the exact HTTPS origin of your chat host page in Integrations → Allowed sites, then publish branding. Its loader calls your backend through getSession, with independently pinned verification keys. Return fresh ticket, nonce and signedConfig values for the same signed-in user, with Cache-Control: no-store. The loader owns ticket redemption and its in-memory chat session.
Before production
Test the published Framer launcher, sign-in, first turn, Stop, history, receipts, renewal and logout. If nesting your host page, allow every ancestor site origin too and test browser cookie restrictions; a top-level launcher avoids third-party sign-in dependencies. Use Getting started and Support for provisioning help.