Custom Triggers

Custom triggers match configured message input and send a stored response, providing lightweight server-specific automation.

• Choose trigger phrases that are specific enough to avoid accidental matches.
• Review response content and mentions before enabling it in busy channels.

1. Open Custom Triggers in the dashboard and add a trigger.
2. Enter the match text, choose contains or exact matching, compose the response, and review its cooldown and action.
3. Save and test the intended match plus a near miss from a normal member account.

• Contains matching responds when the phrase appears within a message; exact matching requires the complete configured phrase.
• Set a per-member cooldown from no delay through 24 hours to prevent repetitive responses.
• Free servers can configure up to three triggers and use response-only or direct-message behavior.
• Test capitalization, punctuation, common sentences, and near matches before enabling a trigger in a busy channel.

• Premium actions can delete the matching message, apply a timeout, kick, ban, add or remove a role, or send a direct message.
• Timeout duration can be configured up to 28 days and all moderation actions still require the corresponding Discord permission and role hierarchy.
• Keep role actions away from privileged roles and use narrowly scoped phrases for destructive behavior.
• Review the resulting action through Discord's Audit Log and keep a documented staff appeal path.

• Premium servers can let an external service fire a trigger's saved response directly, with no matching Discord message required — useful for wiring up uptime monitors, stream-alert services, CI jobs, or other automation.
• Open the trigger, turn on "Allow external webhook firing" under Webhook-Triggered Firing, and choose the channel the response posts to.
• Select "Generate webhook URL" to create a private URL, then copy it immediately; "Regenerate" issues a new URL and invalidates the old one, and "Revoke" disables firing until a new URL is generated.
• Any HTTP POST to that URL (no request body needed) posts the trigger's saved response to the configured channel, up to 20 requests per minute.

• Matching messages receive the configured response.
• Messages outside the configured match conditions do not trigger the automation.