Skip to main content
The File Store is your workspace’s own storage. Open it from the navigation bar. Files and folders here belong to the workspace rather than to any one workflow, so anything put there is available to everything else you build. Four things write into it: you, by uploading; workflows, through the File Store node; Miraxa, when you ask it to save something; and chat, when you save an attachment out of a conversation. They all land in the same place, so a file a workflow produced on Monday is the same file you can download on Tuesday.

​
What you can do

Upload and organise

Upload files, create folders, and move, rename or delete both.

Feed a workflow

Read a stored file into a run and pass it to a connector, or save a run’s output back.

Save from a conversation

Keep an attachment you sent to Miraxa, or something it produced, instead of losing it with the chat.

Share across workflows

One price list or template, referenced by every workflow that needs it, rather than a copy in each.

​
Using it from a workflow

The File Store node gives a workflow the same operations as the page: list, get, save, move, rename and delete, for files and folders. Files a workflow saves appear here immediately.
File content never passes through the workflow history. A Get step outputs a small content reference, and the platform swaps the real bytes back in at the point they are used. That is what lets a run move a large file without carrying it through every step.
A common shape is a scheduled run that produces something and files it: a schedule trigger, an agent step that writes a summary, then a File Store step that saves it under a dated name.

​
Limits and rules

  • Storage counts against your plan’s quota. Files saved by workflows count the same as ones you upload.
  • Directly executable file types are refused, whether uploaded by hand or written by a workflow.
  • Name collisions are handled per save: keep both and add a number suffix, overwrite, or fail the step. Overwrite only removes the old file once the new one is safely stored.
  • The File Store is per workspace. It is not shared across workspaces, and nothing in it is reachable from another one.
  • File Store node for the workflow operations and their outputs
  • Operator Mode, which can read and write here while it works
  • Miraxa for saving attachments out of a conversation