Connect Streamer.bot
How to connect Kinkajou Bridge to Streamer.bot as a user.
Streamer.bot is optional. Bridge can run printers and OBS overlays without it. Connect Streamer.bot when you want Bridge to trigger Streamer.bot actions (DoAction) on printer events. Overlays still talk to Bridge’s API directly either way.
What Bridge does
Bridge acts as a WebSocket client to Streamer.bot’s WebSocket Server. When a printer event occurs, Bridge calls DoAction on Kinkajou Bridge and passes event_name (for example Kinkajou - Print Started) plus printer/context arguments. The exported router then runs your matching user action when it exists.
Only one Streamer.bot connection is configured in Bridge. It receives events from every printer — cloud-linked and standalone alike.
Setup in Bridge
- In Streamer.bot, enable Servers/Clients → WebSocket Server and note the host, port, endpoint, and password (if any).
- Import the Kinkajou Streamer.bot export (provides the
Kinkajou Bridgerouter action). - In Bridge, open Streamer.bot in the top nav.
- If you are not connected yet, fill in:
- Host (often
127.0.0.1) - Port (often
8080) - Endpoint (often
/) - Password (optional)
- Host (often
- Save. Bridge stays on a connection summary with a status badge. Use Edit connection to change settings (leave the password blank to keep the current value).
If the WebSocket cannot connect, Bridge keeps the integration in an error state — fix the server settings in Streamer.bot, then edit and save again (or restart Bridge).
Next steps
- Create user actions named like
Kinkajou - Print Started— see Streamer.bot Action docs. - For on-stream widgets (no Streamer.bot required), see Overlays in OBS and the overlay developer docs.