> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use a flow in a website widget

> Publish a flow, assign it to an assistant, and install that assistant’s current widget.

Use a published flow as an assistant's conversation path, then connect that assistant to a website widget. This keeps the flow, assistant, and widget in the same subaccount.

## Before you start

Test the flow and publish it. You need an assistant in the same subaccount and access to the website's embed settings. For browser voice, the assistant also needs a published voice agent and the page must use HTTPS.

## Connect the pieces

1. Open the assistant's model selector and choose the published flow.
2. Publish the assistant after reviewing its voice and channel settings.
3. Open **Widgets**, create or edit **Chat widget** or **Chat widget V2** (when enabled for your account), and select that assistant.
4. Save the widget. For **Chat widget**, copy its generated script from **Get Code**. For **Chat widget V2**, open **Install** and copy **Embed snippet**.
5. Paste the generated snippet into your website where its platform accepts custom code, normally before the closing `</body>` tag.

Use the current snippet generated for your widget, including its assigned assistant or widget identifier.

## Check the installed result

Open the published website in a fresh browser session. Send a message that should take a distinctive flow branch and confirm the expected next step. If the flow runs a tool, verify the external result separately.

For voice, check microphone permission and the voice-enabled assistant requirements in the [Voice Enabled Chat Widget guide](/v3/voice-enabled-chat-widget). A successful text conversation does not verify browser audio.

## Troubleshooting

* **Widget responds with an old conversation path:** publish the latest flow and verify the widget's assigned assistant.
* **No published flow appears in the selector:** publish it and confirm both resources belong to the same subaccount.
* **Widget is missing:** check the generated snippet, your site's script policy, and the browser console for blocked resources.
* **Works on one page only:** confirm the site includes the snippet on every intended page and test navigation on the actual site.

See [flow testing](/v3/guides/flows/test) before exposing a new path to visitors.

## Widget and flow options

| Choice | Configuration and constraints |
| - | - |
| Chat widget | Text chat; install using **Get Code**. Its script contains embedded settings, so replace the installed script when changing those settings. |
| Chat widget V2 | Available only when enabled for the account. Configure text chat and optional **Voice calling**, save, then copy **Install → Embed snippet**. |
| Assistant | Select the assistant assigned to your published flow, in the same subaccount. |
| Voice calling | V2 only for this chat-widget workflow. Requires an assigned voice agent, HTTPS, microphone access, and a compatible standard voice; GPT Live voices cannot use a connected flow. |
| Greeting and appearance | Configure in the widget editor. These are separate from flow node instructions and assistant call settings. |
| Flow changes | Save, test, and publish the flow. Verify the widget still selects the intended assistant. |

For every appearance, behavior, office-hours, and installation control, use the [Chat widget V2 reference](/v3/guides/widgets/chat-widget-v2) or the [text-widget installation guide](/v3/guides/widgets/install-chat) for the earlier type.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.