FLOWS NODES · 7 NODE TYPES
The building blocks of
intelligent automation.
Every Maxx Stacks Flow is composed of nodes. Seven distinct node types — each with a specific purpose, a specific capability, and a specific place in the logic of your workflow. Learn each type, understand when to use it, and compose flows of any complexity without writing code.
NODE REFERENCE
Node Types
Seven nodes.
Infinite combinations.
TRIGGER
Action Node
Executes a specific operation against a connected system. Update a record, send a message, create a document, call an API endpoint. Action nodes are deterministic — they do exactly what you configure, every time.
USE WHEN
You need to interact with an external system in a defined, predictable way. Best for CRM updates, notifications, data writes, and webhook calls.
LOGIC
Decision Node
Evaluates one or more conditions and routes the flow down different branches. Conditions can reference any field in the current payload, outputs from prior nodes, or external data lookups. Supports AND/OR logic.
USE WHEN
The next step depends on the value of a field, the result of an action, or the output of an agent. Creates separate execution paths for different outcomes.
INTELLIGENCE
AI Agent Node
Invokes a configured Maxx Stacks AI agent. The agent receives the current flow payload, reasons about it, executes multi-step tasks against connected systems, and returns a structured output for the next node.
USE WHEN
The task requires reasoning, judgment, or multi-step execution that cannot be reduced to a deterministic action. Agents handle ambiguity; action nodes do not.
DATA
Transform Node
Reshapes, filters, enriches, or reformats data as it flows through the pipeline. Map fields, apply expressions, merge objects, extract nested values, or call a lookup to add external data to the payload.
USE WHEN
The data coming from one node doesn't match the shape the next node expects. Transform nodes are the glue layer between connectors with different schemas.
ITERATION
Loop Node
Iterates over a collection — an array, a paginated API result, a list of records — and executes the inner node sequence for each item. Supports sequential and parallel iteration with configurable concurrency limits.
USE WHEN
You need to process multiple records, messages, or items through the same logic. Loop nodes prevent you from building repetitive manual sequences for batch operations.
CONDITION
Condition Node
A lightweight single-path gate that either passes or stops the flow based on a boolean evaluation. Simpler than a Decision node — no branching, just a pass/fail gate. Useful for validation and guard logic.
USE WHEN
You want to halt the flow if a condition is not met, without routing to an alternate path. Pair with error handling to define what happens on a failed condition.
TERMINAL
Output Node
Defines the terminal state of a flow or branch. Writes results to a target system, returns a response to the trigger source, emits a signal for trigger chaining, or logs a structured result to the audit trail.
USE WHEN
The flow has completed its logic and needs to deliver a result. Every completed flow execution should pass through at least one Output node.
COMPOSING NODES
Nodes compose into
complex logic.
A single node does one thing well. Chain seven together and you have a complete automation pipeline: scheduled, data-fetching, iterating, intelligence-analyzing, conditionally routing, and delivering results to the right system.
The example on the right shows a complete daily review flow built from six nodes. It runs on a schedule, processes every relevant record through an AI agent, routes based on the agent's score, and writes the result — all without human intervention.
EXAMPLE: DAILY ACCOUNT REVIEW FLOW
Schedule Trigger
trigger
Fetch Records
action
Loop: Each Record
loop
Analyze with Agent
agent
Decision: Score > 80?
decision
Update CRM / Log
output
FAQ
Common questions about Flows Nodes
A node is a discrete unit of work in a Flows workflow. Each node performs a specific function: executing an action, evaluating a condition, calling an AI agent, transforming data, iterating over a collection, or emitting an output. Nodes are connected on the canvas to define the flow of logic.
Action nodes execute deterministic, pre-defined operations against external systems — like updating a CRM record or sending a notification. AI Agent nodes invoke a Maxx Stacks AI agent, which can reason, plan, and execute multi-step tasks. The agent's output becomes the input to the next node in the flow.
Yes. Flows supports arbitrary nesting of nodes. A Loop node can contain Decision nodes, which can branch into additional Action or Agent nodes. Complex multi-step iteration logic is fully supported on the canvas.
Output nodes define the terminal state of a flow or branch. They can write data to a connected system, return a response to a triggering API call, emit a signal to another flow via trigger chaining, or log a result to the audit trail.
Yes. Decision nodes create branching paths, and each branch can have its own Output node. A single flow can produce different outcomes for different conditions — for example, routing high-value decisions to a human review output while auto-processing standard cases.
GET STARTED
Start composing your first flow.
Request access to the Flows Builder and put these node types to work on your most important automation challenges.