Streamer.bot adapter

The Streamer.bot adapter receives confirmed KALYIX Tip events. Your existing alert actions can stay in place. You only replace old donation variables with KALYIX variables.

Requirements

  • Streamer.bot 1.0.4 or newer.
  • The current KALYIX Streamer.bot import file from Downloads.
  • An extension token from the Extensions Dashboard.
  • An active KALYIX Tip page.

Setup

  1. Download the Streamer.bot import file.
  2. Import the file into Streamer.bot.
  3. Open the imported KALYIX Setup action.
  4. Enter your extension token in the bridgeToken argument.
  5. Check the bridge URL in the bridgeUrl argument:
wss://extensions.kalyix.de/extensions/ws
  1. In the KALYIX Tip Bridge WebSocket client, make sure TLS is set to TLS 1.2 or Default/System.
  2. On KALYIX Setup, run the imported Test trigger once. This stores the token, URL, and WebSocket index in Streamer.bot.
  3. On KALYIX Connect, run the imported Streamer.bot Started trigger once manually, or use the additional test trigger if your import includes one.
  4. Open the Streamer.bot history. After connecting, you should see hello first and then auth.ok.
  5. Send a test from the Extensions Dashboard.
  6. Create or open an alert action in Streamer.bot.
  7. Use the KALYIX Tip Paid trigger.

After the first successful setup, Streamer.bot reconnects automatically on the next start because KALYIX Connect runs through the imported Streamer.bot Started trigger.

Imported actions and triggers

ActionTriggerPurpose
KALYIX SetupCore -> TestRun once after entering the token. Stores token, bridge URL, and WebSocket index.
KALYIX ConnectCore -> Streamer.bot -> StartedAutomatically connects Streamer.bot to KALYIX when Streamer.bot starts.
KALYIX Connectoptional Core -> TestUseful for the first manual connect or troubleshooting without restarting Streamer.bot.
KALYIX WebSocket MessageCore -> WebSocket -> Client -> MessageHandles hello, sends auth, receives deliveries, and sends ACK.

Streamer.bot events

When a paid tip or test event arrives, the adapter triggers this custom event:

kalyix.tip.paid

In Streamer.bot, use it as a custom trigger. From there, you can add normal sub-actions such as OBS, sound, TTS, logs, Discord, or custom C# logic.

Variables

The most important trigger variables:

VariableMeaning
%kalyixEvent%Event name, for example kalyix.tip.paid.
%kalyixDeliveryId%Delivery ID.
%kalyixEventId%KALYIX event ID.
%kalyixTipId%Tip ID.
%kalyixPaidStatus%True when the tip is paid.
%kalyixAmount%Amount as a number.
%kalyixAmountCents%Amount in cents.
%kalyixCurrency%Currency, for example EUR.
%kalyixUsername%Username, if allowed.
%kalyixDisplayName%Display name, if allowed.
%kalyixMessage%Message, if allowed.
%kalyixGoalId%Goal ID, if allowed.
%kalyixGoalTitle%Goal title, if allowed.
%kalyixPageSlug%Page slug, if allowed.
%kalyixCreatedAt%Event timestamp.
%kalyixRawPayload%Original payload as JSON.

If a field is not allowed, it is not delivered. Build actions so optional variables may be empty.

Send test

The Send test button in the Extensions Dashboard creates a real extension event for the adapter. It is delivered like tip.paid, but it is not stored as a real payment in the Tip payment history.

Troubleshooting

ProblemCheck
No event in Streamer.botIs KALYIX Connect active and is the WebSocket connection open?
auth_timeoutWas the auth action triggered after connecting, and is the token set?
already_authenticatedThe connection is already authenticated. Do not send auth multiple times.
Fields are missingCheck whether the matching data fields are enabled in the dashboard.
Test works, real tips do notCheck whether event:tip.paid is enabled and the Tip page actually creates paid tips.