Skip to content
yurna
  1. Documentation
  2. Automations
  3. Triggers, blocks and placeholders

Triggers, blocks and placeholders

Every block in the flow editor at a glance – from “Member joined” to “Counter” – plus placeholders like {user}.

Requires Premium · Half MoonDashboardAutomation

Requires Premium

This feature is available from the Half Moon plan.

The flow editor groups its blocks into four categories: Triggers, Actions, Logic and Data. A flow needs at least one trigger; after that you can connect as many blocks as your plan allows.

Triggers#

BlockStarts when …
/flow commandsomeone uses /flow with this flow's name (only on your server)
Button clickedsomeone clicks a flow button with this button ID
Message containsa message contains a text, starts with it, is exactly it or matches a regular expression – optionally only in one channel
Member joined / Member leftsomeone joins or leaves the server
Reaction addedsomeone reacts with an emoji (empty = any reaction, optionally only on one message)
Role added / Role removeda member gets or loses a role (empty = any role)
Scheduledaily or weekly at a set time, or every X minutes (at least 10)
yurna command usedsomeone has used a built-in yurna command, e.g. “ticket”

Schedules use the Europe/Berlin time zone. A missed slot is caught up for up to 30 minutes. Since a schedule has no triggering person, you set a Channel for {channel} there.

Actions#

  • Reply – replies to the command, button or message. With Only visible to that person (for commands and buttons) only the triggering person sees the reply.
  • Send message – text, embed, up to 5 buttons and up to 5 reactions in a channel. Without a channel, yurna uses the current one.
  • Send DM – a direct message to the triggering person or to the member from the command option.
  • Add/remove role – add, remove or toggle a role.
  • Webhook / HTTP – calls a public http(s) address (GET/POST, 5-second timeout). Pick a value from the JSON response with a JSON path like data.0.name. Full Moon only.

Buttons in “Reply” or “Send message” get a button ID. A click starts every flow with the “Button clicked” trigger and the same ID.

Logic#

  • Condition – compares values (equals, contains, greater than, is empty, matches regex …), checks “Member has role” or “Channel is”. The flow continues through the Yes or No output.
  • Random – picks one of 2 to 5 equally likely paths.
  • Wait – pauses for seconds or minutes, at most 15 minutes in total per run.

Data#

  • Set variable – stores text or calculates with numbers during a run. Then usable as {var.name}.
  • Counter – a persistent counter for the whole server or for each member separately: increase, decrease, set to a value or read only. Usable as {counter.name}. Up to 500 counters per server.

Placeholders#

yurna fills in placeholders in texts when the flow runs:

PlaceholderMeaning
{user}, {user.name}, {user.id}, {user.avatar}mention, display name, ID and avatar of the triggering person
{server}, {server.members}server name and member count
{channel}, {channel.name}channel mention and channel name
{date}, {time}date and time (Europe/Berlin)
{random:a|b|c}one of the values at random
{option.eingabe}, {option.mitglied}input given to the /flow command
{count}how often the /flow command has been used
{message}, {button}, {reaction}, {role}message text, button ID, emoji or role of the trigger
{http.status}, {http.value}result of “Webhook / HTTP”

Unknown placeholders stay visible as they are – so typos stand out right away.

Note

Blocks from the old editor appear as Legacy block. They keep working but can't be configured any more. It's best to replace them with new ones.

See also#

Last updated on 15 October 2026