Docs

Understanding Behaviors

Every feature on your bot is a behavior. The Bot Builder writes them when you describe what you want; Templates install ready-made ones. Here is what a behavior is and how to manage yours.

What is a Behavior?

A behavior is a single unit of functionality in your bot. It pairs a trigger (what starts it) with one or more actions (what it does). Whether the Bot Builder wrote a feature or a template installed it, it lands in your bot as a behavior, in the same list, with the same on/off switch.

Where Behaviors Come From

The Bot Builder

Describe the feature in plain English. The builder picks the trigger, writes the action as code, tests it on your bot, and publishes it. You never see the code — you see the behavior it produced.

Using the Bot Builder

Templates

Ready-made behaviors for common features — welcome messages, reaction roles, tickets, leveling. You fill in a short form (which channel, which role) and the template installs a behavior with preset actions. Templates never spend credits.

Using Templates

Anatomy of a Behavior

Trigger

The condition that activates the behavior

Example: When someone joins the server

Actions

What the bot does when triggered

Examples:
  • Send message to #welcome
  • Give @Member role

Trigger Types

You do not pick these by hand. The builder chooses the trigger from what you describe — "when someone joins" becomes an event trigger, "a /rank command" becomes a command trigger. Knowing the types helps you describe features precisely.

Event Triggers

Triggered by Discord events like member joins, leaves, bans, etc.

• Member Join
• Member Leave
• Member Ban
• Member Update
• Role Create/Delete
• Channel Create/Delete

Command Triggers

Fires when a user runs a slash command.

Slash Commands: /kick, /ban, /help
Context Menus: right-click a user or message

Message Triggers

Triggered when a message matches certain conditions.

• Contains word
• Exact match
• Starts with
• Regular expression
😀

Reaction & Component Triggers

Triggered when users react to messages, or click a button, pick from a select menu, or submit a form the bot posted.

• Reaction Added
• Reaction Removed
• Button / Select / Modal

Scheduled Triggers

Runs on a timer with no user involved — a daily announcement, a periodic report, a channel that refreshes a member count.

• Cron schedule (with a timezone)
• Fixed interval

Action Types

Templates use these preset actions. The builder usually writes its actions as Custom Code instead — code that does exactly what you asked, including things no preset covers.

Messages
  • Send Message
  • Send Embed
  • Edit Message
  • DM User
Roles
  • Add Role
  • Remove Role
  • Set Nickname
Moderation
  • Kick User
  • Ban User
  • Timeout User
  • Delete Message
Channels
  • Create Channel
  • Delete Channel
  • Lock / Unlock Channel
  • Set Slowmode
Threads & Pins
  • Create Thread
  • Pin Message
  • Add Reaction
Advanced
  • Call AI
  • Generate Image
  • Custom Code

Example: Welcome Behavior

Ask the builder for "When someone joins, send 'Welcome [username]!' to #welcome and give them the @Member role", or install the Welcome template. Either way, this is the behavior your bot ends up with:

TRIGGERMember Join Event

When a new member joins the server

ACTIONSWhat happens next
1

Send Message

Channel: #welcome

Content: "Welcome {username}! Glad to have you."

2

Add Role

Role: @Member

Target: The user who joined

Managing Behaviors

Your bot's page lists every behavior. Each one has an on/off switch, and its menu offers:

  • View Details: see the trigger and what the behavior does
  • Edit in chat: hands the behavior to the Bot Builder with "Edit <name>:" ready in the composer — finish the sentence and send. This is how you change anything the builder wrote.
  • Open settings: for a template behavior, reopens the template's form so you can change the channel, role, or message without credits
  • Settings: some builder-written behaviors expose their own knobs — cooldowns, channels, messages — in a form
  • Delete: removes the behavior. You are shown first which stored data it used and what stays because other behaviors still use it.

Drag a behavior to reorder the list. Turning one off keeps it for later without deleting it.

Changing a behavior is a conversation
There is no form for editing a trigger or an action by hand. Tell the builder what should be different — "make the welcome message also mention the rules channel" — and it changes the behavior and publishes it. It remembers what it built, so you do not need to explain the feature again.

Overview Tab

Track all your bot's features

The Overview tab lists your commands, event listeners, message triggers, and scheduled tasks, grouped by trigger type.

What it does:
  • • View every command in one list
  • • Copy a command name with one click
  • • See event listeners and triggers
  • • Filter by search query
  • • Show or hide disabled behaviors
Categories:
  • • 🔵 Commands (/help, /ban, etc.)
  • • 🟣 Event listeners (joins, leaves)
  • • 🟢 Message triggers (keywords)
  • • 🟠 Reaction triggers (role menus)
  • • 🔷 Scheduled tasks (cron jobs)

Want a /help Command?

Ask the builder. It reads your bot's existing commands and writes a /help command that lists them in an embed. After you add more commands, ask it to update the list.

Add a /help command that lists all my bot's commands with their descriptions in an embed
Using TemplatesTriggers & Actions Reference