Document

Static Drive

Static Drive is persistent file storage managed by Builders. Files remain available after a workflow run ends and can be organized in personal or team-owned drive scopes.

Static Drive scope, file actions, breadcrumbs, and storage quotaStatic Drive scope, file actions, breadcrumbs, and storage quota

Choose a drive scope

Open Static Drive and select the required personal or team drive. The scope controls who owns the files and which projects can use them.

  • Use a personal drive for files maintained by one user and consumed by compatible personal projects.
  • Use a team drive for files that must remain available to shared team workflows and maintainers.
  • Confirm the selected scope before uploading. A matching filename in another scope is a different resource.

The quota indicator shows current use and the drive limit. Uploads and workflow writes can fail when the scope has insufficient capacity.

Organize files and folders

Use New folder, New file, Upload file, or Upload folder from the current breadcrumb location. Folder action menus expose the same create and upload actions for that folder.

Open folders from the list and use the breadcrumb to return to a parent. Items are draggable, so a file or folder can be moved into another visible folder. Check the destination path after moving an item because workflows resolve Static Drive files by path.

Choose names that remain meaningful outside one run, for example:

event-assets/registration-confirmation.html
event-exports/2026-08/attendees.csv

Avoid placing unrelated files at the root. Stable folders make access rules, cleanup, and workflow path templates easier to review.

Preview and edit supported files

Open a file's Preview / edit action. Text-like formats open in an editor and can be saved back to the same path. Other previewable formats use the supported viewer for that file type.

Treat edits as changes to a shared runtime dependency. Before replacing a template or configuration file used by a published workflow:

  1. Identify dependent pipelines.
  2. Keep a backup under a versioned path when rollback matters.
  3. Edit or upload the replacement.
  4. Run a controlled workflow test.
  5. Remove the old copy only after dependents have moved.

Delete actions are permanent from the workflow's perspective. A block referencing the removed path fails on its next run.

Use Static Drive in a workflow

Select Static drive in Read File or Save File. Internal Builders drives do not require an integration.

Use a literal path for a shared asset:

event-assets/registration-confirmation.html

Use a template path when every run should produce a separate durable artifact:

event-exports/{{run.id}}.json

Save File replaces an existing destination. Include {{run.id}}, a business identifier, or another unique segment when replacement is not intended.

Handle quota and access failures

  • The file is not found: inspect the rendered path, scope, case, and folder hierarchy.
  • The drive is full: remove obsolete files or write to another appropriate persistent store; do not retry unchanged input indefinitely.
  • The block cannot select the drive: verify that the project and drive share a compatible personal or team owner.
  • A moved file breaks a run: update every block that stored the previous path.
  • A team member cannot edit a file: verify team membership and the permissions attached to the owning team.
  • Concurrent runs replace one file: generate unique paths or deliberately serialize the writes.

Next steps