Actions
Actions are the automation engine behind Nexmod. While commands respond to chat triggers with a single response or flow, actions are event-driven automations that can react to anything happening on your stream — follows, subscriptions, raids, timers, webhooks, and more.
Actions vs Commands
| Commands | Actions | |
|---|---|---|
| Triggered by | Chat messages matching a trigger word | Stream events, timers, webhooks, or other actions |
| Primary use | Chat interaction (!hello, !points) | Automations (follow alerts, sub reactions, timed messages) |
| Entry point | Start node | Event Trigger node |
| Flow builder | Available on Plus+ | Available on Plus+ |
| Sub-actions | N/A | Composable steps (send message, run command, HTTP request, etc.) |
Anatomy of an Action
Every action consists of three layers:
1. Triggers
What causes the action to fire. An action can have multiple triggers — for example, fire on both follows and subscriptions.
2. Sub-Actions
The steps that execute when the action fires. Sub-actions run in a configurable order and can include sending messages, setting variables, making HTTP requests, running commands, and more.
3. Execution Mode
How sub-actions are processed:
| Mode | Behavior |
|---|---|
| Sequential | Sub-actions run one after another, in order. Each waits for the previous to finish. |
| Concurrent | All sub-actions fire at the same time, in parallel. |
| Random | One sub-action is randomly picked and executed. |
Creating an Action
- Navigate to Actions in the dashboard sidebar
- Click Create Action
- Give it a name (e.g., “Follow Alert”)
- Add one or more triggers — the events that fire this action
- Add sub-actions — the steps to execute
- Save and enable
Properties
| Property | Description | Default |
|---|---|---|
| Name | A unique name for the action | Required |
| Enabled | Toggle the action on or off | true |
| Execution Mode | How sub-actions are processed (sequential, concurrent, or random) | Sequential |
| Always Run | If enabled, this action runs even when other actions are already processing | false |
| Group | Optional group name for organizing actions | null |
| Flow Data | Visual flow for advanced automation logic | null |
Action History
Every time an action runs, Nexmod logs the execution in Action History. The history records:
- Status — Whether the execution succeeded or failed
- Trigger event — What caused the action to fire
- Variable snapshots — The state of variables at execution time
- Errors — Any error messages if something went wrong
- Timestamps — When the action started and finished
Use action history to debug automations and verify they’re working as expected.
Action Queues
Actions can be assigned to queues that control how concurrent executions are handled:
| Queue Mode | Behavior |
|---|---|
| Blocking | Only one action runs at a time. Additional triggers queue up and wait. |
| Non-Blocking | Multiple instances of the action can run simultaneously. |
Queues are useful for actions that should not overlap, like playing a sound alert — you want one to finish before the next starts.
Dashboard Permissions
| Action | Required Permission |
|---|---|
| View actions | automations:read — Viewer and above |
| Create, edit, delete actions | automations:manage — Editor and above |
Moderators can read commands but cannot manage automations by default. Only Editors, Admins, and Owners can create and modify actions.
Plan Limits
| Plan | Max Actions | Flow Builder |
|---|---|---|
| Free | 3 | No |
| Plus | Unlimited | Yes |
| Pro | Unlimited | Yes |
| VIP | Unlimited | Yes |