Node Directory
Last updated
The Node Directory provides an overview of all available nodes in Decimal and how they are used to build automation workflows.
Nodes are the fundamental building blocks of every workflow. Each node represents a single, well-defined action that can be composed with others to create reliable, production-ready automation.
A node is a modular unit of functionality that performs a specific task within a workflow.
Examples of node responsibilities include:
Triggering workflow execution
Connecting wallets
Transferring funds
Fetching external data
Executing logic and conditions
Running custom code
Nodes are designed to be predictable, reusable, and easy to configure.
Nodes execute as part of a workflow in a defined order.
Each node:
Accepts inputs (static values or variables)
Executes a specific operation
Produces outputs that can be passed to downstream nodes
This model allows workflows to remain flexible while preserving clarity and control.
Nodes in Decimal are grouped by functionality to make discovery easier.
Trigger nodes define when a workflow starts. Every workflow begins with exactly one trigger node.
These nodes handle blockchain interactions such as wallet connections, message signing, and fund transfers.
Used to fetch and process off-chain data from external APIs and services.
Nodes that control execution flow, including conditional logic and variable handling.
Nodes that allow custom logic through code execution when predefined nodes are not sufficient.
Each node includes a configuration panel where you can:
Define required inputs
Select connections or credentials
Reference variables from previous steps
Control execution behavior
Configuration is validated before execution to reduce runtime errors.
Nodes are designed to be fully composable.
You can:
Reuse the same node across multiple workflows
Combine nodes in different sequences
Extend workflows without breaking existing logic
This makes it easy to iterate and scale automation over time.
Nodes report execution status and outputs during runtime.
This allows you to:
Identify failures quickly
Inspect node-level inputs and outputs
Debug workflows efficiently
Clear execution boundaries help isolate issues without impacting unrelated steps.
The Node Directory includes detailed documentation for each supported node, including:
Purpose and behavior
Required and optional inputs
Outputs and variable references
Common usage patterns
Use the sidebar to navigate to individual node pages for in-depth configuration details and examples.
Last updated