Server configuration | Messages

Auto Responder

Set up automated responses for specific keywords or phrases.


Note:

Slash commands for this page

Set this up in Discord with /configure feature:Autoresponders.

Use the slash version of each command below. Prefix commands keep working until March 5, 2027. What is changing

  • ,autoresponder → /configure feature:Autoresponders
  • ,autoresponder add → /configure feature:Autoresponders
  • ,autoresponder list → /configure feature:Autoresponders
  • ,autoresponder remove → /configure feature:Autoresponders
  • ,autoresponder update → /configure feature:Autoresponders
  • ,autoresponder match → /configure feature:Autoresponders
  • ,autoresponder clear → /configure feature:Autoresponders
  • ,autoresponder restrict add → /configure feature:Autoresponders
  • ,autoresponder restrict remove → /configure feature:Autoresponders
  • ,autoresponder restrict clear → /configure feature:Autoresponders
  • ,autoresponder role add → /configure feature:Autoresponders
  • ,autoresponder role remove → /configure feature:Autoresponders

Overview

Auto responders allow greed to automatically reply to messages that contain specific keywords. This is a powerful tool for automated FAQs, community jokes, or server moderation warnings.

Creating a Response

Create a responder by specifying trigger text and the response content. The command accepts inline syntax where the first phrase is the trigger and the rest is the response.

,autoresponder add (content) [--flags]

Run ,autoresponder add on its own to open the builder instead. Set the trigger, reply and match mode in one form, pick options like replying or deleting the trigger, preview the reply, then press Save.


Trigger Logic & Flags

You can fine-tune how sensitive your responder is and how it delivers the response.

Configuration Flags

Add these at the end of your command:

The responder will only trigger if the message content exactly matches the trigger keyword, with no other text around it. This check is case-sensitive.

Choose how the message is compared with the trigger. See Match modes below. A match mode replaces --strict.

greed will use the Discord "Reply" feature (mentioning the user) when delivering the response.

The response will automatically delete itself after the specified number of seconds (minimum 6, maximum 60).

greed will delete the triggering message after responding.

Control which mention types are allowed in the response: everyone-level mentions, role mentions, or user mentions.

Match modes

Every responder has a match mode. If you never pick one, greed uses its default matching: the trigger fires when it appears anywhere in the message as a word or part of one, and a trailing * matches any word that starts with it (thank* matches "thanks").

The four match modes all ignore upper and lower case:

The whole message must be the trigger. With the trigger hey greed, "hey greed" fires but "oh hey greed" and "hey greed how are you?" do not.

The message must begin with the trigger, and anything can follow it. !cuddle @user fires a !cuddle trigger, "oh !cuddle" does not.

The message must end with the trigger. "@user, welcome" fires a welcome trigger, "welcome @user!" does not.

The trigger can be anywhere in the message, even inside another word. dumb fires on both "you're dumb" and "dumbo".

Example
,autoresponder add !hug hugs [$1] --match startswith
,autoresponder match "hey greed" exact
,autoresponder match "hey greed" default

You can also change the match mode from /configure and from the dashboard's responder editor.

Advanced Triggers

If your trigger keyword contains spaces, wrap it in "quotes" (e.g., "good morning").

Use scripting variables like {user}, {channel}, or {guild} in your responses to make them feel personal.


Management & Limits

Server Limits

  • Free: Up to 15 auto responders.
  • Premium: Up to 500 auto responders.

Going over the free limit never deletes anything. The responders past the limit are paused: they stay listed with a warning next to them and stop firing until you remove enough to get back under the limit, or premium is active again. While a server is over the limit you can still delete responders, but not add or edit them.

Management Commands

  • ,autoresponder list: View all configured responders.
  • ,autoresponder remove (trigger): Delete a specific responder.
  • ,autoresponder update (trigger) (response): Update an existing responder's response. editreply works too.
  • ,autoresponder match (trigger) (mode): Change the match mode. editmatchmode works too, and default goes back to the default matching.
  • ,autoresponder view (trigger): Show one responder's match mode, options and response.
  • ,autoresponder clear: Wipe all responders from the server.

Restrict who can trigger a responder:

  • ,autoresponder restrict add (role) (trigger): Only allow users with this role to trigger the responder.
  • ,autoresponder restrict remove (role) (trigger): Remove role restriction from a trigger.
  • ,autoresponder restrict clear (trigger): Clear all role restrictions (allow everyone again).

Automatically assign or remove roles when a trigger fires:

  • ,autoresponder role add (role) (trigger): Grant a role when this trigger fires.
  • ,autoresponder role remove (role) (trigger): Remove a role when this trigger fires.

Reply functions

A reply can use the placeholders and functions below. greed saves these replies exactly as you wrote them and runs them when the trigger fires. You can mix them with greed's own scripting variables.

  • Member: {user} (mention), {user_name}, {user_tag}, {user_avatar}, {user_id}, {user_nick}, {user_joindate}, {user_createdate}, {user_displaycolor}, {user_boostsince}.
  • Any member placeholder can point at someone else by adding : and an ID, a mention or an argument, like {user_avatar:[$1]}.
  • Server: {server_name}, {server_id}, {server_membercount}, {server_membercount_ordinal}, {server_icon}, {server_rolecount}, {server_channelcount}, {server_owner}, {server_owner_id}, {server_createdate}, {server_boostlevel}, {server_boostcount}, {server_nextboostlevel}, {server_nextboostlevel_required}, {server_nextboostlevel_until_required}, {server_prefix}.
  • Channel: {channel}, {channel_name}, {channel_createdate}.
  • Message: {message_id}, {message_content}, {message_link}, {date}, {newline}.
  • Put a backslash in front, {user}, to show a placeholder as plain text.

Arguments are the words typed after the trigger, so they work best with the startswith match mode.

  • [$1] is the first word, [$2] the second, and so on.
  • [$2+] is the second word and everything after it. [$1-3] is words one to three.
  • {requirearg:1|user} only replies when argument 1 is a member. The other types are channel, role, color and number.
  • {choose:a|b|c} picks one option, and [choice] shows the pick.
  • {weightedchoose:rare 20%|common 80%} picks with the chances you set.
  • {lockedchoose:a|b} with [lockedchoice] picks once and reuses that pick everywhere in the reply.
  • {range:1-10} picks a number, shown with [range].
  • You can use up to three of each, numbered: {choose1:…} with [choice1], up to {choose3:…}.
  • {requireuser:…}, {requirerole:…}, {requirechannel:…} and {requireperm:…} only reply for that member, role, channel or permission.
  • {denyrole:…}, {denychannel:…} and {denyperm:…} block them instead.
  • {silent} hides the "you can't use this" message. {silent:your text} shows your own message instead.
  • {cooldown:30} lets each member use it once every 30 seconds.
  • {delete} deletes the trigger message. {delete_reply:10} deletes greed's reply after 10 seconds (up to 3600).
  • {dm} sends the reply in DMs. {sendto:#channel} sends it to another channel.
  • {embed} or {embed:#ff00aa} sends the reply as an embed.
  • {react:👍} reacts to the trigger message, {reactreply:👍} reacts to greed's reply.
  • {addrole:role}, {removerole:role} and {setnick:name} change the member who triggered it. Add | [$1] to target someone else, like {addrole:Muted | [$1]}.
  • {addlinkbutton:Label | https://…} adds a link button. {addbutton:name} adds a button.
  • Role and nickname actions never use dangerous roles, roles managed by an integration, @everyone, or any role above greed's highest role.
  • They only change members ranked below the person who triggered them, and never the server owner.
  • When you set up a responder, you can only use roles below your own highest role. The server owner can use any role greed can assign.
  • Economy functions (balance and inventory) are not supported and are skipped.