OBS Studio
TipLink can connect to OBS Studio over its built-in WebSocket server. Once connected, TipLink receives events like scene changes, stream start/stop, and recording start/stop. These can be used as alert triggers.
Requirements
- OBS Studio 28 or newer (the WebSocket server is built in)
- TipLink V2 desktop app
Enable the WebSocket Server in OBS
- Open OBS Studio.
- In the menu bar, go to Tools → WebSocket Server Settings.
- Check Enable WebSocket Server.
- Note down the Server Port (default is
4455). - If you want password protection, check Enable Authentication and set a password.
- Click OK.
TipLink connects to OBS's WebSocket server while OBS is running. If OBS is closed, the connection will drop. TipLink will automatically retry up to 5 times with increasing delays.
Add Your OBS Account in TipLink
- Open TipLink and go to Connect Your Platforms.
- Find OBS Studio and click Add Account.
- Fill in your connection details:
| Field | Description | Default |
|---|---|---|
| Host | The computer OBS is running on. Use localhost if it's the same machine. | localhost |
| Port | The WebSocket server port from OBS settings. | 4455 |
| Password | The authentication password, if you enabled it in OBS. Leave blank if you did not. | (none) |
- Click Save.
Connect
Click the Connect button next to your OBS Studio account.
If the connection is successful, the button will change to Disconnect and the account will show as active.
Enable Auto Connect on the account to have TipLink connect to OBS automatically every time TipLink starts.
Supported Events
Once connected, TipLink can receive the following events from OBS:
| Event | Description | Event Data |
|---|---|---|
| Scene Changed | Fired when you switch to a different scene | {{ sceneName }} — the name of the new scene |
| Stream Started | Fired when your stream goes live | (no extra data) |
| Stream Stopped | Fired when your stream ends | (no extra data) |
| Recording Started | Fired when recording begins | {{ outputPath }} — the file path being recorded to |
| Recording Stopped | Fired when recording ends | (no extra data) |
| Source Visibility Changed | Fired when a source is shown or hidden in a scene | {{ sceneName }}, {{ sourceId }}, {{ enabled }} |
Using OBS Events in Alerts
You can use these events as Triggers in any alert.
Example: Send a Discord message when you go live
- Create a new alert.
- Set the trigger to OBS Studio → Stream Started.
- Add a Send to Discord action with the message
Stream is now live! - Save.
Example: Change an overlay widget when a scene changes
- Create a new alert.
- Set the trigger to OBS Studio → Scene Changed.
- Optionally, use
{{ sceneName }}in an action to display the current scene name. - Save.
Troubleshooting
TipLink can't connect to OBS
- Make sure OBS is open and the WebSocket server is enabled (Tools → WebSocket Server Settings).
- Check that the Host, Port, and Password in TipLink match the OBS settings exactly.
- If OBS is on the same computer, Host should be
localhost. - Check that your firewall isn't blocking port
4455.
Connection keeps dropping
- TipLink will automatically try to reconnect up to 5 times. After that, reconnect manually.
- Make sure OBS hasn't crashed or been restarted without TipLink noticing.
Remove the Account
- Go to Connect Your Platforms → OBS Studio.
- Click Disconnect if the account is connected.
- Click Remove Account.