Files

The Files section shows the workspace’s file storage — a real tree of folders and files. Three sources feed it: what you upload by hand, what workflow nodes write, and attachments arriving from chat and Telegram.

Moving around the tree

Clicking a folder opens it; clicking a file selects it for preview. Inside a folder the first row is .., one level up. The breadcrumbs in the toolbar say the same thing: “root” and every segment are clickable.

The list sorts by name, size or modification date — click a column header, click again to reverse it. Folders always come before files, whichever column and direction you pick. On narrow screens the Type and Modified columns collapse, and the preview panel is dropped entirely.

Uploads and folders

There are two ways to upload: the “Upload” button (several files at once are fine) or dragging files in from your file manager onto the listing. Both put the files into the current folder — the one shown in the breadcrumbs.

“New folder” asks for a name and creates the folder inside the current one.

To move a file, drag its row onto a folder row. Only files can be dragged: folders are not moved as a whole.

A single upload is capped by a deployment setting (50 MB by default); anything larger is rejected with 413.

Preview and download

The right-hand panel shows the file name, size, MIME type and — when it is known — where the file came from: upload for a manual upload, generated for files produced by nodes, telegram for bot attachments.

What gets drawn depends on the type:

• text (text/*, JSON, XML, YAML, CSV) — the content, first 100,000 characters;
• images — the picture itself;
• audio — a plain player;
• anything else — a “Preview unavailable” note.

The “Download” button works for every file, including the ones that cannot be rendered.

Quota

The line under the toolbar reports the file count and the bytes used. The progress bar only appears once an operator has set a storage quota: at zero (the default) there is no ceiling and no bar.

Deletion

The trash icon on a file or folder row deletes it after a confirmation. Deleting a folder takes its contents with it.

How this connects to workflows

This is exactly the storage the ws_store_config node points at: it aims the file nodes at the current workspace’s store and needs no credentials. Wire it to file_read, file_write or file_glob — files written by a workflow show up in this tree, and files uploaded here become visible to workflows.

Chat-session attachments land in subfolders named sessions/<id>, so they sit next to everything else and can be deleted like any other file.

Where to next