Trigger Command Trigger

Starts a flow when a player (or console) runs a specific command.

Inputs: None · Outputs: Then

Description

The Command Trigger is the entry point for command-based flows. When a player types the configured command, execution begins and flows through the connected nodes.

Settings

Setting	Type	Required	Default	Description
Enabled	Boolean	No	true	Enable or disable this trigger. When deploying a previously-enabled command as disabled, it stays registered but can't be executed until the server restarts.
Command Name	String	Yes	—	The command name without the leading slash (e.g., spawn).
Aliases	String Array	No	—	Additional command names that trigger the same action.
Description	String	No	—	Description shown in the help menu.
Usage	String	No	—	Usage hint (e.g., /spawn [player]).
Permission	String	No	—	Permission node required to use this command (e.g., server.spawn).
No Permission Message	String	No	—	Message shown when the player lacks permission.
Cooldown (seconds)	Number	No	0	Cooldown between uses (0–3600 seconds).
Cooldown Message	String	No	—	Message shown when on cooldown. Use %cooldown_remaining% for the time left.
Who can execute?	Select	Yes	Player Only	Who can run this command: Player Only, Console Only, or Both.

Example

To create a /spawn command:

1. Set Command Name to spawn
2. Set Permission to server.spawn
3. Set No Permission Message to &cYou don't have permission!
4. Connect the Then output to a Teleport Player node set to World Spawn

Available Placeholders

When using a Command Trigger, the following command-specific placeholders become available:

• %command% — The command name
• %args% — All arguments as a string
• %args_count% — Number of arguments
• %arg_1% through %arg_n% — Individual arguments
• %subcommand% — The first argument (synonym for %arg_1%)