Start here

The playground

The playground is the canvas where a workflow is built: a node palette on the left, the wired graph in the middle, and a configuration form for whichever node you click.

The playground with the Nodes palette open on the left, a wired workflow on the canvas, and a node configuration form open on the right

Screenshot to be added

Palette, canvas, node form.

The two panels

Nodes

The palette of everything you can add. What appears here depends on your plan and the module type.

Workflow Nodes

What is already on this canvas. Useful once a workflow grows past a screenful — click an entry to jump to it.

Working the canvas

To…	Do this
Add a node	Drag it from the Nodes palette onto the canvas
Move a node	Drag it
Move the whole workflow	`Ctrl` + click and drag the canvas
Open a node's form	Click the node
Edit or remove a node	Right-click it for the context menu
Connect two nodes	Click the output connector, then the input connector
Remove a connection	Right-click the wire

The playground itself prints the three that are easy to forget: Ctrl + Click to move workflow. Right click on node to view options. Right click on a wire to remove connections.

The four connectors

Nodes do not all connect the same way. A node can expose up to four kinds of connector, and using the right one is what makes a workflow behave:

Connector	Means
Input	Data flowing in from the previous node
Output	What this node produces, for the next node
Tool	A capability an AI node may choose to call
Attachment	A resource carried alongside — memory, a knowledge base

Wiring a tool node into an AI node's input instead of its tool connector is the most common first mistake. On the input the tool runs every time; on the tool connector the model decides when to use it.

The node form

Clicking a node opens its configuration. Every form is different, but they share a shape:

Parameters — the node's own settings.
Input — only shown if the node accepts input. This is where template expressions go.
Response JSON Keys — the keys available from the connected node's output.

You can drag a key from Response JSON Keys and drop it into an input field, and Flux writes the template expression for you. That is the fastest way to build a workflow without memorising the template syntax.

Everything else in the module

Feature	What it is for
Credentials	The credential store for this project's API keys
Templates	Start from a saved workflow, or save this one
Chat logs	What was actually said in each session
Compiled logs	What each template resolved to at run time
Usage	Triggers, tokens, sessions and cost for this module

Your workflow script and your credentials are both stored encrypted. Referencing a key from the credential store rather than pasting it into a node keeps it that way.