Integrations
Overview of every service OBScure can connect to
Integrations
Each integration page shows a connection status badge (Connected, Connecting…, Not connected, Error) and its own setup fields. Once connected, a service's data becomes available throughout the app — as an Event node trigger, an integration-scoped Variable, a Dashboard card, or an Actions & Queues trigger source.
| Integration | What it's for | Auth |
|---|---|---|
| Twitch | Subscriptions, raids, follows, channel points, chat, live stats | OAuth device-code (no client secret) |
| YouTube | Memberships, Super Chats | Google OAuth (Client ID + Secret) |
| Spotify | Now-playing track data | OAuth + PKCE (no client secret) |
| Streamer.bot | Global variables, chat commands, custom events for Actions | Local WebSocket, optional password |
| OBS | Real-time audio levels for the Equalizer node | Local WebSocket, optional password |
| Windows Media | Now-playing data from any local player (not just Spotify) | None — a toggle |
Twitch, YouTube, and Spotify authenticate over OAuth in your system's default browser; OBScure runs a small local callback server (on port 47891) purely to catch the redirect back from each provider once you approve access — nothing outside your machine ever talks to that server.
Streamer.bot and OBS instead connect directly to a WebSocket server you run locally (Streamer.bot's own "Servers/Clients → WebSocket Server", or OBS's own "Tools → WebSocket Server Settings") — there's no OAuth involved, just a host/port and an optional password if you've turned authentication on at that end.