How to Use Custom Nodes

In an application flow, a custom node behaves like any other node: you add it to the canvas, fill in its fields, and connect it to the rest of your logic.

What makes it different is that the node is really a reusable internal flow with a curated input form on top.

Adding a Custom Node

1. Open an application flow.
2. Add a node from the Custom Nodes section.
3. Choose the custom node you want to use.
4. Fill in the input fields it exposes.

Understanding Input Parameters

Each custom node defines its own input schema. That schema is what the calling flow sees.

Well-designed custom nodes group inputs into clear sections, such as:

• action selection
• identification or account settings
• event payload fields
• optional advanced parameters

The goal is to expose only the decisions a user should actually make, not every internal implementation detail.

What Happens at Runtime

At runtime, Fluxyn passes the configured input values into the internal custom-node flow. Inside that private flow, those values are available through the input node and can be used by downstream nodes just like any other data.

That means a good custom node can hide a lot of complexity:

• loading scripts
• preparing payloads
• branching by mode
• calling vendor APIs
• storing intermediate values

Versioning and Updates

Workspace custom nodes are versioned so application flows stay stable.

In practice:

• a flow uses the version it was configured with
• a newer custom-node publish does not silently rewrite old flows
• when an update is available, you can choose when to adopt it and test it

That lets teams improve shared logic without surprising every application that depends on it.

Important Distinction

Official vendor nodes are documented in the Integrations section and are available directly in application flows. They are separate from workspace custom nodes and do not need to be created through the Custom Nodes page.