Skip to content

Spotify song requests from your chat

Viewers request songs with !sr, the queue plays through your own Spotify account, and a now-playing overlay shows it on stream.

Read the guide

New channels can’t join yet. Already using Bloopbot? Sign in.

Now playing overlay
The overlay editor for an overlay called Now playing: the Layers tab lists one Now playing layer, the canvas draws the panel with the track and its Up next list over a sample game backdrop with the layer selected and its toolbar below it, and the settings panel shows Show up next ticked, Songs to show set to 5, Show who requested each song ticked, and a Style section that follows the overlay’s theme.
Pebble, the Bloopbot mascot, waving from the edge of the frame

What chat can do

The Song requests pack installs the commands as flows, so you can rename any of them or change what they say.

CommandWhat it does
!sr song nameRequests a song, or a Spotify link. A refused request is answered with the reason
!songShows the current track
!queueShows the songs coming up
!srstatusTells a viewer how full the queue is and what they have in it, or why !sr would turn them down
!wrongsongTakes back the viewer’s last request
!skip, !removeModerators skip the current song or remove a request
!sron, !sroffModerators open or close requests for the whole channel
!srblock, !srunblockModerators keep a track, an artist or a viewer out of the queue, or let them back in

Requests join your Spotify queue behind whatever you’re playing. Bloopbot never presses play for you, so nothing cuts off the song you and chat are listening to.

Limits are steps you can see

Every request runs through a flow, and the limits live in five variables you change on one page: whether requests are open, how many songs can wait, how many one viewer can hold, how long they wait between requests, and whether the same song can be requested twice.

The Can they request a song? step checks a request against all five before anything is searched for. A refusal comes with a sentence you can send straight to the viewer, such as Queue is full (20 songs max). Try again later.

Want a rule of your own, such as a different line for each refusal? The Check song request limits step hands each fact to the next step — songs in the queue, songs this viewer has queued, seconds until they may ask again — so you can compare it with a number of your own. See gate a flow on the limits.

A flow’s Do this step holding a Check song request limits action: its The song to look up field reads $(from.find.uri) with an Insert… menu beside it and help text explaining that only “already in the queue” needs the link, and its Wait between requests field reads $(var.song_wait_seconds).
The Check song request limits step: The song to look up reads the song Find a song settled on, and Wait between requests follows your wait variable. Click to enlarge.

On stream

Add a Now playing layer to one of your overlays and OBS shows the track that’s playing, the requests coming up next and who asked for each one. It reads the same queue as chat, so a request confirmed in chat appears on screen too. See put now-playing on stream.

The Now playing widget showing Sandstorm by Darude, requested by PixelPal.
The Now playing widget on stream: Sandstorm by Darude, requested by PixelPal. Click to enlarge.

Help from AI, if you want it

Optional AI steps sit inside the same flows:

These may not be available on your channel yet. Smarter song requests with AI shows what each one needs.

Before you start

Song requests may not be available on your channel yet — check what your plan includes.

Set up song requests.

Link Spotify, install the Song requests pack and try !sr on your next stream.

Read the guide

New channels can’t join yet. Already using Bloopbot? Sign in.

Pebble is ready to help