Triggers
Every way an automation can fire, and how to pick the right one.
The When box decides what makes your automation post. Pick the mode first, because everything else in the builder adapts to it.
Which one do I want?
| I want to... | Use |
|---|---|
| Answer a question people ask in their own words | A message like this one |
Answer when someone mentions a word, like refund or store | Words in a message |
Give members a command like !poll or !suggest | A command |
| Match something very specific, like an invite link or an order number | A pattern |
| Turn a whole channel into a suggestion box or a showcase | Any message in a channel |
| Post a panel of buttons once and leave it there | You post it yourself |
| Thank someone for boosting, or for using your server tag | Someone boosts the server, Someone uses your server tag |
A message like this one
The default, and the one most automations want. For questions people ask in their own words, you type a sentence under The Message to Look For, and Tickety fires when someone says something similar enough.
- The Message to Look For:
how do i open a ticket - Fires on:
How do I open a ticket?,how to open ticket,how do i open tickets - Does not fire on:
where are the rules
The match percentage slider decides how close is close enough. 85 percent is a good starting point.
Lower it too far and unrelated messages start firing. If an automation answers things it should not, raise the percentage before anything else.
This mode can also read text out of images. See reading text in images below.
Words in a message
Add words or short phrases under The Words to Look For, pressing enter after each one. A message that has one of them as a whole word fires the automation, and capitals never matter.
- The Words to Look For:
refund,money back - Fires on:
How do I get a REFUND?,can I have my money back - Does not fire on:
I was refunded already
With two or more words, pick Any to fire on one of them or All to need every one.
This mode can also read text out of images. See reading text in images below.
A command
For anything shaped like a command. The message has to start with what you typed under The Command Members Type, and there is no guessing involved.
- The Command Members Type:
!poll - Fires on:
!poll,!poll should we do movie night - Does not fire on:
can we !poll this,poll
The word has to end where your trigger ends, so a trigger of !poll does not fire on !polling. If two commands overlap, the more specific one is used.
This is the mode to use with arguments. Commands that take a question, a list of choices or a user are where automations do the most.
Capitals have to match is off by default, so !Poll and !poll both work.
A pattern
For exact shapes rather than words: an order number, an invite link, a serial code. You write it under Trigger Pattern.
- Trigger Pattern:
discord\.gg/\w+ - Fires on: any message containing an invite link
The dashboard checks your pattern as you type and tells you if it cannot be used. Patterns that would match literally everything are rejected, because they would fire on every message in your server.
Any message in a channel
No text matching at all. Every message a member posts in the channels you pick fires the automation.
This is what a suggestion box is made of: someone posts an idea, and Tickety puts vote buttons under it.
Bots are ignored, and so is the automation's own output, so it cannot answer itself.
A channel you point an automation at belongs to that automation. A message there will not also be weighed against your other triggers, so a suggestion stays a suggestion even if it happens to look like an FAQ question.
Something that happens to a member
These fire without anyone typing, so they cannot reply in a channel. Send the message to a channel or to the member's DMs instead.
- Someone joins the server: a member arrives.
- Someone boosts the server: pick Roles to Give and Tickety gives them to every booster who does not have them yet, then runs the flow, including members who boosted before you set this up. With no roles picked, it runs once for each new boost.
- Someone uses your server tag: Tickety gives your Roles to Give to every member showing your server tag who does not have them yet, then runs the flow. Holding the role is how Tickety knows who already got it, so pick a role meant only for tag users. Pair it with Someone stops using your server tag to take the role back.
- Someone stops boosting and Someone stops using your server tag: Tickety takes the Roles to Take Back off a member who no longer boosts or shows your tag, then runs the flow. Anyone else holding those roles loses them too, so only pick the role your boost or tag automation gives.
- Someone gets a role and Someone loses a role: one of the roles you pick lands on a member or comes off them. Tickety needs the View Audit Log permission to see this.
- Your honeypot catches someone: runs after your honeypot has dealt with the account.
Bots never fire any of these.
You post it yourself
Nothing a member types fires this one. You write the message in the dashboard, press Send the Panel, and pick a channel. That posted message is the automation.
Use it for anything permanent: a self role picker, a rules panel with links, a vote that stays open.
Build the message and its buttons
Write it under Automation Reply and add your button groups in the Then box.
Send it
Press Send the Panel and choose a channel.
Edit it later
Save the automation and the posted message updates itself. You do not need to send it again.
Two things need a fresh send: moving the panel to another channel, and switching your reply between the embed style and the components style. Discord does not allow either on a message that is already posted. Sending again posts a new message, and any votes on the old one start over, because votes belong to the message they were cast on.
Options every trigger has
Reading text in images
OCR Trigger Detection reads the text inside an image and matches your trigger against it too, so a screenshot of an error still finds its answer.
It is available on Words in a message, A message like this one and A pattern only. Nobody types a command inside a screenshot, so it does not appear for command triggers.
OCR Trigger Detection uses AI Credits. See the plans page for how credits work.
Delete the member's message
Removes the message that fired the automation. Handy for command triggers, where the command itself is noise once Tickety has answered.
Conditions
Under Conditions you can narrow where an automation applies:
- Allowed channels: it only fires in these.
- Ignored channels: it never fires in these.
- Only inside tickets: it only fires in ticket channels.
- Required roles: only members with these roles can fire it, matching any of them or all of them.
Only one fires
One message fires at most one automation, so replies never stack up. More specific triggers win over looser ones: a channel you have dedicated to an automation takes priority, then commands and patterns, then words, and similar messages last.