Files & Storage

Workspace storage gives your workflows a place to keep files: attachments captured from a form, documents a run generates, assets you fetch from an API. Files live in your workspace alongside your tables and are addressed by a key, a path-like string you choose (for example invoices/2026-q1.pdf).

#What files are for

• Attachments: a file field on a table stores its upload in workspace storage.
• Workflow artifacts: save something a run produces (a rendered document, a transformed export) so a later step or another workflow can pick it up.
• Fetched assets: pull a file from a web link and keep a durable copy under a key you control.

#Working with files in workflows

Three file nodes move files inside a workflow:

Save File to Storage takes a source (a web link, raw text, or uploaded file data) plus the key to store it under, and returns the file’s URL, key, and size. Get File URL resolves a key to the file’s link and metadata: it returns the URL and details, not the file’s contents. Delete File removes the file permanently and can’t be undone.

#URL access

Stored files are served from a stable public link. Anyone with the URL can fetch the file, so treat the link itself as the access control: hand it only to the systems and people that should see the file. The link doesn’t expire on its own; a file stays reachable at its URL until you delete it with Delete File.

#Storage metering

Files count toward your plan’s included storage allowance, combined with your table rows into a single number. Saving, fetching, and deleting files is free: you’re only billed for what’s stored, and only for the amount above your included allowance. See Data storage for allowances, per-GB overage rates, and how the spending cap bounds it.

#Related

• Data nodes : the file nodes in the builder
• Tables : the file field type
• Billing : storage allowances and rates