Relay chat between platforms

1. Confirm both chats can receive replies

Connect your Twitch and YouTube Live chats to the same SSN session. Confirm both appear in the Dock, then send one manual reply to each from a message with a known source tab. Use your own test channels. A read-only capture source cannot send a relay.

Keep only the intended destination chats open for this setup. A platform destination can include multiple eligible source tabs on that platform. If you use a separate Twitch bot account, complete Bot accounts for replies first.

2. Create Twitch → YouTube in Event Flow

Open the Event Flow Editor from SSN’s menu (also linked from the Actions overlay section). Create a flow and give it a clear name such as Twitch to YouTube.

1. Add a From Source trigger from User & Source. Choose Twitch as its source.
2. Add a Relay Chat action and connect the trigger output to the action input.
3. Select that action. Set Relay Destination to YouTube, and keep the message template [{source}] {username}: {message}.
4. Select Save Flow and enable the saved flow. Keep SSN active.
5. Send a fresh normal message in your own Twitch test chat. Confirm one labelled copy arrives in YouTube.

YouTube Shorts has its own source type and destination. Choose YouTube Shorts where appropriate; it is not interchangeable with YouTube.

3. Add the return direction

Create a second flow named YouTube to Twitch: From Source: YouTube → Relay Chat: Twitch. Save and enable it. Send a fresh message from each side and confirm each produces one cross-platform copy.

Keep Relay all messages (!NOT RECOMMENDED!) off when using these flows, so a second relay system is not doing the same work. Also check whether another bot or multistream service is already bridging the chats.

4. Understand reflections

A reflection is a message SSN sent that gets captured again from the destination chat. Current Relay Chat actions skip recognized reflections automatically. They also exclude the originating tab.

To hide the captured echo from the Dock and overlays, add a Reflection Filter action early in the relevant flow and select Block All. Allow First keeps one matching reflection within its configured window; Allow All displays them. This controls display after capture, not where a relay is sent.

5. Narrow what you relay

For commands, add a Message Starts With trigger set to ! and connect it through a NOT gate; combine that result with your source condition using AND before Relay Chat. See the Event Flow guide for connecting logic gates. Test both a normal line and a command.

If you choose the simpler global relay instead, use Global settings and tools → Commands → Pick relay destinations and enter twitch,youtube. A blank list means all eligible destinations. That list controls destinations, not which incoming platforms can trigger a relay. Disable the Event Flow relay pair before enabling this alternative.

SSApp’s account-role allow/block fields in the same Commands section can restrict which accounts send relays. Use the role assigned to your intended sender; an unmatched role can leave no eligible destination.

Troubleshooting

• Nothing sends: retry a manual reply, verify login/posting permission, enable the saved flow, and check destination and account-role restrictions.
• Messages multiply: disable the relay flows first. Check for duplicate capture sources, global Relay all, and external relay bots before retesting one direction.
• Only the Dock shows duplicates: inspect Reflection Filter display policy and global Message - Visibility echo settings.
• Wrong YouTube destination: check YouTube versus YouTube Shorts and close unintended eligible chats.

Test Flow actions can send real messages. Use controlled destinations; a synthetic test does not prove the real source’s account routing.