Triggers

Triggers define when an action fires. Every action needs at least one trigger, and you can attach multiple triggers to the same action.

Trigger Events

Nexmod supports 15 trigger events covering chat, channel events, stream state, and external sources.

Chat

Event	Description	Configuration
Chat Message	Fires when a message is sent in chat. Optionally filter by a message pattern.	`messagePattern` — glob-style pattern (e.g., `!hello *`)

Channel Events

Event	Description	Configuration
Follow	A new viewer follows the channel.	—
Subscription	A viewer subscribes or resubscribes.	`tierFilter` — Filter by tier: Any, Tier 1, Tier 2, or Tier 3
Cheer / Bits	A viewer cheers with bits.	`minimumBits` — Minimum bits to trigger (default: 1)
Raid	Another streamer raids your channel.	`minimumViewers` — Minimum raid size to trigger (default: 1)
Channel Point Redemption	A viewer redeems a channel point reward.	`rewardName` — The specific reward name to match

Moderation Events

Event	Description	Configuration
Ban	A user is banned from the channel.	—
Timeout	A user is timed out.	—

Stream State

Event	Description	Configuration
Stream Online	The stream goes live.	—
Stream Offline	The stream ends.	—
Category Change	The stream category/game is changed.	—

Twitch Interactive

Event	Description	Configuration
Poll End	A Twitch poll finishes.	—
Prediction Resolve	A Twitch prediction is resolved.	—

Timers & External

Event	Description	Configuration
Timer Tick	Fires on a recurring schedule from a configured timer.	`timerName` — The timer to listen for
Custom Webhook	Fires when an external service sends data to a Nexmod webhook endpoint.	`webhookPath` — The path for the inbound webhook

Trigger Types

Each trigger has a type that controls how it behaves in the dashboard UI:

Type	Description
Basic	A simple on/off trigger — fires whenever the event occurs.
Toggle	Acts as a toggle switch (on/off state).
Range	Fires within a numeric range (e.g., bits between 100–500).
Select	Fires for a selected option from a list (e.g., specific reward name).
Text	Fires based on text matching (e.g., message pattern).

Multiple Triggers

A single action can have multiple triggers. This is useful when you want the same automation to run for different events.

Example: A “Welcome Alert” action with two triggers:

Follow — Fire when someone follows
Subscription — Fire when someone subscribes

Both events run the same sub-actions (send a chat message, trigger an OBS scene change, etc.).

Event Data

When a trigger fires, it provides event context that sub-actions can reference. The data available depends on the event type:

Follow Event Data

Field	Description
`userName`	The follower’s username
`userDisplayName`	The follower’s display name
`userId`	The follower’s Twitch user ID

Subscription Event Data

Field	Description
`userName`	The subscriber’s username
`userDisplayName`	The subscriber’s display name
`userId`	The subscriber’s Twitch user ID
`tier`	Subscription tier (`1000`, `2000`, or `3000`)
`isGift`	Whether the sub was gifted

Cheer Event Data

Field	Description
`userName`	The cheerer’s username
`userDisplayName`	The cheerer’s display name
`userId`	The cheerer’s Twitch user ID
`bits`	Number of bits cheered
`message`	The cheer message

Raid Event Data

Field	Description
`raidingBroadcasterName`	The raider’s username
`raidingBroadcasterDisplayName`	The raider’s display name
`viewers`	Number of viewers in the raid

Stream Online / Offline Event Data

Field	Description
`broadcasterName`	The broadcaster’s username
`broadcasterDisplayName`	The broadcaster’s display name

Use event data in your sub-action messages and templates. For example, a follow trigger can use the follower’s display name in a “Send Message” sub-action.