Core Concepts
Understand the main ideas you will see everywhere in Fluxyn.
Applications
An Application represents the place where a flow will run, usually a website.
It stores things like:
- allowed origins
- trigger settings
- runtime settings
- publish state
Flows
A Flow is the logic you build in the canvas.
A flow starts with a trigger and then moves through other nodes.
Custom Nodes
A Custom Node is a reusable flow that behaves like one node inside another flow.
Use a custom node when you want to hide complexity behind a simpler setup form.
Runtime
The Runtime is the script that runs Fluxyn on the page.
It listens for configured signals, processes flows, and keeps a small page-state snapshot that later events can use.
Events
An event is the payload that starts a flow, such as:
- a click
- a route change
- a timer tick
- a named
dataLayerevent
In flows, you will often use:
$for the current merged page-state snapshot$eventDatafor the raw current event only$inputfor the previous node output$consentfor the current consent snapshot
Consent and held events
Fluxyn can keep processing paused until your page is ready.
This is useful when consent or another readiness signal must arrive before normal events should run.
What to do next
- Follow First 10 minutes
- Read Flow builder basics