Skip to content
MinicrewMinicrew Docs

Web Embed Widget

The Web Embed widget puts your agent on your own website as a floating chat button, similar to Intercom or Crisp. A visitor clicks it, a chat window opens, and they talk to your agent right there on the site, no separate app or channel needed.

Setting it up

Section titled “Setting it up”
  1. Open the agent you want to embed, go to its Channels tab, and select Web Embed.
  2. Toggle the channel on. This generates a publishable key for your site.
  3. Customize how the widget looks and behaves: light/dark/auto theme, accent colour, header text, welcome message, where the launcher button sits on the page, and whether voice messages or file attachments are allowed.
  4. Optionally list the website addresses (origins) where you plan to use the widget.
  5. Copy the generated snippet and paste it into your website’s HTML, just before the closing </body> tag (or wherever your site management tool lets you add custom scripts).

The snippet looks like this, with your agent’s own ID and key already filled in:

<script src="https://<your-worker-address>/embed.js"
        data-agent="<your-agent-id>" data-key="pk_..." data-theme="light" async></script>

Once it’s live, visitors see a small chat launcher button that opens into a full conversation with your agent.

Things to know

Section titled “Things to know”

The key in the snippet is meant to be public. It’s designed to appear in your website’s source code, the same way analytics or chat-widget scripts from other providers do, and it doesn’t grant access to your workspace; it only identifies which agent should answer. You can regenerate or turn off the key at any time from the Web Embed section, useful if you need to cut off a copy of the widget you no longer control, say, after removing it from an old site.

The widget draws on your normal monthly token/message allowance (see Billing & Plans), so a busy day on your site won’t bypass your plan’s limits. Each visitor’s conversation is remembered across page loads on the same device, and a returning visitor picks up roughly where they left off, though the visible chat history starts fresh on every reload.