What is a Flow?
A flow in Noxus is a visual representation of a process, built using nodes connected together to form a directed graph. Each node represents a specific operation, and the connections between nodes show how data flows through the process. This visual approach makes it easy to:- Design Complex Processes: Visually map out your automation logic
- Understand Data Flow: See exactly how information moves through your system
- Manage Dependencies: Clearly define relationships between operations
- Handle Errors: Implement robust error handling and recovery
- Monitor Progress: Track execution status and performance
Think of a flow as a blueprint for automation. Just as an architect uses
blueprints to show how different parts of a building connect and function
together, a flow shows how different operations connect and work together.
Key Concepts
Flow Modules
Nodes are the basic building blocks of a flow. Each node is a specialized component that performs a specific function in your automation process. Think of nodes as the individual tools in your automation toolkit, each designed for a particular task. Triggers allow your flows to run automatically based on specific events.Inputs & Outputs
Handle data flow in and out of your flows with support for text, files,
images, and structured data
Nodes
Explore AI Processing, Data & Files, and Logic & Control nodes in one place.
Integrations
Connect with external services and APIs through pre-built integration nodes
Triggers
Automate flow execution with events, schedules, and external notifications
These nodes can be combined to create powerful automation solutions. Each type
is covered in detail in the Flow Modules
section.
Data Flow
Connections between nodes define how data flows through the flow. These connections are more than just lines - they represent the paths that data takes as it moves through your automation process.| Feature | Description | Benefits |
|---|---|---|
| Typed Data | Ensures data compatibility between nodes with automatic validation | Prevents runtime errors and maintains data integrity across the flow |
| Branching | Allows for conditional processing paths based on data content | Enables dynamic flows that adapt to different scenarios |
Subflows
A subflow is a saved flow that you can reuse as a single node inside other flows. When saved, it becomes a modular building block with clearly defined inputs and outputs, so you can drag it into new flows, map parent inputs to its parameters, and expose only the results you need. Subflows encapsulate their logic, run in their own execution context, and make complex automations scalable, consistent, and easy to maintain across projects.Running a Flow
- 🖱️ Direct Call
- ⚡ Triggers
- 🔌 APIs
- 🤖 Co-workers
The platform interface provides an intuitive way to execute and test your
flows. You can:
- Instantly run flows with custom input parameters
- Monitor execution progress in real-time
- Build and access detailed logs for debugging
- Get immediate visual feedback during development
This method is particularly useful for iterative development and on-demand
processing where immediate feedback is essential.
Next Steps
- Learn about different node types
- Explore flow triggers
- Understand how to integrate AI models