Multi-Action Requests

A multi-action request is a single message that asks ReactionBot to perform more than one supported action.

For example: “Block the fire emoji and limit members to one reaction per message in this channel.”

ReactionBot identifies each instruction separately and attempts to perform the matching actions.

Your message can include normal conversation alongside a supported ReactionBot action.

For example: “What’s up? Block the puke emoji in this channel.”

ReactionBot can respond to the conversational part while also processing the request to block the emoji.

Example: “Block 🔥 and 😂 in this channel.”

Example: “Unblock the fire emoji and limit everyone to two reactions per message.”

Example: “Only allow 👍 and 👎 here, then restrict @User from reacting for one hour.”

Example: “Say hello, block the puke emoji, and remove its existing reactions from today.”

ReactionBot analyzes the message and separates it into individual actions before attempting to perform them.

Each action keeps its own details, including the emoji, member, channel, duration, date range, and intended scope.

Clear punctuation and direct wording can make complex requests easier to interpret.

Every action in the request is checked independently before it is performed.

ReactionBot verifies the requesting user's permissions, the bot's permissions, feature availability, Premium requirements, and any required role hierarchy.

Passing validation for one action does not automatically allow every other action in the message.

A multi-action request may be partially completed when one action succeeds and another cannot be performed.

For example, a channel-based block may succeed while a server-wide reaction limit fails because the server does not have Premium.

ReactionBot's response should show which actions were completed and which actions were unsuccessful.

You can apply the same scope to multiple actions by clearly stating it in the request.

For example: “In this channel, block 🔥 and limit everyone to one reaction per message.”

When different actions require different scopes, describe the scope of each action separately.

A single request can describe channel-based and server-wide actions, but the wording must make the intended scope clear.

For example: “Block 🔥 in this channel, but block 😂 across the entire server.”

Server-wide actions remain subject to the Premium requirements of the equivalent ReactionBot feature.

Each instruction should include enough information for ReactionBot to understand what should be changed.

For example: “Restrict @User” identifies the member but may still be missing the scope or duration.

A clearer request would be: “Restrict @User from reacting in this channel for two hours, and block 🔥 here.”

ReactionBot generally processes actions in the order they are understood from the message.

However, you should not rely on complex dependencies between actions unless the intended order is stated clearly.

Use wording such as “first,” “then,” or “after that” when the sequence matters.

Some instructions may depend on an earlier action being completed successfully.

For example: “Unblock 🔥, then make it the only allowed reaction in this channel.”

If the first action fails, ReactionBot may still evaluate the second action independently, so always review the final response.

ReactionBot can handle multiple actions, but extremely long messages with many members, emojis, scopes, and conditions may become unclear.

For the most reliable results, group related actions together and split unrelated changes into separate requests.

The dashboard or standard slash commands may be better for large configuration changes requiring exact control.

A multi-action message is submitted as one AI request, even when ReactionBot identifies more than one supported instruction inside it.

The actions performed through that request remain subject to their normal Free, Premium, permission, and feature requirements.

Combining related actions can be a convenient way to manage several settings in one conversation.

After submitting a multi-action request, read the entire response rather than assuming every action succeeded.

Confirm that the correct emojis, members, channels, durations, scopes, and settings were used.

If one action failed, you can resend only that instruction with the missing or corrected details.

Continue to AI Access & Requests to learn how AI access, request balances, activation, and server assignments work.