> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/nodes/editor.md).

# Node Overview

In FLORA, Nodes are the core creative units — connect them to build your workflows.

FLORA operates on a node-based system where users can interconnect different AI models for greater creative control.

Read more about our approach in [Our Product Philosophy](/getting-started/publish-your-docs/our-product-philosophy.md).

In the next few sections, we'll explore the core building blocks for your work in FLORA — the Text Node, Image Node, Video Node, Audio Node, and 3D Node — and see how each one can be utilized to achieve your desired output.

### Here's an overview of our Nodes:

{% stepper %}
{% step %}
[**Text Node**](/nodes/text-node.md)
{% endstep %}

{% step %}
[**Image Node**](/nodes/image-node.md)
{% endstep %}

{% step %}
[**Video Node**](/nodes/video-node.md)
{% endstep %}

{% step %}

### [Audio Node](/nodes/audio-node.md)

{% endstep %}

{% step %}

### [3D Node](/nodes/3d-node.md)

{% endstep %}
{% endstepper %}

To learn how running, generation status, and generation history work across all nodes, see [How Nodes Run](/nodes/how-nodes-run.md).

## Node Toolbar

A toolbar appears upon hovering on nodes of all modalities, above each node. The toolbar is contextual and contents vary depending on the node type.

<figure><img src="https://526296967-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWthH0GpcCHwVdtbvahZS%2Fuploads%2Fwvzor1r9Zw7oFySLYWcK%2FCleanShot%202025-09-22%20at%2015.54.32%402x.png?alt=media&amp;token=42a7e1d1-5f2e-4308-942f-fdf8df244b02" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/nodes/editor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.