Automation Rules
A rule reacts to something happening in your server without anyone lifting a finger. It reads the same way every time: when a trigger fires, only if the conditions match, then run an action.
Where it lives
Rules are under Automations → Rules in the dashboard sidebar, next to Flows, Connections and Activity Logs. You need a Manager role (the Manage Automations permission) to open them.
Triggers
A rule starts from one of three sources.
When something happens in a ticket
Ticket events, messages, inactivity timers and member joins on every plan, plus in-game reports from your game server on Community and Pro.
When a connected app sends an event
A connected app such as Whop or Stripe sends an event, like a new member or a failed payment.
On a schedule
Run a flow or post in a channel on a repeating or one-time schedule, with no ticket involved.
The ticket triggers are grouped in the builder the same way as below. Any of them can be limited to one category.
Ticket events
| Trigger | Runs when |
|---|---|
| When a ticket is created | Once, as soon as the ticket channel exists |
| When staff first reply | On the first staff reply only |
| When a customer first replies | On the customer's first message only. Pair it with Reply with an AI response to greet a new ticket, or use the one-click first-reply toggle on AI Control |
| When a ticket is claimed | A staff member claims the ticket |
| When a ticket is closed | The ticket closes, however it was closed: staff, the customer, or another rule |
| When the creator leaves the server | The person who opened the ticket leaves |
| When a rating is submitted | The customer leaves a rating |
| When the priority changes | Every priority change, in either direction |
Messages and time
| Trigger | Runs when |
|---|---|
| When a customer sends a message | On each message the customer sends. Staff messages are ignored |
| When staff send a message | On each message your team sends. Customer messages and the bot's own replies are ignored |
| After customer inactivity | Staff replied last and the customer has not answered for the set time |
| After staff inactivity | The customer posted last and staff have not answered for the set time |
| After no activity from either side | Nobody has posted for the set time, whoever's turn it is |
| After a ticket has been open | The set time has passed since the ticket opened, whatever has been said since |
The four timers take a number of minutes, with presets for 1, 6, 12 and 24 hours.
Inactivity follows whose turn it is
A customer who answered and is now waiting on you is never "inactive", so an auto-close on After customer inactivity cannot shut a ticket out from under them. Tickets both sides dropped are what After no activity from either side is for: pair a long threshold on it with a shorter customer inactivity rule.
Run mode
The two message triggers and the four timers let you choose Once per ticket or Every time. Every time runs on each message, or once per inactivity cycle for a timer. It is only offered for actions that make sense more than once: running a flow, sending a message, sending to a channel and an AI reply. Every other trigger runs once per ticket, apart from When the priority changes, which runs on every change.
Message rules set to Every time can also take a cooldown per ticket of up to a day: after the rule runs, it waits that long before it can run again in the same ticket. Rules on the message triggers ignore other bots unless you turn on Also run on other bots' messages; the bot's own messages never count.
Members
When a member joins the server opens a welcome ticket for the new member. Set the action to Open a ticket and pick a category; the ticket is owned by the member who joined. Greet them with the category's intro message, or pair it with a When a ticket is created rule for anything more involved. Bot accounts are ignored, and no new welcome ticket opens while the member still has one open in that category. Member-join rules don't take conditions.
Game servers
When a player sends a report in game opens a ticket when a player uses the report command on your game server (/report by default). It needs a game server plugin with reports turned on in its config, and works on Community and Pro. Set the action to Open a ticket and pick a category. The ticket is owned by the player's linked Discord account, or by the bot when they haven't linked one, and the report is posted in it with the player, the reported player and the game server. When the player already has an open ticket in that category, the report is posted there instead of opening another. Report rules don't take conditions.
Triggers your plan doesn't include
Every trigger is listed on every plan, so you can see what's possible. Ones your plan doesn't include carry a Community or Pro badge: you can pick them to read what they do, and the rule shows how to unlock them instead of letting you save it. Under When a connected app sends an event, every app is listed. On Pro, an app you haven't connected yet still shows its events, with a link to connect it.
Connected apps
Connect an app on the Connections page first, then pick it when you build the rule. The events come from that app; see Inbound Triggers for the list per app.
Schedules
A scheduled rule runs with no ticket in scope. Choose Repeating (every day, weekdays, weekly on the days you pick, or an advanced cron expression) at a time of day, or One time at a date and time. Both run in the timezone you select. A scheduled rule can Run an automation flow, Send a message to a channel or Do something in a connected app, and its only condition is Business hours.
Conditions
Conditions are optional. Leave them empty and the rule runs every time the trigger fires. Add one or more to narrow it down, then choose whether all of them or any of them must match.
Ticket-event rules check the ticket:
| Condition | Checks |
|---|---|
| Message contains | The message that fired the rule, against a keyword list. Message triggers only |
| Ticket content contains | What the member opened the ticket with: their form answers and first message |
| Ticket age (hours) | How long the ticket has been open, compared with >, >=, <, <= or = |
| Message count | The number of messages in the ticket, with the same comparisons |
| Rating value | The rating the customer gave, with the same comparisons |
| Priority is | Low, Normal, High or Urgent |
| Business hours | During or outside the hours set under Settings → Hours |
| Staff has replied | Whether any staff member has replied yet |
| Ticket is claimed | Whether the ticket is claimed |
| Message author | Whether the message was sent by the person who opened the ticket. Message triggers only |
Connected-app rules check the event payload instead: a path such as data.status that equals, does not equal, contains, or is present.
Hand over to a person
A rule that replies with AI keeps replying after your team joins. Add Staff has replied set to No staff member has replied yet so it goes quiet once someone picks the ticket up.
Message conditions need a trigger that carries a message
Message contains and Message author are only offered on the four triggers that fire with a message in hand: a customer sends a message, staff send a message, a customer first replies, and staff first reply. Anywhere else there is no message to read, so the condition could never match and saving is refused. To match on wording elsewhere, use Ticket content contains.
Matching keywords
A Message contains condition takes a list of keywords. It matches when any one of them appears, and capital letters never matter. Pick how each keyword has to appear:
| Match | Matches when | refund matches | refund does not match |
|---|---|---|---|
| Whole word | The keyword appears as its own word | "Can I get a refund?" | "Refunds are slow" |
| Anywhere in the text | The keyword appears anywhere | "This is non-refundable" | "I want my money back" |
| Whole message | The message is only the keyword | "refund" | "refund please" |
Keywords are plain text, so characters like + or . match themselves. In languages written without spaces between words, such as Chinese, Japanese, or Thai, a whole-word keyword matches anywhere in the text.
Keyword auto-replies
A keyword auto-reply answers common questions as soon as someone asks them. Click Keyword auto-reply next to New rule to start from a rule that is already set up for it, then fill in:
- Keywords: the words to watch for, such as
refund,chargeback, andmoney back. - Reply: the message to post. It supports placeholders like
{user.mention}. - Who it answers: anyone in the ticket except staff, or only the person who opened it. Staff messages never trigger it.
- Cooldown: how long the rule waits before it can answer again in the same ticket, up to a day. If the reply can't be posted, for example because the bot lost access to the channel, the cooldown doesn't start, so the next matching message tries again.
The reply is posted as a Discord reply to the message that triggered it, so it is clear what it answers. You can turn that off under Reply to the message that triggered it.
Example: point refund questions at the policy
Keywords refund, chargeback, money back, matched as whole words. Reply:
Hi {user.mention}, refunds are covered in #refund-policy. A team member will confirm the details here. Answers anyone except staff, with a 1 hour
cooldown. Someone writing "can I get a refund?" gets the reply once, and the
rule stays quiet in that ticket for the next hour.
Keyword auto-replies are ordinary rules: they work on every plan and count toward the same rule limit. The bot never replies to its own messages, so two auto-replies can't set each other off.
Mention a user or role in an automatic reply
There are two ways to do this:
- In a rule: use Send a message and put
{user.mention}in the message to ping the ticket opener. To ping a fixed role, paste Discord's role mention syntax,<@&ROLE_ID>, replacingROLE_IDwith the role's numeric ID. A role name such as@Supportis only text; it does not identify the role reliably. - In a flow: add a Mention node and select the user or role with its picker. Use a Send Message node as well if the ping needs explanatory text. An automation rule can start that flow with Run an automation flow.
To copy a role ID, turn on Discord Developer Mode, right-click the role and choose Copy Role ID. Make sure Ticket Tool can mention the role in Discord; otherwise the name appears without notifying anyone. See Finding Discord IDs and the variables reference for other user placeholders.
Actions
| Action | What it does |
|---|---|
| Run an automation flow | Runs one of your support flows for anything with branches, inputs or several steps |
| Send a message | Posts a message in the ticket. On a connected-app rule it posts in a channel you pick |
| Send a message to a channel | Posts in a different channel, such as a staff log. Nothing is posted in the ticket |
| Close the ticket | Closes the ticket, with an optional close reason. On a GitHub or Linear rule it closes the linked ticket |
| Post in the linked ticket | Posts the event in the open ticket whose flow created the issue it is about. GitHub and Linear rules only |
| Do something in a connected app | Pro. Runs one action in a connected app, such as commenting on an issue, without building a flow |
| Move to another category | Moves the ticket into another category |
| Open a ticket | Opens a new ticket. Connected-app and member-join rules only |
| Reply with an AI response | Pro. Posts an AI answer to the customer in the ticket |
| Stop automations on the ticket | Exempts the ticket from every rule. See Exempting a single ticket |
| Let automations run again | Ends a pause early. The only action that still runs on a paused ticket |
Not every action fits every trigger. Member-join and in-game report rules only open a ticket. Ticket-event rules can use everything except Open a ticket and the linked-ticket actions, and staff-message rules also leave out the AI reply and the two pause actions. Connected-app rules can open a ticket, send a message, run a flow or do something in a connected app, and on GitHub and Linear issue events they can also post in or close the linked ticket. Scheduled rules can run a flow, send to a channel or do something in a connected app.
Do something in a connected app offers the same actions as a flow's Integration node, and its fields take the same variables: ticket variables such as {{ticket.number}} on ticket-event rules, and {{inputs.<label>}} for the fields you map on connected-app rules. With a game server plugin connected, it also offers Game server actions that message, warn, kick or unban the ticket's opener in game; see staff actions.
Reply with an AI response answers from your knowledge base and approved memory using the settings on AI Control, and spends your AI tokens. It waits for the customer to stop typing, so a burst of messages gets one reply. You can choose who sees the 👍 / 👎 feedback buttons under the reply, or keep the server default. See AI Assist for how grounding works.
For connected-app rules you can also map payload fields onto the message or ticket. Each mapping is a label plus a path, so "Plan" with path data.plan shows up as "Plan: Pro".
Exempting a single ticket
Rules apply to every ticket in scope, which is a problem when one ticket needs to be left alone: a reference thread you keep around, or one that is waiting on someone outside your team. Staff can pause it with /pause in its channel, or from the Automations section of the ticket sidebar in the dashboard, for 1 hour, 1 day, 1 week, or indefinitely.
While a ticket is paused, no rule touches it: no auto-close, no inactivity reminder, and no rule reacting to a message or a rating. Staff can still close, claim and reply to it by hand. The bot pins a notice in the channel for as long as the pause lasts; without the Pin Messages permission the pause still works and only the notice is skipped.
To hold back one rule and leave the rest running, pick it in /pause rule:. /resume rule: turns it back on. A single-rule pause posts no notice.
Automations can pause a ticket too, with the Stop automations on the ticket action or the Pause Automations flow node. Both take a custom length as well as the presets, so a rule can pause for 45 days if that is what you need.
When a pause ends, whether it lapses or someone runs /resume, any inactivity clock restarts from that moment. A ticket paused for a week past a 72-hour rule is not closed the second the pause lapses; it gets the full window again.
Ordering, limits and the log
Use the up and down arrows on the Rules page to reorder ticket rules, and the switch on each rule to turn it off without deleting it. Rules that share a trigger run one at a time, from the top of the list down, and once one closes the ticket the rest are skipped. A new rule goes to the bottom.
A rule limited to one category counts toward that category's rule limit, which is 5 on Free, Unlimited on Community and Unlimited on Pro.
Every run is recorded under Automations → Activity Logs as ran, skipped or error, and the latest result shows on each rule in the list. A skipped run usually means the conditions did not match, and an error shows what went wrong.
Related
- Inbound Triggers: connected-app events in depth
- Support Flows: multi-step automation
- Automate the boring parts: auto-close, reminders and auto-replies set up step by step
- AI Control: the first-reply toggle, AI settings and usage