Wanderer Documentation

Learn how to build your first flows

Learn how ro embed the Wanderer chat widget into your website

Learn how to connect your own hub instance to the Wanderer Flow Builder.

Displays a permanent visible information inside the interactive area of the chat.

Displays a button that emits a very short signal once it has been clicked.

Send prompts to OpenAI's ChatGPT API and use the response dynamically in your flow.

Clears the chat if reached

A comment node. This one does nothing. It's useful if you want to explain things in detail in the flow.

This node doesn't do anything special. Use it to forward signals, bundle them, or collect data.

Check if a text contains specific words

Counts its own activations

Will finish a task

Send emails directly from your flow.

Fetch data from an API

Will finish a race

Displays a form in the interactive part of the chat. Requires connected form input nodes and optionally a submit button.

Connect inputs to form nodes to display input fields

Defines JSON data

Jumps to a flow by a given URL

Send prompts to browser native llm and use the response dynamically in your flow.

A manageable list of numbers, texts or data

Fires a message to the chat

Calls the next item of a list node

Defines or calculates new numbers

Will be traversed only once per session

Calls the previous item of a list node

Send data to your local printer

Displays a free type prompt

Ask a question in the chat. Requires connected suggestion nodes, which are displayed as buttons or checkboxes.

This is a task queue. It manages tasks.

Start a race - the first racer node wins

A racer node must be assigned to a race.

Reflect the current graph structure

Select from array

This is the starting node of every flow. Select this node and begin adding your first nodes. Metadata for your flow is also stored here.

Watch and reacts to changing states

Submits the connected form

Connect suggestions to questions to display answer options

A switch node can be on or off. Switch this node using call edges or button nodes.

This is a task. Connect it to a task queue.

Defines or composes texts together

Throw information back to the try node.

This node is triggered after a certain time has elapsed

Try to find a way forward.

This edge is not part of the normal traversal. It just calls state methods on other nodes.

This edge may activate the target node if its optional condition is true when traversed. Optionally it can carry fluid data to the target node.

This edge must be traversed for the target node to activate. If a condition is defined, it must evaluate to true. Optionally it can carry fluid data to the target node.

This edge does not activate the target node on its own. Instead, it prevents activation if it is traversed and its optional condition evaluates to true.

This edge is not part of the normal traversal. It just pushes fluid states to other nodes. The states will disappear if the edge becomes inactive.