Create a Widget
Provision the Web Messenger in the dashboard — the three creation paths, plan & role requirements, and the shared secret
A Web Messenger is a WebIntegration record on your organisation, separate from your messaging channels. Creating one gives you a publicKey (embed identity) and a sharedSecret (server-to-server auth). One widget per organisation in v1.
Requirements
| Requirement | Detail |
|---|---|
| Plan | Standard tier or higher. On lower tiers the Connect button shows an upgrade tooltip and the web pages show an upgrade card. |
| Role | Creating/deleting the integration and editing widget settings needs Admin / Owner. Editors can manage content (help articles, news) but don't provision the widget. Agents are view-only. |
| Limit | One Web Messenger per organisation. |
Three ways to create one
A. From the integrations page (recommended)
- Go to Settings → Integrations.
- Find the Web Messenger card and click Connect.
- In the Create Web Messenger modal, enter a Name (1–100 chars, internal label only) and click Create.
- The modal switches to a "Save your secret" step and reveals the shared secret one time. Click Copy and store it safely. The public key is different and always visible later, so you don't need to copy it here.
- Click Done. You're routed to the Brand editor (
/{org}/web/brand).
The shared secret is shown only once. If you lose it, you must rotate it — which reveals a new value and invalidates the old one.
B. Auto-provisioned from a content page
If a Standard+ admin opens Help (/{org}/web/help) or Articles (/{org}/web/articles) and no widget exists yet, Wexio creates a default widget automatically (named "Gaia"). Help and news content is scoped to a widget, so the widget has to exist first.
The shared secret is not revealed on this path — rotate it from the Install area if you need it. The Brand editor does not auto-provision; opening it with no widget shows a setup prompt instead.
C. From the inbox empty state
The inbox "Connect a messaging channel" screen has a Web Messenger card whose Connect opens the same modal as path A.
Public key vs shared secret
| Public key | Shared secret | |
|---|---|---|
| Example | pk_live_… | a long random string |
| Where it goes | Client-side HTML (every embed snippet) | Server-side only |
| Visibility | Always visible in the dashboard | Shown once at creation or rotation |
| Used for | Identifying which widget to load | Signing visitor-identity proofs server-to-server |
Never put the shared secret in a page. See Authentication for how it's used.
Manage, pause, or delete
From the Settings → Integrations card:
| Action | Effect |
|---|---|
| Edit | Opens the Brand editor. |
| Pause / Resume | Toggles disabled. While paused the widget stops serving — embeds load nothing. |
| Disconnect | Confirmation modal, then deletes the widget and its scoped content (help articles, news). Destructive and not reversible. |
After creation
You have a widget with defaults applied. Continue to: