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 | Can be hidden on paid plans |
| 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
Section titled “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
Section titled “Activating”- Open the agent in the admin panel.
- Go to Triggers.
- On the Public URL card, click Connect.
- Pick a Slug (3 to 64 characters, lowercase letters, numbers, and hyphens only). It is the last segment of the link.
- SquadOS validates the slug in real time. If it is already in use, pick another.
- 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
Section titled “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
Section titled “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
Section titled “Activating”- Open the agent, go to Triggers.
- On the Site Widget card, click Connect.
- Set up the modal:
- Widget slug — unique identifier used in the script (3 to 64 characters). Appears in the snippet’s
data-agentattribute. - Bubble position — bottom right (default) or bottom left.
- Welcome message (optional) — first message shown when the visitor opens the widget. Useful for guidance.
- Allowed domains — list of domains allowed to embed the widget. Use
*.example.comto whitelist subdomains. You must save at least one domain (or turn on “Allow any domain”). - Allow any domain (not recommended) — any site will be able to embed the widget and burn through your org’s credits.
- Daily credit quota (optional) — cuts off the widget when the limit is reached for the day. Visitors see “limit reached” until the next day.
- Hide “Powered by SquadOS” — removes the SquadOS branding from the widget footer. Available on higher-tier plans only.
- Widget slug — unique identifier used in the script (3 to 64 characters). Appears in the snippet’s
- Click Save and activate widget.
Install snippet
Section titled “Install snippet”Once saved, the modal 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 /embed/<slug> in a new tab so you can see the raw iframe before embedding on your site).
Domain allowlist
Section titled “Domain allowlist”The widget only works when loaded from a listed domain. The loader checks the page’s Origin against the allowlist and blocks it on mismatch. Use this to prevent other sites from embedding your widget and burning your credits.
localhost and 127.0.0.1 are always accepted for development.
Public URL / Widget vs. /hub (internal use)
Section titled “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.