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

# Widgets and embeds

> Add a Flowra chat widget to your website, bound to a workflow.

A **widget** is a branded chat surface on an external site, tied to one workflow. Configure widgets in the dashboard, then paste the embed snippet or iframe URL on your site.

## Configure a widget

<Steps>
  <Step title="Open widgets">
    Go to [Workflow widgets](https://flowra.dev/dashboard/workflows/widgets) (also reachable from workflow actions).
  </Step>

  <Step title="Create or edit">
    Set a friendly name, which workflow answers, active flag, on-screen position, button size, colors, header text, optional quick-reply chips, whether file upload is allowed, and whether threads persist (plus retention/expiry when shown).
  </Step>

  <Step title="Copy embed details">
    After save, the UI provides embed instructions and a **widget id** for the public URL.
  </Step>
</Steps>

## Public embed URL

Pattern:

```text theme={null}
https://flowra.dev/embed/chat?widgetId=<identifier>
```

The page uses minimal chrome and loads branding and persistence settings from the widget config. Treat the widget id like a capability: do not post it publicly if the bound workflow can access private data or powerful tools.

Widget visitors appear as [external users](/product/external-users) with source **Widget**. Use the End user switcher to inspect their threads and connections.

## Security hygiene

* Use a dedicated workflow for public embeds — limit tools and knowledge.
* Prefer separate workflows for internal automations vs customer-facing chat.
* Test on a staging page before production.

## Try it

[Embed a widget](/product/try-embed).