Auto Responder
Make Cakey Bot reply on its own when a message matches a trigger you set.
Overview
Auto Responder lets you set up custom triggers on Discord that Cakey Bot answers automatically. For example, you can make Cakey Bot reply to messages such as wot with a link to a funny gif. You can also set flags to decide which types of messages Cakey Bot replies to.
Setup
You need the Manage Server or Administrator permission to manage servers and auto responders.
You can also give specific users or roles dashboard access without Manage Server or Administrator. See Dashboard Access for details.
- Log in to the web dashboard on the main website here.
- Click the server you want to edit auto responders for.
- Go to the "Auto Responder" page.
- Create, delete and edit responses on this page. The flags you can use are listed below.
Flags
Only one auto responder triggers on a given message, even if the message meets the requirements of several. The matching responder with the lowest ID is the one that triggers.
| Flag Type | Description | File Extensions |
|---|---|---|
| Exact Match | Default behavior, looks for exact match strings | - |
| Contains | Searches the entire message for this string/trigger | - |
| Starts With | Checks whether the message begins with this string/trigger | - |
| Ends With | Checks whether the message ends with this string/trigger | - |
| Contains Files | Checks whether the message contains any files/attachments (i.e. documents, images, videos) | - |
| From Webhook | Checks whether the message was sent by a webhook | - |
| Contains user mention | Checks whether the message contains a user mention | - |
| Contains channel mention | Checks whether the message contains a channel mention | - |
| Contains role mention | Checks whether the message contains a role mention | - |
| Wildcard Contains | Searches message with wildcard support: * (any chars), ? (single char), use \? for literal question marks |
- |
| Regex Match | A more powerful version of wildcard, allows full regular expressions | - |
| Contains image attachment | Checks if attachments include image formats | .jpg, .jpeg, .png, .gif, .bmp, .tiff, .ico, .svg, .webp, .heic, .heif, .jfif, .exif, .raw, .psd, .ai, .eps |
| Contains video attachment | Checks if attachments include video formats | .mp4, .avi, .mkv, .mov, .wmv, .flv, .webm, .m4v, .mpeg, .mpg, .3gp, .rm, .swf, .vob, .ts |
| Contains audio attachment | Checks if attachments include audio formats | .mp3, .wav, .flac, .aac, .m4a, .wma, .ogg, .alac, .aiff, .opus, .mid, .midi, .amr, .ape |
| Contains text attachment | Checks if attachments include document/text formats | .txt, .csv, .json, .xml, .html, .htm, .md, .log, .rtf, .doc, .docx, .pdf |
| Contains executable attachment | Checks if attachments include executable formats | .exe, .msi, .bat, .sh, .app, .jar, .com, .cmd, .vb, .vbs, .ps1 |
| Contains sticker | Checks whether the message has a sticker. Any sticker counts, including ones from other servers | - |
Note: The "Command" field is still required for "Contains Files", "From Webhook", the "Contains X mention" flags and "Contains sticker". It is not used to trigger the auto response. It is purely cosmetic.
Regex Match Triggers
Every message sent in your server is checked against every regex trigger you have, so each one gets a strict time budget to match in. A pattern that takes too long is abandoned.
If a regex trigger repeatedly runs out of time, Cakey Bot disables that auto responder automatically so it does not slow down every message in the server. You will find it toggled off on the dashboard. Fix the pattern and re-enable it.
The usual cause is a pattern that isn't anchored. Without ^, the engine doesn't read the message once. It starts over from every single character in it, so a 200 character message is scanned 200 times instead of once, and that cost climbs sharply on longer messages.
Anchoring the pattern with ^ tells it to try once, from the start:
| Pattern | |
|---|---|
| Slow | (?i)(?=.*\bhello\b)(?=.*\b(help\|support)\b).* |
| Fast | (?si)^(?=.*\bhello\b)(?=.*\b(?:help\|support)\b).* |
Both match the same messages. The differences that matter:
^anchors it, so the message is read once instead of once per character. This is the important one.smakes.match newlines too. Without it an anchored pattern only ever sees the first line of a multi-line message.(?:...)makes the group non-capturing, so the engine isn't storing text you never use.
Patterns are matched case-insensitively already, so you don't need (?i). Avoid [\s\S] and other constructs that rely on an uppercase letter, since patterns are lowercased before they run and [\s\S] would become [\s\s], which only matches whitespace. Use the s flag instead.
Shortening your list of words is rarely the fix. Alternation over a dozen short words costs almost nothing next to an unanchored scan.
Permissions
Every auto responder has an optional Permissions section, collapsed by default, in its create/edit/clone form on the web dashboard. Use it to restrict who can trigger a response and where, without writing anything into the response text.
| Selector | Effect |
|---|---|
| Required Roles | The member must hold any of the selected roles to trigger this response. |
| Excluded Roles | A member holding any of the selected roles is blocked from triggering this response. |
| Required Channels | The response can only trigger in one of the selected channels. |
| Excluded Channels | The response is blocked in the selected channels. |
| Required Users | Only the selected users can trigger this response. |
| Excluded Users | The selected users are blocked from triggering this response. |
Leave a selector empty to skip that restriction. All six selectors are independent. For example, you can combine a Required Role with an Excluded Channel on the same response.
Required and Excluded checks for the same category (e.g. Required Roles and Excluded Roles) are both evaluated. A member can satisfy a Required Role while also holding an Excluded Role, and in that case the exclusion still blocks the response.
This replaces the old {require:}/{not:} text placeholders. They are no longer supported, and existing auto responders that used them were migrated to the new Permissions selectors automatically.
Limitations/Restrictions
- You can't have duplicate tags with the same name
- Auto Responders are also limited to Discord's message character limit
- Messages sent by bots or webhooks will be ignored
- Non-Premium servers are limited to 100 auto responders. Premium servers have no cap on the number of auto responders.
- Regex triggers that repeatedly take too long to match are disabled automatically. See Regex Match Triggers.
Placeholders/Variables
Auto Responder works with BOTH Basic Placeholders and Advanced Placeholders. You can put placeholders in the response section to change the behavior or output of the response. The list of supported placeholders is here.
Using Emoji/Emotes in Responses
You can use emoji and emotes in auto responders, but it takes a little more work because of how Discord parses emotes. In Discord you can normally type :lel: or :smile: to get an emote. In Cakey Bot, neither of these works. To get a valid emoji, send the emoji in Discord with a backslash in front of it to get the emote's full ID. Like so: \:lel: or \:smile:, which produce these results: <:lel:408424717217693717> or, for Unicode emoji, 😄 . Once you have the full emoji ID or the raw Unicode output, paste it into Cakey Bot's web dashboard. It works as long as Cakey Bot is in a server that has that custom emote.
Cakey Bot can use emojis across servers. If you have an emoji in Server #1, you can use it in a response for Server #2 if Cakey Bot is in both servers.
Using Images in Responses
To use an image in a response, type the image URL/link as you would in a normal message. If the file is on your local machine and has no URL, upload it to an image hosting website (such as Imgur) and paste the URL they give you into the response. Cakey Bot embeds the image in Discord's client if it's a valid URL/image.
Custom Embeds Premium Only
You can add an optional embed to responses by following the steps below:
- Follow the instructions at the top of this page to sign in to the dashboard.
- Open the Embed Editor and design your embed.
- Click Save (or Save As New) and give it a name.
- Create an auto responder as you normally would, then select your saved embed from the Custom Embed dropdown.
Custom embeds work with all Basic Placeholders. The list of supported placeholders is here. Custom embeds do NOT work with the Advanced Placeholders.
Bulk Import/Export
You must apply through a support ticket to get access to Bulk Import. Anyone can use Bulk Export without applying. This limits potential abuse.
Limitations/Guidelines
- File MUST be in CSV format.
- File MUST be formatted with all of the required columns.
- Additional/extra columns will be ignored.
- Any fields that have too many characters will be trimmed. Column limits:
- Command: 200 characters
- Response: 2,000 characters
- Any fields that exceed the character limit will NOT work after importing.
- Bulk importing can NOT be canceled or reversed once started.
- Any broken commands will have to be individually deleted or fixed after the import is finished.
- There is a limit of 500 commands per bulk import.
What do the columns/fields and their values mean?
The template CSV file and bulk exported CSVs have several columns with various restrictions. These are explained below:
Status
- This determines whether or not the command/response is "enabled" or "disabled"
- Acceptable values:
- 0 - Disabled
- 1 - Enabled
Command
- This is the command/trigger phrase for a response.
- It must be less than 200 characters.
Flags
These are only used for Auto Responders, they map directly to the Auto Responder flags.
Acceptable values:
Value Flag Name 1 Exact Match 2 Contains 3 Starts With 4 Ends With 5 Contains Files 6 From Webhook 7 Contains user mention 8 Contains channel mention 9 Contains role mention 10 Wildcard Contains 11 Regex Match 12 Contains image attachment 13 Contains video attachment 14 Contains audio attachment 15 Contains text attachment 16 Contains executable attachment 17 Contains sticker
Response
- This is the response phrase for a trigger/command.
- It must be less than 2,000 characters.
Embed
- This is an optional field for responses that use a Cakey Bot custom embed. Embeds can only be used by Premium Servers regardless of whether a value is set here.
- This must be the numeric ID of an embed already saved for this server in the Embed Editor. You can find a saved embed's ID in the Custom Embed dropdown. Leave blank for no embed.
RequiredRoles / ExcludedRoles / RequiredChannels / ExcludedChannels / RequiredUsers / ExcludedUsers
- These are all optional and correspond directly to the Permissions selectors.
- Each field accepts a semicolon-separated (
;) list of Discord role, channel, or user IDs (matching the relevant field). Leave a field blank to skip that restriction. - Example:
237273200055156736;225182513465786369sets two required/excluded roles at once. - Older CSV files exported before the Permissions feature existed can still be imported. These columns are treated as blank (no restrictions).