Connecting StreamSync and StreamHub
If you run both apps, you can link them so a StreamSync trigger — a raid, a follow, a chat command, anything — can post straight to any destination you've connected in StreamHub (Discord, and in Pro, Facebook, Instagram, YouTube, X, or Threads). This page covers that link from both sides; see StreamSync or StreamHub for everything else each app does on its own.
🍼 ELI5
StreamHub runs a little local server. You give StreamSync its address and password once, and after that, any StreamSync trigger can say "post this to Discord for me" without you touching StreamHub at all. Both apps have to be running on the same computer (or network) for this to work.
Requirements
- StreamHub running on the same machine (or one reachable on the same network)
- At least one posting destination configured in StreamHub (Connections page — Discord, Facebook, Instagram, YouTube, X/Twitter, or Threads)
- StreamSync running with the Triggers & Actions module active
Starting the StreamHub server
- Open StreamHub → Connections
- In the StreamSync section, click Start to start the local WebSocket server
- Note the Port (default:
5680) and the generated Password - Use Regenerate if you want to issue a new password (any previously connected StreamSync client will need the new one)
The server only binds to 127.0.0.1 — it is never reachable from another machine, even on the same network.
Connecting StreamSync to StreamHub
- Open StreamSync → Triggers → Integrations tab → StreamHub
- Enter the host (
127.0.0.1unless StreamHub is on another machine), port, and password from StreamHub's Connections page - Click Save settings, then Connect
- The status badge changes to connected when the handshake succeeds, and the destinations configured in StreamHub (e.g. Discord webhooks) appear in the Connections list
Unlike OBS, this link auto-reconnects: if StreamHub restarts or the connection drops unexpectedly, StreamSync retries every 5 seconds until it succeeds. It still won't connect automatically on app launch — click Connect once per session.
What StreamSync can do with StreamHub
As a trigger
StreamHub forwards its own post events back to StreamSync in real time, so a trigger rule can react to what StreamHub does:
- StreamHub Post Published — fires when a post (e.g. a Discord webhook message) is sent successfully.
- StreamHub Post Failed — fires when a post fails to send.
As an action
- Post via StreamHub — sends a message to any destination configured in StreamHub. Pick the destination from the Destination dropdown (populated from StreamHub's connected accounts — Discord webhooks, Facebook Pages, Instagram, YouTube channel, X/Twitter, or Threads), write a Message (supports the usual
{user}/{bits}/{viewers}variables), and optionally include an Image URL.
This reuses the same posting logic as StreamHub's own Post page — StreamSync never sees API tokens or webhook URLs, only an opaque destination ID and label.
See Triggers & Actions for how rules, queues, and actions fit together in StreamSync generally.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Connection times out | StreamHub's server isn't started | Click Start in StreamHub → Connections → StreamSync |
| Auth failed | Wrong password | Copy the password shown in StreamHub → Connections → StreamSync exactly (use Show to reveal it) |
| No destinations in the dropdown | No accounts connected yet | Connect at least one platform in StreamHub → Connections (Discord, Facebook, Instagram, YouTube, X, or Threads) |
| "Post via StreamHub" action fails in the queue | StreamHub disconnected at rule-fire time | Reconnect to StreamHub before going live |
| Connection drops repeatedly | StreamHub closed or password changed | Reopen StreamHub, or re-enter the new password and reconnect |