Folders

Folders organize objects within a Site. They improve navigation and team ownership without changing runtime behavior or the stable identity of the contained objects.

Separate folder trees

Flowgear maintains separate folder trees for:

• Workflows.
• Connections.
• API Keys.

A Workflow folder cannot contain a Connection, and moving between these explorers is not supported. The root of each explorer represents objects with no folder assignment.

Folder identity and paths

Every folder has a stable key, name, object type, and optional parent-folder key. The parent chain creates its path, such as /Finance/Receivables.

A folder name identifies one segment, not the full location. The same name can be meaningful under different parents, so use the full path when communicating a destination and the exact folder key when using APIs or agent tools.

Moving or renaming a folder changes the path of its descendants. It does not change the stable IDs of those folders or the objects they contain.

Using folders in Console

In an explorer that supports folders, use:

• New folder to create a child of the current folder.
• Breadcrumbs to move back through the hierarchy.
• Rename to change a folder's display name.
• Move to to move selected folders or objects within the same Site and object tree.
• Delete to remove selected content after confirmation.

Available actions depend on Folder permissions and the object-specific permissions for selected items. Console deletes selected objects before their folders so a failed object deletion does not intentionally leave orphaned content.

Folders and agents

An agent should list or resolve folders before creating or moving a Workflow. It must not invent a folder key from a name.

Flowgear's Builder tools expose canonical Workflow folder paths and exact keys. When creating a nested path, the tool can create missing parent segments. Confirm the resolved path and key before saving the Workflow, especially when similarly named folders exist.