Studio Queues Team · Last updated July 17, 2026
Twitch chat commands for artists: the six baseline commands every art streamer needs, Nightbot setup steps, and how to wire your commission queue to chat.
Twitch chat commands for artists are one of the highest-leverage things you can set up on a stream, and one of the most consistently underused. A well-configured chat bot answers "when do commissions open," "what are your prices," "where's your portfolio," and "what's the current commission" without you breaking flow, without needing a moderator on duty, and without the same message getting typed forty times an hour. This guide walks through what chat commands actually do on an art stream, the three bots to know, the core commands every art streamer should set up, how to connect them to your commission queue live, and where to go from basic to advanced setups.
Chat commands are short prefixed messages (typically starting with !) that trigger an automatic response from a bot in your Twitch chat. A viewer types !prices, the bot responds with your pricing info. A viewer types !queue, the bot responds with your queue status. You never see the interaction until you look, and it happens every time someone asks.
On an art stream specifically, this matters more than on a gaming stream because viewers arriving mid-piece almost always ask the same questions: what are you drawing, who is it for, are commissions open, how do I get one, what's your pricing. Every one of those questions has a stable answer that a command can deliver instantly. Skip commands and you either answer the same questions on a loop (breaks your flow) or ignore them (viewer feels unwelcome). Neither is a good option once your channel starts growing.
The three bots most Twitch art streamers use are Nightbot, StreamElements, and Fossabot. All three are free to use for the core command features. All three connect to your Twitch account with standard OAuth and moderate your chat, respond to commands, and support external HTTP-fetch commands (which is how you'll pull live data from your commission queue).
Nightbot is the oldest and most-installed. Its custom-command syntax is documented at the Nightbot commands documentation, with the URL-fetching feature documented separately as the Nightbot UrlFetch variable. It is the safest default for a first-time chat bot setup.
StreamElements bundles chat bot functionality with overlay hosting, tipping, and subscriber management. It uses ${customapi.url} as its equivalent of Nightbot's $(urlfetch url). Streamers who want an all-in-one platform for overlays and chat commands often prefer it.
Fossabot is the newer entrant, built specifically for larger channels that need faster moderation and more granular permission control. It also supports URL-fetching for custom commands.
You do not need more than one. Pick one, install it, and stick with it. Running two chat bots on the same channel creates duplicate responses, permission conflicts, and confusion. This guide uses Nightbot examples for setup syntax, but every command pattern here works on the other two with minor syntax differences.
A working set of twitch chat commands for artists covers the questions viewers actually ask. The minimum baseline is six commands:
!commission: Are commissions currently open or closed? Include a link to how to buy in if open.!queue: What is the current queue status? How many slots are available, or when will the next round open?!prices: A short summary of your standard pricing, or a link to your rate card.!portfolio: A link to where viewers can see more of your work.!socials: Links to your Twitter/X, Instagram, Bluesky, or wherever else you post.!current: Who or what you are currently drawing on stream.Some optional additions that pay off once you have the baseline running:
!discord: Invite link to your community Discord.!tip: Link to your Ko-fi, Streamlabs, or other tip jar.!lurk: Fun message for viewers who join and go idle.!raid: Message for viewers who arrive during a raid.!brush: What software and brushes you are using (art viewers ask this constantly).Twitch chat commands for artists work best when they are short, predictable, and rarely edited. Viewers memorize what your commands do and use them consistently. Rewriting the response for !prices every three months confuses regulars.
Setup takes about five minutes once your Nightbot is connected to your Twitch account. Steps:
!prices) and the response text.You can also add commands from chat directly using Nightbot's own !commands syntax. Example: typing !commands add !prices Standard rates start at $80 for a bust, $200 for a half-body. Full rate card: yourportfolio.com/prices in chat adds that command instantly. Per the Nightbot documentation, you can specify a user level with -ul= (owner, moderator, twitch_vip, subscriber, regular, everyone) and a cooldown with -cd= in seconds, so !commands add -cd=30 -ul=everyone !prices [response] restricts to a 30-second cooldown while allowing anyone to trigger it.
Test each command in your own chat before your first stream. Commands with broken links, missing spaces, or unclear phrasing feel worse to viewers than no command at all.
Static commands are useful. Live commands that reflect real-time queue data are transformative. When a viewer types !queue and gets back "3 of 5 slots open, taking commissions" pulled from the actual state of your queue that second, you have removed one of the biggest gaps between streamer and stream: the delay between what the viewer sees and what is actually true right now.
Studio Queues provides direct chat endpoints for exactly this. Each artist account gets a unique API token and three chat endpoints that return live one-line responses ready to plug into any bot that supports URL fetching. The endpoints are:
https://studioqueues.com/api/chat/YOUR_ARTIST_TOKEN/queue: Returns your current queue count and open/closed status.https://studioqueues.com/api/chat/YOUR_ARTIST_TOKEN/status: Returns whether commissions are currently open or closed.https://studioqueues.com/api/chat/YOUR_ARTIST_TOKEN/prices: Returns your current price summary as configured in your Studio Queues account.Replace YOUR_ARTIST_TOKEN with the token from your Studio Queues account. Do not share the URL publicly the way you would a portfolio link; treat it as you would any API key.
To wire the queue endpoint into Nightbot, add this command in your chat:
!addcom !queue $(urlfetch https://studioqueues.com/api/chat/YOUR_ARTIST_TOKEN/queue)From that moment on, every time a viewer types !queue, Nightbot fetches the current queue state from Studio Queues and responds with the live count and status. The same pattern works for the status and prices endpoints:
!addcom !commission $(urlfetch https://studioqueues.com/api/chat/YOUR_ARTIST_TOKEN/status)
!addcom !prices $(urlfetch https://studioqueues.com/api/chat/YOUR_ARTIST_TOKEN/prices)On StreamElements, the equivalent is ${customapi.url}. On Fossabot, the equivalent uses their fetch variable. The Studio Queues endpoints return plain text under Nightbot's 400-character response limit, so no transformation is needed on the artist's side. Open the queue on Studio Queues, and the next !queue from chat reflects it. Close it, same thing. Update your prices in your Studio Queues account, and the next !prices response reflects the new rates automatically.
This is one of the practical upsides of routing commissions through a workflow platform rather than a spreadsheet: the operational data your viewers ask about is the same data the platform already tracks. For context on how the chat command layer connects to the overlay layer (both driven by the same queue data), see how these commands integrate with your OBS overlay.
Once the baseline works, three patterns are worth learning:
User-specific responses with variables. Nightbot supports variables like $(user) (the viewer who ran the command) and $(touser) (the first argument passed to the command). A command like !shoutout can respond with a message that includes the target user's name automatically. Nightbot documents its variable syntax on its official variables page.
Cooldowns. Cooldowns prevent commands from spamming chat. A 30-second cooldown on !prices is standard. High-cooldown values (5+ minutes) are appropriate for commands that link to expensive-to-load pages or that would look weird to see too frequently. Cooldowns are set via the -cd= parameter when adding commands, or in the Nightbot dashboard.
Permission tiers. Some commands should be restricted. A command like !open that flips your queue from closed to open should be moderator-only, not everyone. Nightbot supports user levels including everyone, subscriber, regular, twitch_vip, moderator, and owner. Set them via -ul= when adding a command.
Once you have the baseline set up, add advanced patterns incrementally. Setting up eleven complex commands before your first stream is overengineering; setting up six simple ones you actually use every stream is the right starting point. For more resources on running the streaming side of a commission practice, browse more Studio Queues resources for streamer artists.
One habit worth building from the beginning: review your commands every three months. Old links go stale, your pricing structure changes, and commands that were useful when your channel was small can start to feel out of date once your audience shifts. The maintenance cost is low, and stale commands are worse than no commands at all because they signal to viewers that nobody is minding the shop.
Twitch chat commands for artists solve one of the most predictable problems on an art stream: viewers arriving mid-piece with the same questions the last twenty viewers asked. Six baseline commands (!commission, !queue, !prices, !portfolio, !socials, !current) handle roughly 90 percent of that traffic. Nightbot, StreamElements, and Fossabot are the three bots that get the job done; pick one, set up the baseline, and run it. Static commands take five minutes each; wiring your commission queue to live chat responses via URL-fetching takes another ten. The whole system is under an hour of one-time setup and pays off every subsequent stream.
Studio Queues provides direct chat command endpoints for !queue, !commission, and !prices that update live from your account, so you configure your queue once in your Studio Queues dashboard and never edit the chat command response again. Change your prices there, chat reflects it. Open or close the queue, chat reflects it.
If you want a workflow platform with built-in chat command endpoints, an OBS queue overlay, and milestone-based payment support in one place, you can lock in 0% platform fees while founding artist spots are still open. The founding artist program keeps 0% platform fees active for as long as your premium subscription stays active, and only the first 500 spots are available. Payment processing fees (Stripe) still apply the same way they would on any platform.
