Flow triggers, conditions and steps
Every trigger, condition and step a Gildi flow can use, plus how waits, branches and variables work and how long a wait can be on each plan.
A flow is one automation. It starts with a trigger (something that happens, like a member joining or someone using a slash command), then runs its steps in order. Add a condition and the flow splits into two branches: what to do when it’s true, and what to do when it isn’t. The builder reads the whole thing back to you as plain sentences, like “When someone joins, give them @Sprout.”
Flows are how you make your own custom commands, and they’re also what modules like Welcome, Moderation and Levels run behind the scenes.
Building one
- Start from the trigger. Each flow has exactly one. A slash command trigger also names the command and its options.
- Add steps. A Free flow can have up to 25 steps, Plus up to 100 and Pro up to 250.
- Branch with conditions. Combine conditions with all, any or not. A step can also have an “if it fails” path, which gets the error as
{error}. - Test, then publish. Edits stay in a draft until you publish, and a test run lets you try it in a channel you pick.
A flow can’t loop back on itself. To repeat something or share steps between flows, use the Run another flow step.
Waits
A wait pauses the flow, then carries on where it left off. How long a single wait can be depends on the server’s plan:
| Plan | Longest wait |
|---|---|
| Free | 1 hour |
| Plus | 7 days |
| Pro | 30 days |
Discord only accepts a reply to a command or button for 15 minutes. After a longer wait, a reply is posted in the channel instead, and a reply only they can see isn’t sent. The builder warns you when that applies.
Variables
Every step that sends text can use message variables, such as {user.mention}. Which ones work depends on the trigger: a slash command gives you {options.name}, a form gives you its answers. Flows can also store their own values per server or per member with Set a variable, and read them back as {vars.server.name} or {vars.member.name}.
Runs
Every time a flow starts counts as one run, and each server has a monthly number of runs on its plan. Flow runs explains how they’re counted and what happens near the limit.
The full catalog
This list comes straight from the code the builder uses, so it’s always current.
Reference
Triggers (75)
Commands: Slash command, User menu command, Message menu command
Components: Button clicked, Select menu used, Form submitted
Messages: Message sent, Message edited, Message deleted, Messages deleted in bulk, Reaction added, Reaction removed, Message pinned or unpinned, Reactions cleared, Poll vote
Threads: Thread created or changed, Member joins or leaves a thread
Members: Member joins, Member leaves, Member passes screening, Role added to a member, Role removed from a member, Nickname changed, Member boosts, Member timed out, Member stops boosting, Timeout removed, Avatar changed, Member banned, Member unbanned, Member kicked
Voice: Joins a voice channel, Leaves a voice channel, Moves voice channel, Mutes, deafens, streams or shares video
Server: Server change, AutoMod blocked something, Stickers changed, Webhooks changed, Scheduled event created or changed, Someone follows a scheduled event, Stage started or changed, Integration changed, AutoMod rule changed, Soundboard sound changed
Time: On a schedule
Thresholds: Many events in a short time
Levels & economy: Member levels up, Daily reward claimed, Item bought, Item used, Balance crosses an amount
Moderation: Moderation case created
Other: Run by another flow, Incoming webhook
Community: Role picked, Member verified, Verification failed, Ticket opened, Ticket claimed, Ticket closed, Form answers submitted, Answer accepted, Answer denied, Giveaway ended, Message starred, Suggestion posted, Suggestion status changed, Appeal sent, Appeal decided, Birthday today, Invite reward reached, Voice room created, Voice room closed, Goal reached
Conditions (21)
Compare text or numbers, Member has role, Member has permission, In channel, In category, Random chance, Not on cooldown, Account age, Time in server, Member is a bot, Member has no avatar, Member is an unverified bot, Member name looks wrong, Time of day, Day of the week, Level at least, Leaderboard rank, Balance at least, Member owns item, List contains, Channel had messages since the bot last posted
Steps (81)
Messages: Send a message, Reply, Send a DM, Edit a message, Delete a message, React, Pin a message, Unpin a message, Publish an announcement, Remove a reaction, Clear reactions, Send a poll, Delete recent messages
Threads: Create a thread, Archive, lock or rename a thread, Add a member to a thread, Create a forum post
Interaction: Show a form, Show “thinking…”
Members: Add a role, Remove a role, Toggle a role, Apply picked roles, Set nickname, Time out, Remove timeout, Kick, Ban, Unban, Move in voice, Ban many members
Server: Create a channel, Edit a channel, Delete a channel, Set channel permissions, Create an invite, Create a role, Edit a role, Delete a role, Lock or unlock a channel, Set slowmode, Lock down the server, Pause invites, Pause DMs between members, Set verification level
Moderation: Create a case, Count warnings, List cases, Look up a case, Change a case reason, Lift or delete a case, Check a moderator may act on a member, Look up a member, Use a predefined reason, Start or end raid mode
Logic: Run another flow
Data: Set a variable, Increase a variable, Delete a variable, Add to a list, Remove from a list, Pick from a list
Levels & economy: Change XP, Start an XP boost, Change balance, Give or take an item, Claim the daily reward, Work for currency, Transfer to a member, Buy an item, Use an item, Gift an item to a member, Look up level and balance, List the leaderboard, List the shop, List an inventory
External: HTTP request, Send to a webhook
Community: Give a role for a set time, Open a ticket, Start a giveaway