Automations

Build simple if-this-then-that rules that connect modules, roles, messages, and staff workflows.

Set it up

1. 1Open Automations and enable it.
2. 2Create a rule with one trigger, optional conditions, and one or more actions.
3. 3Turn on a staff-only log action, save, and test the rule with a harmless case before using it live.

How to think about automations

An automation is a small rule: when this trigger happens, optionally check conditions, then run one or more actions. Keep the first rule narrow, test it, then add more rules.

Supported rule shape

• Trigger - the event that starts the rule, such as a member joining, verification passing, a role being granted, or a scheduled interval.
• Conditions - optional checks, such as member has/does not have a role, channel matches, or text contains a phrase.
• Actions - what QREATE does next, such as grant/remove a role, send a message, post a log, or open a follow-up workflow.

Example rules

New member onboarding:
Trigger: member joins
Conditions: account age greater than 7 days
Actions: send welcome DM, add @New role, post to #mod-log

Verified reward:
Trigger: verification passed
Conditions: member does not have @Member
Actions: add @Member, remove @New, post a short welcome in #welcome

Support escalation:
Trigger: ticket created
Conditions: category is Billing
Actions: mention @Support Lead, add internal note, route log to #ticket-log

Safety rules

• Do not build loops where an action immediately retriggers the same rule.
• For role actions, check QREATE's role hierarchy before enabling the rule.
• Use a staff-only log action while testing so you can see each run.
• Disable or pause a noisy rule before editing it during a live event.

What to know

• Automations is for glue between existing surfaces, not a replacement for module settings.
• Keep rules small and named by outcome, such as Verified member cleanup or Billing ticket escalation.
• If a rule grants or removes roles, Discord role hierarchy still applies.