Build your first graph from a pack

Quick steps

01Install a pack that contributes at least one graph (e.g. Gmail Triage Kit).
02Open the Hub and find the contributed graph under 'Installed packs'.
03Fork the graph — give it a name and open it in the workspace.
04Connect the input nodes to your data sources (credentials, filters).
05Run the graph manually to verify the output.
06Set up a trigger if you want it to run automatically.

The node model

Everything in [fix]net is a node. A graph is a directed acyclic graph of nodes: each node has typed input and output ports, and you connect them by drawing edges.

A pack contributes new node kinds — the templates from which you stamp out instances. When the pack is installed, those kinds appear in your node library and in any contributed graphs.

Start from a contributed graph

The fastest way to build something useful is to start from a contributed graph rather than a blank canvas.

After installing a pack, open the Hub (the left-side panel). Under "Installed packs", click the pack name. Any graphs it contributes are listed there.

Click Fork on the graph you want. Give your fork a name. The original stays untouched; your fork is what you'll edit.

Connect your inputs

A contributed graph typically has placeholder input nodes at the top — email credentials, a filter condition, an API key reference. These are intentionally left disconnected so the author doesn't bake in their own secrets.

Click an input node to open its configuration panel. Fill in your values. Secrets (API keys, OAuth tokens) are stored in the app's secure credential store — the graph only holds a reference, never the value itself.

Run the graph

Once inputs are connected, click Run in the top toolbar. The graph executes node-by-node from the sources downward. You can watch the data flow in real time: each node shows its output state (pending → running → complete or error).

If a node errors, click it to see the full error output. Common first-run errors:

Auth failure — re-check the credential reference; the token may have expired.
Type mismatch — the output of one node doesn't match the input kind the next node expects. Check the port labels.
Rate limit — an external API returned 429. Add a throttle node upstream.

Add a trigger

A manually-run graph is useful for one-shots. For recurring workflows, add a trigger node at the source end:

Schedule trigger — runs on a cron expression.
Webhook trigger — wakes the graph when an external service POSTs to a generated URL.
Event trigger — fires when another node in a different graph emits an event.

Connect the trigger's output to the first processing node. Save and enable the graph. [fix]net's scheduler will run it automatically.