File Store

Unstructured file collections — upload, organize, and reference files from workflows

File Store is where your agents and workflows keep arbitrary files — PDFs, images, CSVs, HTML exports, generated artifacts, anything that doesn’t fit neatly into a database row. Files live in collections, and each collection is separately shareable. Every file is addressable by URL and readable by the built-in File Storage MCP server.

Find it under Tools → File Store.

The File Store List

Each row is one file collection. The layout mirrors Database:

Column	Description
Name	Collection name.
Max	Max file count allowed in the collection.
Current	Current file count.
Created by	Email of the creator.
Actions	Share, Rename, More (Delete, Export).

Click + New File Store to create a new collection. The create dialog is the same “New Resource” dialog used by Database, but with the Database Type field pre-set to File Storage.

Inside a Collection

Clicking a collection row opens its detail view.

Toolbar controls:

Button	Action
Filter by filename or tag	Client-side search.
Refresh	Re-fetch the list.
Upload	Add one or more files.

Each row shows:

Column	What you can do
Name	Click to preview the file.
Custom Tags	Free-text tags you can apply for grouping.
Type	Inferred MIME/format (e.g. HTML Document, PDF, CSV).
Public	Yes/No — whether the file has a public URL.
Created / Last Updated	Timestamps.
Actions	Edit metadata, Delete.

Select multiple files with the checkboxes to bulk-delete, bulk-tag, or bulk-toggle public.

Uploading Files

Click Upload to attach files from your local machine. Files are stored in the collection and get a stable URL you can reference from workflows (and, if made public, share externally).

Typical upload patterns:

• Drag and drop — drop one or many files onto the Upload button.
• Workflows write directly — workflow steps (e.g. code execution, scraper, document processing) can emit files straight into a specified collection without a manual upload.

Sharing

Share per collection via the Share action. ACLs match Database and Connections:

• Read — list and download files.
• Write — upload, rename, tag, delete.
• Admin — share further.

Using File Stores in Agents and Workflows

Reference File Store collections through the built-in File Storage MCP server. Tools include listing collections, listing files, reading file contents, creating files, and moving files between collections.

Common recipes:

• Download every attachment from a trigger email into a collection.
• Save screenshots or PDFs generated by workflows.
• Stage exports from one service (e.g. a CSV pulled from Salesforce) before feeding them into another.

Notes

• File Store is builder-only.
• Files can be made public on a per-file basis — the generated public URL is stable until you unshare.
• Large uploads are chunked automatically; the UI shows per-file progress.
• For document retrieval (question-answering over a set of files), use Knowledge Base instead; it indexes content for semantic search, while File Store just stores the raw files.