Skip to main content

Support Flows

Support Flows are visual workflows made from connected nodes. Use them when a ticket needs more than a simple button: ask questions, route by answer, call an external service, create a ticket with context, or run follow-up actions automatically.

Flow types

TypeUse it forTriggered by
Click-startedForms, guided intake, knowledge base suggestions, conditional ticket creationPanel buttons, custom commands, or a category's workflow buttons
Runs on its ownBackground ticket actions, reminders, tagging, routing, auto-close workflowsCategory auto-actions and automation rules

Click-started flows can ask the member for input; flows that run on their own work without anyone clicking. These docs also call them interactive and automation flows, and an automation rule starts one with Run an automation flow. After Create Ticket, a click-started flow carries on inside the new ticket the same way a flow that runs on its own does.

Build a flow

Create it

Open Automations → Flows in the dashboard, choose New Flow, then pick Click-started or Runs on its own.

Add nodes

Drag nodes into the builder and connect them in the order they should run. Every flow starts at a Start node.

Configure each node

Set labels, messages, conditions, variables, or actions on each node. Keep labels short so the builder remains readable.

Test and activate

Run a test, fix any missing connections, then mark the flow active.

Attach interactive flows to a panel button, a command, or a category's workflow button. Attach automation flows from a category auto-action or automation rule.

Node catalog

Node cards in the builder show the exact plan requirement. The groups are:

Interactive nodes

Collect input or show information during an interactive flow.

Embed

Show rich info in a Discord embed: title, description, images, and fields.

Use for:

  • •Welcome messages
  • •Instructions
  • •Formatted info display

Button

Present navigation buttons with customizable styles and emojis. Up to 5 buttons per row.

Use for:

  • •Menu navigation
  • •Yes/No choices
  • •Multi-option selection

Modal

Collect input from users via Discord modals. Each page holds up to 5 fields, and modals can span multiple pages for longer forms.

Use for:

  • •Short text answers
  • •Long descriptions
  • •Multi-page form collection
Community

Application

Multi-page application posted to a review channel, with an optional Approve/Deny step that can grant a role.

Use for:

  • •Staff applications
  • •Whitelist or allowlist requests
  • •Role applications with review

Create Ticket

Final action to create a ticket with collected information in a specific category.

Use for:

  • •Creating tickets
  • •Routing to categories
  • •Setting priority

Condition

Branch based on user responses or variables with multiple condition operators.

Use for:

  • •Conditional routing
  • •Response-based logic
  • •Value checking

Permission Check

Verify user has required Discord permissions with AND/OR logic.

Use for:

  • •Admin-only flows
  • •Staff verification
  • •Role-based access

Logic Gate

Advanced AND/OR logic branching with multiple condition checks.

Use for:

  • •Complex logic
  • •Multiple conditions
  • •Variable existence checks

Knowledgebase

Display knowledge base articles with pagination controls to reduce ticket volume.

Use for:

  • •Self-service
  • •FAQ display
  • •Troubleshooting guides

Action nodes

Change a ticket, message a channel, tag a role, set a variable, or wait before continuing.

Send Message (Ticket)

Send a message into the current ticket channel, with variable interpolation support.

Use for:

  • •Automated notifications
  • •Status updates
  • •Reminders

Send Message (Channel)

Send a message to any channel you choose, not just the ticket channel, with variable support.

Use for:

  • •Post to a log channel
  • •Notify a staff channel
  • •Cross-post updates

Rename Ticket

Rename the ticket channel from a template, so its name reflects the latest context.

Use for:

  • •Add the order number
  • •Show the issue type
  • •Mark a ticket escalated

DM User

Send a direct message to the ticket creator, the staff member who claimed it, or a specific user.

Use for:

  • •Follow-up messages
  • •Private instructions
  • •Status nudges

Reopen Ticket

Reopen a closed ticket, with an optional reason, so the conversation can continue.

Use for:

  • •Customer replies again
  • •Reopen on new info
  • •Undo an early close

Set Variable

Store a value in a flow variable for use in later nodes, with full variable interpolation.

Use for:

  • •Save a computed value
  • •Carry state between nodes
  • •Flags
Community

Round-robin Assign

Assign the ticket to the next staff member in a role, spreading work evenly across the team.

Use for:

  • •Even workload
  • •Fair distribution
  • •Auto-claim by rotation
Community

Request Rating

Ask the ticket creator to rate their support, using a five-star scale or a thumbs up/down.

Use for:

  • •Collect CSAT
  • •Post-close feedback
  • •Measure quality

Add User

Add users to ticket channels automatically for team collaboration.

Use for:

  • •Adding staff
  • •Including users
  • •Team collaboration

Remove User

Remove users from ticket channels for access control.

Use for:

  • •Removing users
  • •Access control
  • •Temporary participants

Close Ticket

Automatically close tickets with optional reason and silent mode.

Use for:

  • •Auto-close inactive
  • •Close after resolution
  • •Scheduled closing

Tag Role

Mention roles in tickets for notifications and escalation.

Use for:

  • •Notify teams
  • •Escalation
  • •Role alerts

Claim Ticket

Automatically assign tickets to staff members for load balancing.

Use for:

  • •Auto-assignment
  • •Load balancing
  • •Round-robin

Update Priority

Change a ticket's priority as part of a flow, for example when triage detects an urgent issue.

Use for:

  • •Escalate urgent tickets
  • •Set priority on triage
  • •Re-prioritize on reply

Add Note

Add an internal staff note to the ticket, visible to your team but not to the ticket creator.

Use for:

  • •Record context
  • •Hand-off notes
  • •Triage findings

Move Category

Move the ticket to a different category, updating its support roles and settings.

Use for:

  • •Re-route to the right team
  • •Escalation paths
  • •Reclassify tickets

Generate Transcript

Save a transcript of the ticket conversation to the configured transcript channel.

Use for:

  • •Archive on close
  • •Compliance records
  • •Supervisor review

Delete Ticket

Permanently delete the ticket channel. A transcript is saved first when auto-transcript is enabled.

Use for:

  • •Remove spam tickets
  • •Clear test tickets
  • •Close-and-purge flows
Community

Wait / Delay

Pause an automation for a set time, up to your plan's max, before the next node runs. Automation only.

Use for:

  • •Send a reminder later
  • •Stagger follow-ups
  • •Wait before auto-close
Pro

Wait for Reply

Pause until the ticket opener (or anyone you pick) replies, then branch on reply vs timeout. Automation only.

Use for:

  • •Ask for missing details
  • •Confirm before closing
  • •Chase a stalled ticket
Pro

Wait for Reaction

Post a prompt and wait for a reaction, routing each emoji to its own branch, plus a timeout path. Automation only.

Use for:

  • •Staff approval gates
  • •Yes / no confirmations
  • •Route by emoji choice
Pro

Poll

Post a Discord poll and wait for it to close, then continue down the winning answer's branch. Nobody voting has its own path. Automation only.

Use for:

  • •Let a ticket vote on an outcome
  • •Group decisions
  • •Pick between options
Community

Manage Role(s)

Add or remove Discord roles on the ticket creator, the claimer, the last person to reply, or a user you name.

Use for:

  • •Grant access after approval
  • •Verification roles
  • •Revoke a role on close
Community

Account Lookup

Look up a member's linked Steam, Roblox, Minecraft or game server account, use it in later steps, and branch on whether one was found.

Use for:

  • •Only open tickets for linked players
  • •Show in-game stats in a message
  • •Ask unlinked members to link first

Looking up a member's linked accounts

The Account Lookup node fetches a member's Steam, Roblox, Minecraft or game server account at that point in the flow, the same lookups a category runs when a ticket opens. It fills {{steam.*}}, {{roblox.*}}, {{minecraft.*}} and the game server variables for later steps, and branches Found, Not found or Unavailable, with Otherwise for any branch left unconnected. It only reads accounts the member shared with your server, and needs Community or Pro. See Account Lookups in Flows.

Letting a button run out

A button posted by an automation flow stays in the channel, so by default anyone can press it as often as they like and the flow runs again each time. Give a button a click limit to cap that. Once the limit is reached the button either greys out or disappears, whichever you pick, and the flow can swap the message text for something else at the same time.

The count is per posted message and shared by everyone, so a limit of 1 makes a claim-once button: the first person to press it takes it. Leave the limit empty and the button keeps working indefinitely.

This applies to automation flows, and to an interactive flow's buttons when the message is sent to a channel. Otherwise an interactive flow replaces its message at every step, so its buttons cannot be pressed twice.

Showing answers on the ticket

Create Ticket copies the answers collected earlier in the flow onto the new ticket while Include form responses is on. Under the switch is a tick box for each form field and each message dropdown that comes before the step, on every branch leading to it. Clear the box to keep it off the ticket. A run only fills the answers on the path the member actually took, so a dropdown on a branch they skipped never appears.

A dropdown answer shows the option the member picked, under the dropdown's Answer name (its placeholder text or the message title when that's left empty). Steps wired after Create Ticket run inside the new ticket, so a Send Message there can repeat any answer: pick it from the variable picker, or type {{responses.<Answer name>}}.

Dropdowns on different branches can share an answer name. A flow that asks "Basic or advanced hosting?" and then shows a basic or a premium plan dropdown can name both plan dropdowns Plan Type, so one message works whichever way the member went:

Plan Class: {{responses.Plan Class}}
Plan Type: {{responses.Plan Type}}

A condition on a dropdown compares against the option label too.

How long a flow can wait

Four nodes pause an automation flow: Wait / Delay parks it on a timer, while Wait for Reply, Wait for Reaction and Poll suspend it until someone acts. Wait / Delay is available on Community and Pro; the other three are Pro only. A Poll runs for whole hours, because that is what Discord accepts, and it continues once the poll has closed and the votes are final.

One maximum covers whichever of the four your plan can use, and it comes from your plan. Community servers can wait up to

7 days, and Pro raises that to 30 days.

That is long enough for the usual follow-up pattern: ask the member for the missing details, wait a couple of days, nudge them, then close if the ticket is still quiet.

Saving a flow whose wait exceeds the maximum is rejected, so the builder always shows what the flow will actually do.

Waits end with the ticket

If the ticket is closed or deleted while a flow is waiting, the wait is canceled and the run is marked abandoned. A paused flow never resumes into a ticket nobody can reply to.

When a flow loops back on itself

A step wired back to an earlier one can send a run round the same circle over and over. A run that takes 50 steps in a row without any of them doing anything is stopped and marked abandoned.

Bad wiring often only breaks one way of starting the flow. A form step waits for a person, so the flow finishes when someone drives it from a panel, and the same flow can circle when it carries on by itself after a ticket is created, because nothing left in the circle can act without input. So the pause is per trigger: five circling runs on one trigger within 24 hours pause that trigger for 24 hours, and every other way of starting the flow keeps running. Switching the whole flow off would take the working path down with the broken one.

The server owner gets one DM naming the flow and the way of starting it that paused, in plain words rather than internal names. There is nothing to switch back on, since the pause lifts itself when the 24 hours are up, so fix where the last step points before then or it will pause again.

Advanced nodes

Compose flows out of other flow blocks.

Call Flow

Trigger another flow with variable passing for reusable workflows.

Use for:

  • •Flow reusability
  • •Nested workflows
  • •Shared sub-flows

Integration nodes

Call webhooks, external APIs, connected apps, or AI features.

Pro

Send Webhook

Send data to external webhooks with custom headers and JSON body interpolation.

Use for:

  • •External services
  • •Trigger automations
  • •Zapier/Make/n8n
Pro

API Request

Fetch data from external APIs with authentication and JSONPath extraction.

Use for:

  • •User verification
  • •Data lookup
  • •External integration
Pro

AI Logic

AI-powered routing and response generation with knowledge base context.

Use for:

  • •Intelligent routing
  • •Automated responses
  • •Sentiment analysis
Pro

AI Summarize

Generate a short summary of the ticket conversation so staff can catch up at a glance.

Use for:

  • •Hand-off summaries
  • •Quick context
  • •Transcript recaps
Pro

AI Sentiment / Route

Read the tone of a message and branch the flow, for example sending frustrated users to a priority path.

Use for:

  • •Detect frustration
  • •Priority routing
  • •Escalate by tone
Pro

AI Suggested Reply

Draft a reply for staff to review and send, based on the ticket and your knowledge base.

Use for:

  • •Faster responses
  • •Draft answers
  • •Assist new staff
Pro

AI Auto Reply

Send an AI-written reply automatically, grounded in your knowledge base, to handle common questions.

Use for:

  • •Answer FAQs
  • •Reduce ticket load
  • •First-line support
Pro

Translate

Translate a message between languages so your team can support users in any language.

Use for:

  • •Cross-language support
  • •Translate replies
  • •Global teams

Plan gates

Webhook, API and AI nodes require Pro.

Variables

Most text fields take variables, such as {{user.mention}}, {{ticket.number}} or {{responses.Email}} for an answer a form collected. Names are case-sensitive. See the variables reference for the full list, and put {{all_variables}} in a step while you build to print everything the flow has collected so far.

A Set Variable node saves your own value as {{custom.name}}; see Saving your own values and the order menu guide.

Conditions

A Condition node sends the flow different ways depending on what is true right now. It has one or more rows, each wired to its own next node, plus an else output (labeled Closed on the Business hours preset). The rows are checked top to bottom, and the first one that matches decides where the flow goes; if none match, it takes else. To show or hide text inside a message instead, use conditional blocks.

Start from a preset (Business hours, User has role, Priority is, Message contains, Has Roblox account or Is banned), or pick Advanced to build the rows yourself. Each row checks one of these:

SourceWhat it checks
Variable / fieldAny variable: a custom.* value, a form answer (responses.Email), the button pressed on an earlier node (pick that node as the data source; inside a ticket only the button just pressed is available, so save earlier choices with Set Variable), an api.* field, a lookup result such as roblox.name, or ticket.priority
Message contentText in the ticket's messages: the last one, the last few, or all of them, counting messages from anyone, only the ticket creator, or only staff
User has permissionWhether a member holds a role or Discord permission: the member who started the flow, the ticket creator, the claimer, the last replier or a user you name
Staff role heldWhether at least one member holds any of the roles you pick. Point it at a role your staff add while on duty, such as On Duty
Business hoursWhether it is within your server's business hours

A variable row names the variable without braces, such as custom.tier, and compares it with one of these:

ComparisonNotes
Equals, Does Not EqualThe whole value, ignoring case, so vip equals VIP
Contains, Does Not Contain, Starts With, Ends WithPart of the value, ignoring case
Regex MatchA regular expression, also ignoring case
Is Empty, Is Not EmptyWhether the variable has a value at all. Use it to check whether an earlier Set Variable or form filled it in

The value you compare against is plain text. It can't be another variable, and there is no "greater than": to check a number, use Regex Match, for example ^[1-9][0-9]{2,}$ for 100 or more.

To require several things at once, use a Logic Gate node. It combines conditions with AND (all must be true) or OR (any one) and branches True or False, for example "has the VIP role AND it is within business hours". To act when something is not true, use the Condition's else output.

Waits, loops and repeat clicks

BehaviorHow it works
WaitingWait / Delay parks an automation flow on a timer (Community and Pro). Wait for Reply, Wait for Reaction and Poll wait until someone acts (Pro). The longest wait is 7 days on Community and 30 days on Pro, and a flow that asks for longer can't be saved.
PollsRun for whole hours, because that is what Discord accepts, and continue once the poll closes.
Ticket closesIf the ticket is closed or deleted, a wait is canceled and the run is marked abandoned, so a paused flow never resumes into a ticket nobody can reply to.
Click limitsA button posted to a channel can be pressed again and again. Set a click limit to cap it. The count is per posted message and shared by everyone; once it is reached the button grays out or disappears, and the message text can change. A limit of 1 makes a claim-once button.
LoopsA run that takes 50 steps in a row without any of them doing anything is stopped. Five such runs from one trigger within 24 hours pause that trigger, and only that trigger, for 24 hours. The server owner gets one DM naming the flow.

An interactive flow replaces its message at every step, so its buttons can't be pressed twice unless the message was sent to a channel.

Buttons that start another flow

A public message, such as a listing or sign-up post, can stay up as long as you like. Point its buttons at another flow, rather than at a step in this one, and every press starts that flow fresh for whoever pressed it. A message sent to a different channel must use buttons like this, because the flow that posted it has already finished.

A button that continues the same flow also works, but whoever presses it starts again from that step without the earlier answers. That is fine for a menu, and the editor warns you if later steps need those answers.

The flow a button starts can read who posted the message and what they answered, through the source.* variables. For example, an Accept button can start a flow that creates a ticket and then uses Add User with {{source.user.id}} to bring the poster in.

Import, export, and templates

Use Templates to start from common flow shapes such as ask-questions-first, route-by-topic, tag-staff, save-transcript, or warn-then-close.

Use the flow card action menu to Export as JSON. Use Import on the Support Flows page to create a new flow from an exported file. Server-specific IDs are not included, so imported flows still need to be linked to this server's panels, categories, channels, and roles.

Limits by plan

LimitFreeCommunityPro
Active flows5UnlimitedUnlimited
Total flows10UnlimitedUnlimited
Webhook nodes00Unlimited
API request nodes00Unlimited
AI nodes00Unlimited
AI tokens / month10,000250,0005,000,000
Longest flow waitNot available7 days30 days

AI usage and limits

AI nodes require Pro. They share the server's monthly AI token budget, and the Plan & Billing page shows usage, limit, and reset date.

The reply nodes (AI Suggested Reply and AI Auto Reply) have an Include knowledge base switch that grounds the reply in published knowledge base articles and approved AI memory. It is on by default for new nodes, and a node saved without an explicit setting inherits the server-wide grounding default from AI Control. AI Auto Reply can post straight to the customer or run in draft mode, where staff review the reply with Send, Edit, and Discard buttons before anything reaches the customer. The AI Decision and AI Classify routing nodes have an opt-in Ground in knowledge + memory switch that adds the same retrieved context to their verdicts. See AI Assist for the reply modes in full.

If your server brings its own OpenAI-compatible provider key, AI runs on your provider account instead of the included platform budget. Plan limits for how many AI nodes a flow can use still apply.

Troubleshooting

ProblemCheck
Flow does not startIt is active and linked to the panel, command, category, or rule that should trigger it.
Flow stops mid-runEvery branch has a next node or an intentional end.
A trigger stopped firing on its ownIt is not looping on that trigger. Five circling runs pause that trigger for 24 hours, and the server owner is DMed once.
A variable is empty or shows as typedIt is set earlier in the run and spelled the same. Add {{all_variables}} to a step to see the real names.
Webhook, API, or AI node is disabledThe server plan includes that node type.
Modal does not appearEach modal page has at least one field and no more than five. Longer forms split across multiple pages.