Beta Visual node-based editor

Como funciona o Logic Nodes

Logic Nodes is the most visual way to build an automation in Ayami: you connect blocks on a canvas instead of writing code or filling out a form step by step.

"Think of it like a whiteboard: every node is an idea, and the lines are the path it travels.", Ayami

What is Logic Nodes

Logic Nodes is a visual automation editor based on connected nodes: you drag blocks onto the canvas — an event, a condition, an action — and link them with lines to draw the path the flow should follow.

It's part of the Logic Engine, the same automation engine behind Logic Builder and Logic Script. The only difference is how you build: here, everything happens by arranging nodes in space instead of filling out a step-by-step form or writing text commands.

Logic Nodes
Built by dragging nodes onto a free-form canvas. Great for visualizing flows with multiple paths.
Logic Builder
Built by filling out a step-by-step form (When → If → Then).
Logic Script
Written directly as code, in the Logic Script language.

All three products share the same engine under the hood — so whatever you build in any of them runs the same way on your server. Pick whichever fits how you think.

Canvas Anatomy

Every Logic Nodes flow follows the same logic: an event node triggers the flow, it can pass through condition nodes that decide whether the path continues, and it ends in action nodes that make something actually happen on your server.

Event Command
Condition IF
Action Send Message

Simplified example: a command triggers the flow, a condition decides the path, and an action executes the result.

Node Library

Side panel listing every available node, organized by category and searchable.

Properties

Panel that opens when you select a node, to configure its specific fields.

Connections

Lines that link one node to another, defining the flow's execution order.

Undo/Redo

Undo and redo any change on the canvas, without fear of making a mistake.

Node Categories

Nodes are organized into 4 categories, each with its own color on the canvas to make the flow easier to read at a glance:

Event — where the flow starts

Start

Starting point for flows that don't depend on a specific external trigger.

Command

Triggers the flow when someone uses a configured slash command.

Interaction Create

Triggers when the bot receives any interaction (button, menu, etc).

Condition — decides if the flow continues

IF

Splits the flow into two paths, depending on a condition.

Compare Text

Compares two text values against each other.

Compare Number

Compares two numeric values (greater, less, equal).

Contains Text

Checks whether a text contains a specific substring.

Equal

Checks whether two values are exactly equal.

Exists

Checks whether a value exists (isn't null or empty).

Action — what actually happens

Send Message

Sends a message in a server channel.

Edit Message

Edits a message previously sent by the bot.

Reply to Interaction

Replies to the interaction (button, menu) that triggered the flow.

Reply to Message

Replies directly to a message, as a quote.

Edit Reply

Edits a previously sent interaction reply.

Ephemeral Reply

Sends a reply visible only to whoever interacted.

Delay

Pauses the flow for a set time before moving to the next node.

User Variable

Reads or writes a value tied to a specific user.

Server Variable

Reads or writes a value shared across the whole server.

Flow — control of the flow itself

End

Marks the explicit end of a flow path.

A Node's Properties

When you select a node on the canvas, the Properties panel opens on the right with that node type's specific fields — that's where you set, for example, which channel to send a message in or what text to display.

Action Send Message
Properties — Send Message
#geral
Welcome to the server! 🎉

Just like in Logic Builder, text fields accept placeholders like {user} or {guild}, which get replaced with real values when the flow runs.

Full Flow Example

A simple welcome flow, built with 4 nodes connected in sequence:

Event Member Joined
Condition Has Blocked Role?
Action Send Welcome
Flow End

Each line between nodes represents the execution order. When a condition has more than one possible output (yes/no), you can connect different paths from it — just like Logic Builder lets you branch with conditions, except here the path is visible right on the canvas.

Automatic execution

Logic Nodes is out of Beta: build your flows visually and they run for real on your server.

As soon as you save a flow, the execution engine starts listening for commands and interactions (buttons, menus, modals) and walks the graph automatically when the trigger fires.

The same guidance still applies: for the fastest way to build, Logic Builder is the most direct path; for more control with code, Logic Script. Logic Nodes shines for more complex, branching visual flows.

Ready to sketch your first flow?

Open the visual editor right from your server's dashboard and start building.