Skip to main content
Figranium stores intercepted browser downloads in Cabinets: durable, installation-wide download queues that make files reusable across executions and upload steps. Every installation has a default Cabinet. New installations start with Basic Cabinet, while legacy intercepted downloads are migrated automatically so existing download links continue to work.

​
How downloads are stored

Figranium automatically monitors browser sessions for download events. When a download is triggered by a click, form submission, or navigation, the file is intercepted and routed into the Cabinet selected by the task. Task Settings exposes a Cabinet selection for downloads. If the task does not specify one, Figranium uses the instance’s default Cabinet. Cabinet items preserve their original filename and folder structure in isolated storage so files with the same name do not collide. Items also track metadata such as kind, size, timestamps, upload status, and source task/execution.

​
Waiting for downloads

Downloads are asynchronous, so a task can otherwise finish before a transfer completes. Use Wait for Downloads (wait_downloads) immediately after the action that starts the download.
  • Usage: Place it after the Click or other action that triggers the download.
  • Timeout: Configure how long the task should wait for pending downloads.
  • Default: If no timeout is set, the block uses its normal default wait.
Wait for Downloads controls execution timing. The completed file itself is persisted in the selected Cabinet, so it remains available after the execution ends.

​
Cabinets workspace

Open Cabinets from the application sidebar to manage durable downloaded files.

Organize

Create and rename Cabinets, inspect item metadata and upload state, and move workflows onto the Cabinet that fits them.

Manage items

Download individual items, clear a Cabinet, or delete selected items in bulk.

Archive

Create ZIP archives from Cabinet contents and safely extract compatible ZIP archives.

Migrate

Migrate items before deleting a Cabinet so durable files can move with your workflow.
Individual Cabinets have direct, reload-safe URLs. If a Cabinet URL points to an invalid Cabinet, Figranium falls back to the default Cabinet.

​
Reusing a download with Upload

Figranium provides two Agent actions for turning a captured download into a later upload.
Upload selects the newest unuploaded item in its source Cabinet and attaches it to the page. It supports ordinary files, ZIP archives, compatible folders, native file inputs, file chooser flows, and drop targets.An Upload action can choose its own Cabinet. If it does not, it uses the task’s selected Cabinet, then falls back to the instance default.This makes download-then-upload workflows possible without copying files outside Figranium.
Finalize Uploads marks all Cabinet items attached during the current execution as uploaded.Keeping finalization as a separate action lets a workflow attach a file first, submit or validate the surrounding form, and only mark the item consumed after that later step succeeds.An Upload action can also mark an item uploaded immediately when that behavior is preferable.
Keep finalization separate when attaching the file is not the same as successfully completing the upload flow.

​
Integrations

JavaScript SDK

The SDK exposes Cabinets through figranium.cabinets and includes typed actions.upload() and actions.finalizeUploads() helpers.

MCP

The MCP server understands task-level cabinetId, upload, and finalize_uploads, and can list or create Cabinets before building a task.

n8n

The official n8n node exposes Cabinet ID in Task Create and Update so workflows can choose the task’s download Cabinet.