Public URL and Widget

SquadOS has two channels that let anyone chat with the agent without signing in: Public URL (shareable link) and Site Widget (embeddable bubble). Both appear as separate cards under Triggers because they fit different scenarios — pick the right one.

When to use	Public URL	Site Widget
Distribution	Direct link you share	Embed on your own site
Look	Full screen at squados.io/a/<slug>	Floating bubble in the page corner
SquadOS branding	Always visible	Always visible
Domains	Open to anyone with the link	Restricted by domain allowlist
Quota	No dedicated quota	Optional daily credit quota

The authenticated Hub (route /hub) is something else: it is the panel where signed-in collaborators chat with the agents of their organization. It does not require configuration in the Triggers card — every active agent already shows up there for org users.

Public URL

Creates a unique URL https://squados.io/a/<slug> that anyone can open to chat with the agent in full screen, without signing in.

Activating

1. Open the agent in the admin panel.
2. Go to Triggers.
3. On the Public URL card, click Connect.
4. Pick a Slug (3 to 64 characters, lowercase letters, numbers, and hyphens only). It is the last segment of the link.
5. SquadOS validates the slug in real time. If it is already in use, pick another.
6. Click Activate Public URL.

The URL shows up in the card once active, with a copy button. To deactivate, click Disconnect — the URL goes offline immediately.

Before sharing

• Test the agent by opening the URL yourself.
• Make sure the prompt clearly defines the support scope.
• Ensure that sensitive tools (email sending, transactions, internal data) are not exposed without guardrails.
• Monitor the first conversations under Conversations.

Site Widget

A <script> snippet you paste into your site that renders a floating chat bubble. Visitors click, talk to the agent, close — all without leaving your page.

Activating

1. Open the agent, go to Triggers.
2. On the Site Widget card, click Connect.
3. In the modal, the only required field is in the Essential section:
   • Allowed domains — the sites authorized to use the widget. Type a domain and press Enter (or Add). Use *.example.com to whitelist every subdomain. Without at least one domain the widget works nowhere.
4. The Advanced section (collapsed by default) holds optional tweaks — the defaults work for most cases:
   • Bubble position — bottom right (default) or bottom left.
   • Welcome message — first message shown when the visitor opens the widget.
   • Daily credit quota — cuts off the widget when the day’s limit is reached; visitors see “limit reached” until the next day.
5. Click Save and activate widget.

The widget slug (the identifier in the data-agent attribute) is generated automatically from the agent’s name — you neither type nor pick it. It never changes once created, so snippets already pasted on your sites stay valid.

Once the widget is active, the card turns green with Connected and three actions: Open (opens /embed in a tab), Information (reopens the configuration and the install code), and Disconnect.

Install snippet

Click Information on the card to reopen the configuration — the Install code block shows the ready-to-paste snippet:

<script async src="https://squados.io/widget.js" data-agent="your-slug"></script>

Paste it just before </body> on every page where the widget should appear. The loader takes care of the rest: paints the bubble, opens the iframe on click, and brokers messages.

The modal also offers Copy snippet and Test on /embed (opens https://squados.io/embed/<slug> in a new tab so you can see the raw chat before embedding on your site).

Domain allowlist

When the widget is loaded through the snippet, the loader checks the page’s domain against the allowlist and only paints the bubble on authorized domains. Use this to prevent other sites from embedding your widget and burning your credits.

To test before pasting it on your site, use the Test on /embed button — it opens the chat hosted on SquadOS itself, which always works regardless of the allowlist.

Public URL / Widget vs. /hub (internal use)

	Public URL / Widget	/hub
Sign-in	Not required	Required (collaborator of the org)
History per user	Anonymous per session	Persistent per user
Who sees it	Anyone with the link/embed	Only org members
Configuration needed	Yes (Triggers card)	None — every active agent appears

Use Public URL or Widget for the external public. Use Hub for your team’s internal operation.