Build

The editor

Where you build a Blueprint: you place Nodes on a canvas, link them, set them up, then test and deploy it.
1The top bar — where you are, the status, who's here, Test and Deploy. The Blueprint's name opens its window (overview, activity, analytics); the logo menu, the view and help.2The canvas — the Nodes and their links.3The toolbar — the Nodes by family, a group, a note and search.4Properties — the selected Node, its fields and what it gives next.5The bottom panel — one section at a time: Problems, Executions, Test or History.6The status bar — saving, the problems, the bottom panel's sections, the credits and the zoom.

Create a Blueprint

  1. Click New Blueprint, from the Blueprints page, the server's home page or the editor's logo menu. A window opens over the Blueprints page.
  2. Give it a name, and a description if you want.
  3. Choose what to start with: an empty canvas, or an Event already placed (a command, a message, a member joining, a reaction, a schedule).
  4. Click Create: the editor opens on your Blueprint. Esc cancels: nothing is created before.

The draft then saves on its own, at every change.

Open a family in the toolbar (Command, Event, Discord, Data, Logic), click a Node then place it on the canvas, or drag it there.

To link two Nodes, drag from an output of one to the input of the other. Drop the link on empty canvas to pick the next Node: it's created there, already linked. A right-click on the canvas adds a Node at that spot; on a Node, it copies it, duplicates it, adds what follows or deletes it.

One output, several Nodes. The branches run one after the other, in the order they were linked, never at the same time. Each link shows its number (1, 2, 3) halfway along; to change the order, delete the links and create them again in the order you want.

A Node runs for every path that reaches it. If two links of one output lead to the same Node, directly or further on, it runs twice, with everything after it. The editor flags it on the Node, with the number of possible runs. It's useful to write in a log channel from two branches; for a summary to send only once, chain it after the other Nodes.

Set up a Node

Click a Node: the Properties panel shows it, beside the canvas. To widen it, drag the space between it and the canvas; a double click gives it back its size. The bottom panel, which the status bar opens, resizes the same way; its title ▾ switches from one section to another.

  • At the top, its type (hover it to read what it does), its number, its cost and a link to its reference page. Its ⋯ menu copies its id or deletes it.
  • Settings: its problems first, each with a link to fix it ("Go to the field", "See on the canvas"…). Then the fields, and Options and Advanced (folded) for less common settings. Some only show when they apply: the audio bitrate for a voice channel, the Forum settings for a forum.
  • Output lists what the Node writes, output by output. Click a value to copy its reference, then paste it into a later Node.
  • Activity shows the Node over seven days (its runs, its failures, its average duration) and its latest executions. A failed execution reopens on the canvas. The tab needs the right to view analytics or executions.

A text field accepts data from an earlier Node, written {{ … }}: see Expressions. A picker (channel, role, number, yes/no, list) switches to a formula with the ƒ button, to write an expression instead of a choice.

Change what exists

On an Action that changes something that exists (Edit channel, Edit message…), each field has a menu next to its name:

ChoiceWhat happens
Don't changeThe field stays as it is on Discord.
Change toThe field takes the given value. If it's empty when the Action runs, the Action fails rather than silently doing nothing.
ClearThe field is emptied (a channel's topic, its category…), only where Discord allows it.

For a channel's permissions and a forum's tags, Add or change only touches what's listed, and Replace all replaces the whole list.

When an Action fails, the execution's trace links to the explanation of its error in the error reference.

Compare two versions

In History (in the status bar, at the bottom), pick a version: its detail shows what it changed, and Compare sets it against the draft. The canvas shows what was added (green), changed (orange) or removed (dashed red) since, and Properties shows the before and after of the Node you click. You can change the two versions compared, step from one change to the next, and fade what didn't change. Exit, at the right of the bar, or Escape, goes back to the editor.

Shortcuts

ShortcutWhat it does
KAdd a Node, go to a Node of the Blueprint or run an action
= / -Zoom in, zoom out
⇧ 1 / 0Fit the view, zoom to 100%
.Hide or show the interface, to keep only the canvas
?Show every shortcut
,Open your settings
/Go to the page's search, anywhere in the dashboard
G then a letterOpen a page of the server: G B the Blueprints, G E the Executions…

The toolbar's search icon opens the same palette as K. From the keyboard, Tab moves from Node to Node on the canvas, the focused one ringed like a selection; before them, a Go to the properties link (or Skip the canvas) jumps straight to the panel.

You can change the editor's shortcuts in your settings, two per action at most.

See also

How data flows

What a Node can read, and why a value can be empty.

Expressions

Insert data, compute, format.

Test mode

Try the draft for real on Discord.