Workflows Overview
Workflows let you automate repetitive development tasks without writing any code. Using a visual node-based editor — similar to tools like Unreal Engine Blueprints — you connect blocks of logic on a canvas to define what happens and in what order.
A workflow might automatically move a work item to "In Review" when a pull request is opened, assign a task to an AI agent when a story is created, or send a notification when a build fails. Complex multi-step sequences that would otherwise require custom scripts can be assembled visually in minutes.
How workflows fit into Fluxlix
Each workflow belongs to a project and can be assigned to one or more work items as an automation template. When a workflow is triggered, it runs through your node graph step by step, reading and writing data along the way.
Workflows can also be triggered on a schedule, by an incoming webhook, or directly from a chat session — not just from work item events.
Node categories
Every piece of logic in a workflow is a node. Nodes are organized into five categories:
- Triggers — The starting point of every workflow. Defines what event causes the workflow to run.
- Control — Manages the flow lifecycle: ending a run successfully, raising errors, adding delays.
- Actions — Performs real work: running AI prompts, making git commits, sending notifications, updating work items.
- Decisions — Pauses execution to wait for human input, review, or a response in chat.
- Logic — Pure computation: conditionals, loops, math, string manipulation, and data transformation.
Reusable building blocks
Frequently used sequences can be extracted into functions and macros, making it easy to share logic across multiple workflows in a project. See Functions and Macros for details.
Next steps
- Creating Workflows — Build your first workflow in the editor
- Node Library — Explore all available node types
- Triggers — Understand how workflows start
- Using Variables — Pass data between nodes