Frequently asked

Yes, and it'll stay that way — every core feature (moderation, appeals, logging, tickets, welcome messages, join and reaction roles, polls, events, birthdays, Twitch/Kick/YouTube/TikTok notifications, the Message Builder, the Twitch chat bot) is free to use, and safety tools never sit behind a paywall. Supporting the project on Patreon gets you one of two plans for one of your servers: TrinketSupporter raises the limits on the tools that cost something to run (more custom and word commands, feeds, automations, webhooks, forms, uploads and so on), and TrinketChad includes all of that with bigger limits and Bot Identity — the bot's own nickname, avatar and bio on your server. Either one also gives you a glowing Supporter name and badge. The Premium page lists exactly what each plan allows. It also helps a ton in keeping the project funded and actively worked on.

No. Every module is its own switch on its own settings page, so a server can run just go-live alerts, or just moderation, or the whole set. Nothing posts until you turn it on and pick a channel — with one exception, Scam Shield, the one protection that is on from the start (see the next question).

Scam Shield is the one protection that starts on in every server, because scam accounts reach a new server first and a protection that waits to be set up arrives too late. It reads each new message the way a message filter does, judges whether it looks like a scam (fake gifts, wallet links, fake support, look-alike websites, programs from brand-new accounts, the same message in many channels), and can delete it and time out the sender. It does not store messages. It starts alert-only: for the first 48 hours it only posts what it would have done in an alert channel, so you can see it is right before it removes anything, and it never bans without somewhere staff can review the ban. Switch it off, add trusted roles or mark a website as safe on its page. What it reads and keeps is in the Privacy Policy, and how it decides is in the documentation.

The server's owner and anyone who has the Administrator permission there — nobody else, and having Manage Server alone is not enough, because what the dashboard changes (automatic kicks and bans, roles, channels) is more than that permission is meant for. It is checked against Discord, never taken from a saved list, and an answer is kept for only a few seconds — and dropped the moment Discord tells TrinketBot that someone's roles or a role's permissions changed — so taking the permission away takes effect within moments. You can see who has it on the server's Overview page.

TrinketBot is invited without Administrator. The invite link asks for the permissions its features use — for example Manage Roles for join roles and verification, Manage Channels for tickets and counter channels, Timeout Members for timeouts. If one is missing, the dashboard says so: the module that needs it shows which permission, what stops working without it, and how to grant it (Server Settings → Roles → TrinketBot, or add the bot again with the current invite link). Nothing breaks silently. Every permission, and which feature uses it for what, is listed on the permissions page. A channel also has to be visible to TrinketBot's role: from 2026-11-16 Discord no longer shows bots the channels they can't view, so a module whose channel TrinketBot can't see says so in its last error or when you test it, and you give it View Channel there or choose another channel.

You choose in your account settings: delete it immediately when TrinketBot leaves, or keep the default 3-day grace period so nothing is lost if you add the bot back.

An account you haven't logged in to for a year and that has nothing active — no Patreon membership in good standing, and for a Twitch channel account no bot or events switched on — is deleted automatically. Your servers' data is never touched by this, and logging in again simply makes a new account. You can also delete your account yourself at any time from Settings; see the Privacy Policy.

Start with the documentation — every module has its own section — and the status page if something seems down. Still stuck? Join the TrinketBot Support server and ask there.

Both halves work alone. The Discord bot is set up for a server, on its dashboard, with a login with Discord. The Twitch chat bot is set up for a Twitch channel, in the streamer area, with a login with Twitch. Together they give you go-live alerts, raid cards and clip cards in Discord, thank-yous for follows and subs in chat and in Discord, a Twitch log in a private channel, and your server's news in your chat through Make, Zapier or n8n. The guide has a recipe for each, with what to expect and what to check.

They are two areas. Your servers use a login with Discord, and the streamer area for your Twitch channel uses a login with Twitch. Neither gives TrinketBot a token of your own Twitch account. Linking Discord from the streamer area is optional, keeps only your Discord user ID and when you linked it, and is not a login. Neither login brings you back to where you were, so a link from one to the other says which login it will ask for. See the guide.

No. The Discord bot works in Discord servers. The Twitch chat bot chats in Twitch chat as its own Twitch account. They share a name, a website, a support server and your plan, but they are set up separately and neither needs the other.

The admin (Manage Server) sets up the go-live alert, Live status, Raids & clips and the schedule on the server's dashboard, and tells the streamer first: TrinketBot reads a channel's public Twitch data and doesn't ask the streamer to confirm. The streamer logs in with Twitch for the chat bot. To post the streamer's events in the server, the streamer links a Discord account that manages it, or the admin gives them a Discord webhook address. The checklist has the rest.

Go-live alerts and Live status work for Kick and YouTube, and so do webhooks, with YouTube uploads as well. The Twitch chat bot, raid cards, clip cards, the weekly clips post and the schedule are Twitch only, and there is no chat bot for Kick or YouTube chat. A Kick or YouTube go-live can be said in a Twitch chat through the Discord-to-chat recipe. The table has the details.

On the server's dashboard, connect the Twitch channel, then open Raids & clips, switch on Post new clips and choose a channel. A card usually comes 1.5 to 6.5 minutes after the clip was made, because TrinketBot looks every 5 minutes at clips that have had about 90 seconds to finish. A clip made with the Twitch chat bot's clip command is posted as soon as Twitch has finished it, and the later check doesn't post it again. Clips made before you switched it on aren't posted, each clip is posted once per channel, and if more than five turn up in one check the newest five are posted with a line saying how many more there were. A new clip can also start an Automation, and the card can be switched off for that. Once clips are on, the Clips card has an Is it working? box that shows what is stuck. If cards don't come, check that the channel is connected and that TrinketBot has View Channel, Send Messages and Embed Links there. See the recipe.

Yes. On the server's Raids & clips page, switch on Post the most-watched clips once a week, choose a channel, a day and an hour (in UTC) and, if you like, a role to ping. Once a week TrinketBot posts the 3 clips of the week that Twitch counts the most views for, as one message with a card for each. Nobody has to vote. Saving doesn't post anything, a week without clips posts nothing, and if TrinketBot was down at the chosen time it still posts within 12 hours. It is separate from Post new clips, which posts every clip as it is made, and from the weekly pick in Art & clips, which is for what your members post and vote on. See Raids & clips.

Yes. A Twitch raid and A new Twitch clip are choices under When in the server's Automations, and events for webhooks too. They start only while Raids or Post new clips is switched on under Raids & clips. A raid rule hears only the raids that the server's direction and smallest raid let through, and TrinketBot's own card is posted as well unless you switch its Post a card in a channel switch off there. Each rule is one of the server's rules, and how many a server can have depends on its plan. The recipe has the steps.

Yes, two, on the Automations page under Ready-made rules: ping a role when a stream starts in a game, and welcome a raid. Use this rule opens the editor with the rule filled in, and nothing is created until you press Save rule. It is then an ordinary rule and uses one of the server's rules, which depends on its plan. Each one shows what it needs switched on elsewhere and links to the page that fixes it. Neither replaces TrinketBot's own go-live alert or raid card: the rule is a second post. See the documentation.

A Twitch connection made now starts on mark the alert as ended: a couple of minutes after the stream is over the alert gets a note with how long it ran, and its Watch button becomes a replay link (or goes, if Twitch didn't save the stream). A server that connected before keeps what it chose, and Kick and YouTube start on leaving the alert as it is. On Twitch the note can also say the most viewers TrinketBot saw and carry up to 3 buttons for the stream's most-viewed clips, if the server ticks Add the stream's peak viewers and best clips; it is off until then. Change it under When the stream ends on the platform's page. See the documentation.

Use Discord's own Twitch integration, under Server Settings, Integrations. It is for Twitch Partners and Affiliates, and Discord keeps the subscriber roles up to date. TrinketBot doesn't copy it, because reading who subscribes needs your own Twitch login, which TrinketBot never keeps. In TrinketBot those roles can be a condition, not a reward: a giveaway's required role, a leveling XP multiplier, a reaction-role panel's required role or the go-live ping role. Discord has the same for YouTube members. Mind the setting for when a subscription ends: Discord can remove the role, or kick the member. The guide has the steps.

No. A pledge puts your Discord account on a plan. On the Premium page you assign it to one server, and your Twitch channel's chat bot takes the plan of the Discord account you linked on the streamer's Connect page, with no server slot used. Link the same account in both places. If the plan ends, both go back to the free plan and nothing is deleted. A plan bought for a server covers only that server. See the guide.

Yes. The Twitch chat bot has its own login: go to the streamer area, log in with Twitch and press Set it up for me. It answers commands, posts timers, keeps quotes and thanks people for follows, subs and raids — and it works whether or not you have a Discord server. It runs in the cloud, so it works while your PC is off. The documentation walks through every part.

It answers your chat commands (with counters, and live facts like the game and uptime, your next streams from your Twitch schedule and your Discord link), posts timers while you're live, keeps quotes, and reacts to follows, subs, resubs, gifted subs, cheers, raids, hype trains and channel point rewards — in chat, in a Discord channel, at a web address of yours, or any mix. Other tools such as a Stream Deck or Streamer.bot can make it talk with a key. It can also moderate: commands for your moderators and filters that remove links, spam and blocked words. Everything is optional.

Yes. Events, the Discord link, the web address, the key for other tools and every moderation tool are all free, and so is a good amount of the rest: 20 commands, 5 timers and 200 quotes, 25 blocked words. If your channel leans on the bot, TrinketSupporter raises that to 60, 15 and 1,000 (100 blocked words) and TrinketChad to 150, 40 and 5,000 (300 blocked words) — through the Discord account you link, with no server needed, and TrinketChad also lets the bot chat as your own bot account. Going over a limit never deletes anything; the newest commands and timers just pause. See the Premium page.

Your Twitch name and picture, the list of permissions you gave it, and what you set up (commands, timers, quotes, event settings, an optional Discord link and web address, and the Discord invite you save for chat). It keeps no token of your own Twitch account and none of your chat — the only Twitch token it holds belongs to a bot account (its own, or the one you make with TrinketChad), encrypted, and used for clips, follow lookups and checking which emotes the bot can use only. Delete my channel account removes your channel's settings, commands, timers, quotes, events, links and key in one step, except go-live alerts that Discord servers have set up for your channel, which belong to the server. An account left unused for a year is deleted automatically. The Privacy Policy lists it all.

Logging in only asks to let the bot join your chat. Twitch shares follows, subs, cheers, hype trains and channel point rewards only after you allow each, and TrinketBot asks only for the ones you switch on. Raids need no permission. You can withdraw any of them in Twitch's Settings → Connections.

Yes, two ways. Link your Discord account (one click, then pick the server and channel from a list), or paste a Discord webhook — no linking, and TrinketBot doesn't even have to be in that server. Both are on the Connect page, with step-by-step instructions: how Connect works. If TrinketBot isn't in a server you manage, Connect has an Add TrinketBot to a server button. With a linked account, the server's admins can see on the server's Twitch page that your channel posts there, and can remove it. The Discord dashboard and the streamer area have separate logins, with Discord and with Twitch. A linked account can also hand your events to the server's automations, instead of or as well as posting them.

Yes. Make a key on the Connect page and the tool sends a request to an address that contains it — a Stream Deck Website button (with GET request in background), a Streamer.bot Fetch URL sub-action, a script, Make or Zapier — to make the bot say something or run one of your commands. A command that makes a clip answers with its link and whether Twitch had finished it, and what you send as the arguments becomes the clip's title. Events can also be sent out to Zapier, Make, n8n or your own server. The Connect page shows the exact steps for each, with your key filled in.

Yes, with TrinketChad. You make a Twitch account for your bot (call it anything), authorize it once with a one-time link, and from then on the bot reads and writes your chat as that account, with its own name and picture. TrinketBot keeps the account's name and an encrypted token for it (used only for clips, follow lookups and checking which emotes it can use), which goes when you go back to TrinketBot's own account. The Overview walks you through it, and one button does that. See the documentation.

Yes, once you make the bot a moderator in your chat (/mod and its name). The moderator commands (!so, !announce, !to, !ban, !unban, !permit, !clip, !followage) are ordinary commands you add with one button: each has its own On switch, and you can rename it, rewrite what it says or delete it. On the Moderation page you also choose filters for links, capital letters, symbols, emote spam, repeats and blocked words. A filter deletes the first slip and times the chatter out on a repeat; you and your moderators are never filtered. Every action shows in Twitch's own moderation log under the bot's name, and you decide the rules. See the documentation.

Yes. A command has an action (shout out a channel, time out, ban, unban, let someone post links, make a clip, say how long someone has followed) and a way of answering (a chat message or a highlighted announcement). Set !so to the shoutout action and answer with an announcement saying Go and check out {touser}!, and one command gives Twitch's shoutout card and an announcement together. Every command can also be switched off on its own. See Commands.

Yes, if its account has earned them: a subscriber emote needs a subscription to your channel for the bot account, so have a moderator or friend gift it a sub (Twitch doesn't let you subscribe in your own channel). Every message box has an Add an emote picker with your emotes and Twitch's global ones, and a lock marks the ones the bot can't use yet. Global emotes always work. See Emotes and the bot's subscription.

Yes. Link Discord, choose a channel (ideally one just for the log), and switch on what you want to keep: bans and timeouts, unbans, deleted messages, cleared chats, and optionally every chat message. Lines are grouped into one Discord message every few seconds, so a busy chat or a raid doesn't flood the channel. Deleted messages show what they said if the bot saw them in the last 15 minutes. A chat log shows chatters' names, so use a private staff channel; the server's admins can see on the server's Twitch page that it is on. Details and what it can't see are in the documentation.

Two things can post a raid card: your server's Raids & clips, and the chat bot's Incoming raid event if you chose to post it in Discord. If both post into the same channel, only the server's card is posted and both pages say so. If they post into different channels you get two cards, and the Events page has a Turn this one off button. A raid under the server's smallest size, on a server that only announces raids you send, or on a server whose card is switched off, isn't covered, so the chat bot's card is posted. A Discord webhook used as your web address is not de-duplicated, and neither is an Automation that starts from a Twitch raid: with the server's Post a card in a channel switch on, the rule and the card both post, so switch the card off on Raids & clips if the rule is enough. See the recipe.

Not directly: there is no built-in route from Discord into your chat. A webhook of your server into Make, Zapier or n8n, then a say request to your key, works with no code; the tab From your Discord server on Connect has the steps. Whoever builds the scenario holds your key, so build it yourself or make a new key afterwards. Let a go-live through only when its platform is not Twitch, or your own go-live comes back. If the tool in the middle is slow, a line can be said twice. Member events never go in, since they carry people's Discord names.

Yes, once Discord is linked and you manage the server: choose the server on Connect and press Turn on the go-live alert. There is nothing to type. A server has one main Twitch channel, so if it already has another the card says so. A new alert starts on mark it as ended. Manage Server is checked once, when you switch it on, and then the alert belongs to the server: it stays on if you unlink Discord or delete your account, until someone who manages the server switches it off. It doesn't set up Live status, raids or clips. Live status follows the alert's switch, so it works only while the alert is on; the Live status page's Is it working? box shows that.

Anyone who manages the server sees it on the server's Twitch page, under Streamers posting here: the channel, the Discord channel it posts in, which events and log parts are on, whether every chat message is logged, and which events it hands to the server's automations. Remove stops it all, and the streamer can choose the server again for as long as their linked account still manages it, but has to switch the automations on again. Posts made through a Discord webhook aren't listed; look under Server Settings, Integrations, Webhooks in Discord. You can also take Manage Server from the linked account, or deny TrinketBot Send Messages in that channel.

Yes, it posts a card. When the bot makes a clip, TrinketBot posts a card for it as soon as Twitch has the clip: in each server whose main Twitch channel is yours, with Post new clips on and a clips channel TrinketBot can post in, and in your own Discord channel if you switch on Clip made with the bot on the Events page. A server's card never says who asked. The card in your own channel can say “Requested in chat by” and the viewer's chat name; that switch is Say who asked for it, on by default, and the name is never put on the clip on Twitch. A moderator, or you, can give the clip a title by typing it after the command; words from anyone else are ignored. The bot waits up to 12 seconds for Twitch to finish the clip before it answers in chat, then keeps asking for up to 40 seconds more; after that the command posts no card, and it makes a card for no more than 20 clips an hour for a channel. See the recipe.

Yes, if you hand them over. Link a Discord account that manages the server, choose the server on Connect, and on the Events page switch on Let my server's automations react for the follows, subs, resubs, gifts, cheers, hype trains and reward redemptions you want; each still needs its Twitch permission. Then someone who manages the server writes a rule on its Automations page, under From a streamer's Twitch channel. Rules can post a message but never give or take a role, since a viewer isn't a member of the server. Each time an event is handed over, TrinketBot checks that your linked account still manages the server, and choosing a different server turns it off, so each server is agreed to on its own. Turn all off is on Connect. See the recipe.

Only the rules of the one server you chose, and whatever those rules post there. A rule gets the viewer's Twitch name, the tier and the amount (bits, gifted subs, months, hype train level, reward and its cost) and the channel, and never anything a viewer wrote: not a resub message, not the words of a cheer, not what a reward asked them to type. The people who manage that server can see on its Twitch page which events you hand over, and they can remove your channel. You can turn it all off on Connect.

Save your invite on the Connect page, under Your Discord link for chat, then use {discord} in a command or a timer; the discord example on Commands and the Discord invite example on Timers start from it. Chat gets the saved link, so replacing it there changes every command and timer. Nothing needs to be linked for this. The card checks the link with Discord each time you open it and says if it has expired, was deleted, is paused or leads to another server, and it shows how to make one that never expires. A command or timer that says {discord} can't be switched on while no link is saved, and says nothing if the link is removed. See the recipe.

Yes: put {schedule} in a command or a timer. It says up to 3 of your next streams from the schedule you plan on Twitch, each as a time in UTC with the time left, because chat can't show each viewer their own timezone. TrinketBot keeps what it read from Twitch for 5 minutes, so a change you make shows within about that long. With no schedule it says nothing is scheduled right now; if Twitch can't be asked, a command says so and a timer stays quiet that time. It needs no Discord server. See Commands.

Open the Together tab in the streamer area. It changes nothing: for your channel, and for each server your linked Discord account manages whose main Twitch channel is yours or that gets your events, it shows what is set up and what is stuck, with a link to where each problem is fixed. A server is shown only if your linked account manages it, which Discord is asked each time, and Find my servers looks through every server TrinketBot is in. A grey row is something switched off, which is a choice. A green row means the saved settings and permissions are in place, not that Twitch is delivering events. See the guide.

The Overview of the streamer area has a Needs attention box at the top. For what you have switched on, it lists events set to post in Discord with no channel chosen or in one TrinketBot can't post in, events Twitch hasn't been given permission for, a web address that is missing or failing, the bot not being a moderator when filters or moderator commands are on, commands and timers paused over your plan, and the notes the bot stored. Each line says where to fix it, and a problem only TrinketBot's owner can fix points to the Support server. Check again looks now. It doesn't cover what a server does for your channel (the Check tab of the Connect page does) and it can't see whether Twitch is delivering events. See the documentation.

It chats as one Twitch account of its own, named on your Overview page (type /mod and its name in your chat to make it a moderator). To remove it, turn it off on the Overview, remove TrinketBot in Twitch's Settings → Connections, or delete your channel account.

One independent developer — see About. There is no team behind it: it's built, run and supported by one person. That means updates arrive in bursts rather than on a fixed schedule — but it's under active development, and the status page is always public.

The idea for TrinketBot goes back to 2025, but it sat untouched for a while. Development properly kicked off around September 2026, when the project got picked back up and actually built out.

It's under active, ongoing development. One person works on it, which means updates come in bursts rather than a fixed schedule — but new features and fixes are shipping regularly.

Only time will tell exactly what's next — but there's plenty more planned. Don't worry, you won't be missing out on anything in the meantime.

Not right now — the source is being kept private, since TrinketBot is part of the developer's personal portfolio.

Check the live status page for current uptime, incident history, and response times across every part of the bot.

A Node.js/discord.js bot backed by PostgreSQL, with a Next.js dashboard for setup — no config files or slash-command hunting required for anything the dashboard covers.