Admin Dashboard: Widgets

The Widgets page configures a web client for a chat-enabled schema. Widgets are not stored server-side: every embed carries its schema name and appearance settings in data-* attributes.

Prerequisites

Enable Accept chat requests on a schema. The page lists only chat-enabled schemas.

Generate the appearance settings

Open Widgets and choose a schema.
Set title, color, position, size, welcome message, and placeholder.
Copy the generated script attributes.

The Admin-generated snippet deliberately contains no credential. It is the appearance half of an embed and cannot call the protected chat endpoint by itself.

Create a working embed

Use the get_embed_snippet management MCP tool. It accepts the schema name, issues a chat-scoped key, and returns a complete snippet containing the credential and widget URL. Transfer the appearance attributes from Admin onto that snippet.

<script
  src="https://YOUR_SYNTHETICBREW_ORIGIN/widget.js"
  data-schema="support"
  data-api-key="bb_REDACTED"
  data-position="bottom-right">
</script>

The expected result is a widget that loads, starts a schema chat, and renders structured interruptions and errors safely. SYNTHETICBREW_PUBLIC_BASE_URL must identify the visitor-reachable origin in Enterprise so generated URLs are absolute and correct.

Credential caution

Anything embedded in a public page is readable by its visitors. Treat the chat key as a deliberately public, least-privilege credential: grant only Chat scope, isolate the schema, monitor usage, restrict allowed widget origins, and revoke/rotate the key if the page is retired.

Troubleshooting

A visible widget with 401 chat failures usually has no key or the wrong scope.
A 404 for widget.js indicates the configured origin or deployment artifact is wrong.
If no schemas appear, enable chat on the intended schema.