🧩 Action Builder and Action Sequences

The Action Builder tells SheevChat what to do when something happens. Use its search to find actions by name, description, category, or type instead of opening every category.

You can use it inside Custom Commands, Automations, Timers, and SheevPad buttons.

The Basics

Trigger: What starts the actions.

A viewer follows your channel.

Action: One thing SheevChat does.

Send a chat message.

Sequence: Multiple actions that run in numbered order.

1. Send a message
2. Pause for 10 seconds
3. Send another message

Variable: A placeholder replaced with real information.

Welcome, {user}!

If the viewer is named Alex, SheevChat sends Welcome, Alex!.

Adding an Action

1. Create or edit a Custom Command, Automation, Timer, or SheevPad button.
2. Scroll to Actions.
3. Choose an action category from the first menu.
4. Choose the action from the second menu.
5. Click Add action.
6. Complete the settings shown on the action card.
7. Save your work.

Creating a Sequence

Add more than one action to create a sequence. SheevChat runs the numbered cards from top to bottom.

For this example, create or edit an Automation:

1. Add Chat Bot Commands → Send chat message:

Time for a quick stretch!

1. Add Utilities → Pause / wait and set it to 10 seconds.
2. Add another Send chat message:

Welcome back! Remember to drink some water.

SheevChat sends the first message, waits 10 seconds, then sends the second message.

Use the ↑ and ↓ buttons on an action card to change its position. Use × to remove it.

Pause Versus Delayed Message

Pause / wait stops the entire sequence. Every later action waits for it to finish.

Send chat message (delayed) schedules only that message for later. The next action continues immediately.

Use Pause / wait when all following actions should wait. Use a delayed message when only one message should happen later.

When a sequence changes both a broadcast scene and Master Overlay, the overlay's Fade setting controls the visual blend; a Pause only delays later actions. Match the fade to the OBS or Streamlabs transition and make it slightly longer when independent action swimlanes do not start together. See How To Match Overlay Fades to Scene Transitions.

Using Variables

1. Click inside a supported message or text field.
2. Open Insert Variable.
3. Select the information you want to insert.

Not every trigger provides every variable. If an action displays a Needs warning, choose another variable or a trigger that provides it.

Choosing Where Messages Go

• Same platform as event replies where the event happened.
• All platforms sends to every connected platform.
• A named platform sends only there.

For most automations, Same platform as event is the safest choice.

For supported message-based triggers, choose Reply to triggering message where supported when the response should use native Twitch or Kick reply threading. Other platforms fall back to a normal message.

Supported replies include visible original-message context in SheevChat chat feeds and compatible Chat overlays.

Send Payloads to Overlay Widgets

The Send to Overlay category can send TTS, Media Library audio, alert data, or text payloads to Overlay Builder sources and widgets. Every active Overlay Builder source can receive TTS and audio through the global path, so new layouts do not require an Audio Receiver widget. Play Audio volume is set directly on its action; legacy receivers remain compatible for older channel-routing workflows.

Payload actions also support priority and expiration. Add and save a receiving widget before opening Action Builder when a widget-specific target is required. See How To Set Up Overlay Audio for OBS-routed speech and audio.

TikTok chat actions are explicitly opt-in and link-free. Use only the TikTok destinations and action types offered by the editor; existing all-platform items do not silently add TikTok.

Shared action families also include Create Twitch Clip, Windows audio controls, Set loyalty name, and Snooze upcoming Twitch ad. Their provider and operating-system requirements still apply. See How To Create Twitch Clips and How To Control Windows Audio with Actions.

Random-viewer variables such as {viewer.random:current} and {viewer.random:all} can be inserted into supported fields. See How To Select Random Viewers.

Testing Your Actions

1. Save your work.
2. Open Tests from the SheevChat header to simulate commands or events.
3. For SheevPad, use the editor's Test button.
4. Confirm the actions run once, in order, and on the correct platform.
5. Confirm variables are replaced instead of appearing as {variable}.

Overlay Builder actions can trigger a saved Alert Preset or change which saved layout the Master Overlay displays. Create the preset or overlay first so it appears in the action's picker.

Installed Marketplace apps can add their own action categories. Complete and test the app's connection under Marketplace → Installed Apps before using those actions.

Connect OBS under Settings → Connect, test OBS WebSocket, and select targets from its live scene/source catalog. See How To Connect and Control OBS Studio.

Streamlabs Desktop Control is separate from OBS Studio Control. Connect Streamlabs under Settings → Connect, refresh its live scene/source catalog, then select Streamlabs-specific targets in the action. See How To Connect and Control Streamlabs Desktop for linked-source versus exact scene-item visibility.

Interactive Overlay Builder packages may provide Overlay Widgets → Trigger Marketplace Widget. Select the Marketplace Item, enter the publisher's widget-action key, and provide optional payload JSON. The target widget must exist in a saved overlay.

Use SheevChat → UI Resizing to increase or decrease Chat, Events, Viewers, Sidebar, or all UI font sliders from a Command, Automation, Timer, or SheevPad button.

Common Mistakes

• Nothing happens: Make sure the item is enabled and saved.
• Wrong order: Move action cards with ↑ / ↓, then save again.
• Variable appears as text: The trigger may not provide it.
• Wrong chat: Check the action's Send to setting.
• Only the message waits: Use Pause / wait to delay later actions too.
• OBS, Streamlabs, or imported action fails: Test the matching connection under Settings or Marketplace → Installed Apps.
• Marketplace widget action fails: Confirm the target widget is saved and use the action key documented by its publisher.