BuildcordDocs

Nodes

Every step you can add to a flow, grouped by category, with its settings and ways out.

A node is one step in a flow. This section documents all of them. Each node has the same parts, and each page follows the same layout.

How to read a node

PartWhat it is
KindThe identifier that appears in the blueprint, such as message.reply.
SettingsThe fields you fill in. Text fields accept tokens unless noted.
Ways outThe handles on the right edge. A branching node has one for each outcome.
SummaryWhat the node says about itself on the canvas.

Categories

Ways out

Most nodes have one way out, labeled out. Branching nodes have named ways out. Green ways out mark the expected outcome and red ones mark the other.

Any node that can fail also offers a red If it fails way out. Turn it on in the node's settings. See Handling failures.

Shared settings

Several settings appear on many nodes and mean the same thing everywhere.

SettingWhat it does
MessageThe text to send. Accepts tokens.
EmbedOne of your embeds.
Buttons and menusOne of your component sets.
Only visible to the userMakes the reply ephemeral: only the person who triggered the flow sees it.
MemberA member's ID, a mention, or a token such as {option.member} or {user.id}. Left empty on a moderation step, it's the member a command names, or else whoever started the flow.
Audit log reasonThe reason Discord records in the server's audit log.
ChannelA channel of the server.
RoleA role of the server.
Where, Sorted by, Read the row asThe collection query settings.

Unknown steps

If a step's type no longer exists, the canvas shows Unknown step. Delete it and add its replacement.

On this page