Trigger alerts, sounds and replies with channel points

The short answer

To play a sound when someone redeems a Twitch channel points reward, make a flow in Bloopbot that starts on On a reward redeemed and give it a Play media step with your sound. The sound plays through a Bloopbot overlay you add to OBS as a Browser Source, from your own media library, so there is no Twitch extension or desktop app to install. The same flow can show an alert, reply in chat, read the viewer's message out loud or queue a song instead. Responding to rewards is included on every plan, Free too.

From a new reward to a sound on stream:

1. On Twitch, make the reward in your channel's Channel Points → Manage Rewards.
2. In Bloopbot, open your overlay in Overlays, add a Media layer from Add and press Publish. If the overlay is not in OBS yet, Add an overlay to OBS puts it there as a Browser Source.
3. Open Flows and choose + New flow, then Start blank. Add On a reward redeemed and pick your reward in its Reward field.
4. Add a Play media step after it. Under File, press Upload to add an MP3, OGG or WAV sound (up to 5 MB), or Choose media to pick one you already have.
5. Set Seconds on screen and Volume, then save the flow and switch it on.
6. Redeem the reward yourself on Twitch to hear it.

The rest of this guide covers each step, replying in chat, keeping or refunding the points, rewards on Kick and what to check when nothing plays.

Before you start

For this flow, make a reward on Twitch, in your channel’s Channel Points → Manage Rewards. Bloopbot watches it and does something when it is redeemed. Keep your channel connected on Connections so Bloopbot can read the list. To play a sound or show an alert you also need an overlay open in OBS: Add an overlay to OBS sets one up.

Twitch Channel Points are not the same as Bloopbot loyalty points. Viewers spend Twitch Channel Points on a reward; Bloopbot loyalty points are the separate balance on the Loyalty page.

Eligible channels can unlock Channel Points by completing Twitch’s monetization onboarding before becoming Affiliate. Bloopbot also needs Twitch to allow it to read your rewards and receive redemptions; having Channel Points in Twitch’s dashboard does not guarantee every reward operation is available to other apps. Check which Twitch features your channel can use explains onboarding, permissions and live checks.

Kick has channel rewards too, and they work the same way. Rewards on Kick lists what is different.

Get help with your setup

Optional Help me explains your actual reward-response flow. A blank reward in On a reward redeemed matches every reward, so review its scope. Twitch Channel Points are separate from Bloopbot loyalty points. Test fire is a dry run; setup never creates or spends a real redemption.

1. Start a flow that watches a reward

1. Open Flows and choose + New flow, then Start blank.
2. In Add a node, search for reward and add On a reward redeemed. This is the trigger: it decides which flows start when someone spends points.
3. Give the flow a name you will recognise later, such as “Hydrate alert”.

The trigger node is where the reward is chosen. Everything after it happens because of that redemption.

2. Pick the reward

Select the trigger and open its Reward field. Bloopbot lists the rewards your channel has, with what each one costs, so you pick from what actually exists instead of typing. Choose yours and save.

• The name is what the flow matches on, so a reward renamed on Twitch stops matching. The field keeps showing the old name marked (not on Twitch now) — pick the new one to repair the flow.
• A saved reward that is no longer on Twitch stays selectable, so opening a flow never silently repoints it at a different reward.
• Leave the field on Any reward to run for every reward your channel has — useful for a log or a thank-you.
• If the list is not there the field says why, and you can type the reward’s name exactly as it appears on Twitch. A channel with no rewards yet is told to make one on Twitch; a channel Bloopbot is not allowed to read is not sent anywhere it cannot fix.

3. Say something back

Add a Send a chat message action and connect it to the trigger’s next output. The Insert… menu on that action offers what the redemption carried:

For example:

Thanks for the $(reward), $(user)!

4. Keep or refund the points

Add a Fulfil or refund reward action and connect it after your reply. In Mark the redemption as, choose Fulfilled to leave the points spent, or Cancelled (refund the points) to give them back. Both choices usually belong in the same flow on different branches: keep it when everything went as expected, refund it when it did not — screening the typed-in text is the worked example.

If you save a flow for a picked reward and nothing in it fulfils or refunds the redemption, Bloopbot adds a Fulfil or refund reward step set to Fulfilled after the flow's last step, and the save message says so. It does this once, the first time you save that trigger with a reward picked. Move the step, switch it to a refund or delete it. If you delete it, the trigger shows a warning and the step is not added again. A trigger left on any reward never gets one, and neither does a reward you made on Twitch, for the reason below.

The Check reward text before it goes on stream template tells a viewer their flagged message was held back before attempting a refund. Its Held back exit means the message stayed off screen, not that points returned. A skipped or failed refund leaves the reply in chat and the redemption for you to check in Twitch. Screen a reward’s typed-in text explains the flow and updating an older copy.

Rewards on Kick

A reward you made on Kick starts the same On a reward redeemed trigger, and the same tokens work in the flow: $(user), $(reward), $(cost) and $(query). What differs:

• Which rewards you can pick. On a Kick channel the Reward field lists your Kick rewards. On a Twitch channel with Kick added it lists both, grouped under Twitch rewards and Kick rewards, and the Kick logo shows beside a Kick reward you have chosen. A saved reward Kick no longer lists reads (not on Kick now).
• Which redemptions start the flow. Open More options on the trigger and set Platform to Twitch and Kick, Twitch only or Kick only. The default is both. A Twitch channel with a reward of the same name on both platforms starts on both, unless you pick one platform.
• Reconnect for rewards. A Kick connection made before rewards were supported can't read your rewards. The field then says Reconnect Kick to show your Kick rewards. Choose Reconnect Kick on Connections, then reload the flow editor. Until then you can type the reward’s name exactly as it appears on Kick.
• Accept or reject, not refund. On Kick the same step is called Accept or reject reward. Accepted completes the redemption. Rejected declines it, and Kick decides whether the points go back to the viewer: Bloopbot can't refund them itself. Which of the two happens follows the platform the redemption came from, so one flow can handle both.
• Only rewards Bloopbot created. As on Twitch, Kick lets Bloopbot accept or reject only a reward Bloopbot created, when you import a flow and choose to create its reward. For a reward you made in your Kick dashboard the step fails with a sentence saying so, and the redemption waits in your Kick queue.
• Importing creates the reward on your channel’s platform. On a Kick channel, Create it, switched off makes the reward on Kick, with Kick’s limits: a name of up to 50 characters and at most 50 rewards on the channel. At the limit the import tells you to delete one on Kick first. On a Twitch channel the reward is made on Twitch, even with Kick added.
• Already handled. If a redemption was already accepted or rejected on Kick (for example by you, a moment earlier), the step finishes quietly and the run log reads already closed.

Play a sound or show an alert

A reward can play a sound, a picture or a short video on stream, the way a sound-alert extension does, but from your own media library and through your own overlay.

1. Open your overlay in Overlays and add a Media layer from Add, where pictures should appear. Sounds play from it too. Press Publish.
2. In the reward’s flow, add a Play media step after On a reward redeemed. Under File, press Choose media, or Upload to add an MP3, OGG or WAV sound (up to 5 MB).
3. Set Seconds on screen (1 to 60; a sound stops when the time is up) and Volume (0 to 100), then save the flow and switch it on.

For example, a reward called Airhorn with Play media set to airhorn.wav for 3 seconds plays the horn on every open overlay that has a Media layer. Media waits its turn behind any alert already on screen, so two redemptions in a row never play over each other.

To show a full alert card for the redemption instead, with the viewer’s name and avatar, add a Redemption alert layer to the overlay and tick Channel points redemption for it under Choose what plays it…, picking the reward first. Choose what plays it walks through it, and Play images, videos and sounds covers the Media layer in full.

A reward can also read the viewer’s words out loud: the Text to speech pack makes a Speak a message reward for you, and the Speak text step does the same for a reward of your own. Let viewers send text-to-speech shows how.

A reward can also queue a song on your Spotify: see take requests with channel points.

Check it works

1. Press Save, then Test fire. The dry run uses a realistic example redemption — “Hydrate!” by Thirstygamer — so the branches your conditions check take a real path. Because the example is always “Hydrate!”, a flow set to another reward stops at its trigger with a different reward (Hydrate!); leave Reward on Any reward while you test, then pick your reward again before you switch the flow on.
2. Expand the Run log and confirm which nodes ran and what each decided. A Play media step reads queued. Request a song reads dry run: the example carries Thirstygamer as the viewer and records a simulated request. Nothing here reaches Twitch or Spotify: a test fire never fulfils or refunds a real redemption and never spends real points.
3. Redeem the reward yourself in Twitch to confirm the live path. The flow’s row on Flows shows when it last ran and how it ended.

Troubleshooting

• Nothing happened when the reward was redeemed: the flow is paused, the reward was renamed on Twitch since you picked it (the field shows it as not on Twitch now), or another flow already handles that reward — check Needs attention on Flows for what stopped.
• Every reward starts the flow: the Reward field is on Any reward.
• The flow ran but no sound played: the overlay with the Media layer is not open in OBS, or it was not published after you added the layer. The run log shows the step as queued even when no overlay is open to play it.
• The sound plays twice: OBS has just started and you have not clicked through the scenes with the overlay yet, the overlay is also open in a browser tab, or Studio Mode shows it in both Preview and Program. Click through those scenes once, or close the extra copy, as in alerts in more than one scene.
• The sound never played: the overlay's scene was hidden in OBS for more than two minutes after the redemption. Media waits while every overlay with the Media layer is hidden, and plays when you show one.
• Channel Points are missing from your Twitch dashboard: Twitch offers Channel Points to Affiliates, Partners and channels that have finished its monetization onboarding. Check which Twitch features your channel can use.
• The points are not refunded, or the redemption sits in your Twitch queue: that is the step 4 limitation — Twitch will not let Bloopbot complete a redemption for a reward you made yourself, so the step skips it and the run log says so. Action it in Twitch, or switch on Skip Reward Requests Queue for the reward on Twitch.
• Kick rewards are missing from the Reward field: reconnect Kick, as Rewards on Kick describes.
• The list is missing from the Reward field: read the reason it shows. For missing permission, choose Re-authorize on Connections, then reload. For unavailable rewards, check Channel Points and monetization onboarding in Twitch’s Creator Dashboard; reconnecting does not change feature availability. You can type the exact reward name, but that does not make Twitch deliver events it has refused.