Embed
Learn how to share a published agent's dedicated chat page as a public link, so anyone can talk to it without signing in.
Embedding makes an agent you built in the Agent Builder publicly available outside Flux. When you turn embedding on, the agent gets a dedicated chat page address (a public link) that anyone can open without signing in. Insert that address into an external site with an iframe, share it as a link, or open it in a new tab, and visitors can chat with the agent right away, without a Flux account.
Use it to ship agents that are safe to expose publicly — support bots, product guides, internal wiki helpers, and the like.
Embedding can only be turned on for a published agent. For an agent to be reachable externally, two conditions must both be true — the agent is published, and embedding is enabled. If either one is missing, the embed address returns a not-found page.
What embedding is
An embedded agent runs as a standalone chat page hosted by Flux. The page contains only the chat UI — no admin sidebar or header — so it drops cleanly into an external site. Conversations on the embed page are stored as anonymous records, so you can review usage and quality later.
Publish once
Publishing the agent and turning embedding on is all it takes to ship. No separate server or custom code required.
iframe or a link
Insert the embed address into an external site with an iframe to show it as a chat widget, or copy the address and share it as an email, message, or button link, or open it in a new tab.
Continue conversations
Each visitor's history is kept in their browser, so returning on the same device picks up where they left off.
No login needed
Visitors chat without a Flux account. You control who can see what through the agent's public scope.
Setting up embedding
Embedding is configured from the top of the Agent Builder. The 'Embed' button only appears once the agent is published, so publish the agent first.
Publish the agent
Use the Publish button at the top right of the builder to switch the agent to published. Only then does the 'Embed' button appear.
Open embed settings
Click the 'Embed' button in the header to open the embed settings dialog.
Enable embedding
Turn on the 'Enable embed' switch. While this switch is off, the address cannot be reached from outside even if it exists.
Enter a URL slug
Choose the slug used in the agent's address. Only lowercase letters, numbers, and hyphens are allowed, and a slug is required to turn embedding on.
Add a description and save
Optionally write a short description shown to visitors (up to 500 characters) and save. Saving creates the embed address, which you can copy or open in a new tab right away.
The slug becomes part of the embed address, so use something recognizable like 'support' or 'product-helper'. Changing the slug later breaks the old address, so settle on it before sharing externally.
Deploying to your site
After you save, the embed address takes this shape — your-site/chat/embed/org-slug/agent-slug. You can deploy it two ways — embed it directly in an external site with an iframe to show it as a chat widget, or share the address as a link or open it in a new tab.
| Method | Description |
|---|---|
Address shape | Your site address, followed by /chat/embed/ and then the organization slug and the agent slug. |
Share as a link | Send the address as an email, message, or button link to open the full-page chat. |
Open in a new tab | Use the copy or open-in-new-tab buttons in the embed settings dialog to grab the address, then add a link pointing to it on your internal portal. |
Embed with an iframe | Put the embed address in an iframe |
The embed page can be inserted directly into an external site with an iframe. Put the embed address in the iframe src — for example: <iframe src="your-site/chat/embed/org-slug/agent-slug" width="400" height="600" style="border:0"></iframe>. A published, embed-enabled agent can be framed by any external site, so only enable embedding for agents that are safe to expose publicly.
Access and security
Embedding is an anonymous public channel, so it's important to understand what gets exposed. An embedded agent does not draw on everything in your organization — only documents marked as available to everyone.
Embedded chat searches public document groups only. Document groups tied to a specific team are automatically excluded from embedded conversations, so internal-only material is not exposed to outside visitors. Keep anything that should stay private in team-only groups.
Embedded chat applies request limits to prevent abuse. A visitor who sends messages too quickly in a row is briefly blocked and works again after a short wait. Also, if the organization is suspended, the embed address stops responding.
Operating and managing
Even after embedding is on, you can turn it off or unpublish at any time, and embedded conversation records are cleaned up automatically after a period of inactivity.
Turning off the 'Enable embed' switch or unpublishing the agent immediately changes the embed address to a not-found page. Links you already shared will no longer open.
Conversations are kept in the visitor's browser so they can continue on the same device, and are also stored as anonymous records that let operators review usage and quality. Visitors can clear their own history with 'Delete all conversations' on the embed screen.
Yes. Embedded conversations that go inactive for a period are cleaned up automatically, so old records don't pile up and operators don't have to manage them by hand.
The embedded chat screen does not offer file attachments. Embedding is built around text conversations.
Yes. Turn embedding on per agent and give each one its own slug, and you can publish multiple agents at different addresses at the same time.