Using Variables

Data in Fluxlix workflows flows through connections between nodes. Each node can have input and output handles — you wire them together on the canvas to pass data from one node to the next.

How data flows between nodes

Every node that produces data exposes one or more output handles on its right side. Downstream nodes have input handles on their left side. To pass data, drag a wire from an output handle to a compatible input handle.

Output and input handles are color-coded by type — string, integer, float, boolean, object, and so on. You can only connect handles of the same type. If you need to convert between types (for example, turning a number into a string), use one of the type conversion nodes in the Logic category.

When a node runs, its outputs become available to any node connected downstream.

Node outputs

After a node executes, its results are stored as named outputs. For example, a Clone Repository node might produce an output called repoPath — the local file path where the repository was cloned. You can wire that output into the next node's input to use it.

To see what outputs a node provides, select it and look at the handles on the right side of the node, or check the node's configuration panel.

Builtin context

Workflows automatically have access to context about the current run. These builtins are available as inputs throughout the workflow without needing to wire anything:

• Task/Work Item — the work item that triggered the workflow (its ID, title, status, type, priority, metadata fields)
• Project — the project the workflow belongs to (ID, name, settings)
• Repository — the repository linked to the work item (URL, default branch)

When configuring a node, you can reference these builtins in expression fields using the $ prefix:

$task.title
$task.status
$project.id
$task.metadata.repositoryId

Many nodes default their projectId input to the current project automatically, so you often don't need to set it.

Workflow variables

Use the Set Variable node to store a named value that persists across the workflow run. This is useful for carrying a computed value across branches or accumulating results in a loop.

Set a variable by giving it a name and wiring a value into it. Later nodes can read it back using a Get Variable node or by referencing $var.variableName in expression fields.

Expression fields

Some node inputs accept expressions in addition to direct wired connections. In these fields, you can type $ to open a picker that shows all available data at that point in the workflow — builtins, upstream node outputs, and workflow variables.

Tips

• Prefer wiring connections over typing expressions — the editor validates types at connection time and prevents mismatches.
• If a node's output handle is grayed out, it means the node hasn't been configured yet or the output type can't be determined.
• Use the Set Variable / Get Variable pair when you need to pass data across branches that aren't directly connected.