How to automate buttons and select menus with GuildPilot

Interactive controls in Embeds and Smart Panels can run a short action sequence. You can reply, send content to a channel, manage a role or open a ticket while GuildPilot checks access and dependencies each time the control is used.

Warning: Role, channel and ticket actions affect the live server as soon as a member activates the control. Test with a designated account and disposable targets before publishing it widely.

Component automationIllustration

Before you start

Create an Embed or Smart Panel with a button or select menu. Prepare any destination channel, manageable role, saved design or ticket type the sequence will use; GuildPilot's role must sit above roles it manages.

Build an action sequence

1. Edit an interactive control

Open Messages → Embeds or Messages → Smart Panels, edit a button or select option, then choose Add action or Edit actions.

2. Add actions in execution order

Choose actions such as Reply with a message, Send a message to a channel, Add a role, Add a temporary role or Open a ticket. You can add up to five steps, and GuildPilot runs them from top to bottom.

3. Apply access and cooldown rules

Open Access and cooldown only when needed. Required and excluded roles apply to this control, while Per-member cooldown limits repeated use by the same member.

4. Review sequence rules and publish

Use only one direct reply. Put Open a ticket last; if that ticket opens a form, it must be the only action. Choose Use these actions, review the summary, then save and publish the parent design.

Recommended configuration

Keep the first version short. Add a private reply so members know whether the interaction succeeded, and use a cooldown for actions that could create repeated messages or tickets.

Test the setup

1. Use a non-staff test member with the intended roles. Activate the control once and confirm each action runs in order and the expected reply appears. Test a blocked role or cooldown when configured, then undo test roles, messages or tickets.

What a successful setup looks like

The control performs the saved sequence once, stops if a step fails, and gives the member a clear success or failure response without bypassing role, channel or hierarchy checks.

Common problems

A saved target is unavailable

Cause: A role, channel, saved design or ticket type was removed or is no longer usable.

Fix: Edit the action, choose a current target and publish the parent design again.

A ticket form will not follow another action

Cause: Discord cannot open that form after another interaction response.

Fix: Make the form-based ticket the only action in the sequence.