Skip to content
One platform. From customer conversation to completed work.Take a closer look
Documentation menu

Storage

Private files for your business.

Keep files in buckets with version history. NodeHub checks access on every request, and your workflows, agents and tickets use the same files.

Product preview: workspace access opens at launch. Follow the launch.

What you can use it for

  • Files your team keeps for a business, organized in buckets and folders
  • Files from a ticket that you want to keep after the conversation
  • Files a workflow lists, reads, writes, checks or deletes
  • Text an AI agent saves, only in the buckets you choose for it
  • Starting a workflow as soon as a file arrives
Open Storage Automate a bucket

Create a bucket

  1. Open Storage.As a workspace owner or administrator, open Storage and confirm the active business.
  2. Choose New bucket.Use up to 80 lowercase letters, numbers, dots, hyphens and underscores, starting with a letter or number, such as invoices.
  3. Upload a first file.Choose Upload file. Name it with a path, such as 2026/october/receipt.pdf, to keep related files together.

Each bucket belongs to one business. Owners and administrators can use every bucket in it. Members with the Agent role see only the buckets they have been given access to.

Upload and manage files

NodeHub checks the bytes it receives against the file before it publishes a new version. Filter a bucket by path prefix, such as invoices/, to find files.

  • Replace a fileReplacing a file adds a new version. Version history keeps the earlier versions, and you can download any of them.
  • Delete a fileDeleting removes the file from the bucket. Its space is released once the stored bytes are deleted.
  • Pinned filesA file linked to a table record or a ticket, or held by a workflow run, cannot be deleted. Remove the record or ticket link, or wait for the workflow's retention to end.

Use files in a workflow

Add the trigger A file is added to a bucket to start a workflow when an upload finishes. Choose the bucket and, if you want, a folder prefix. The run starts as the member who uploaded the file.

The Storage step group has List stored files, Read stored file, Store workflow file, Verify stored file integrity and Delete stored file. Each step uses the bucket access of the member who started the run.

Automate a bucket

In Storage, choose Automate on a bucket, or on a file to use its folder. Pick a template. It installs as a draft that already starts when a file is added there:

  • Start when a file is added
  • Add each new CSV file's rows to a data table
  • Summarize each new PDF with AI
  • Keep a log of every new file

Review the draft in the builder, run a test, then publish it.

Give an agent files

Two agent tools work with Storage. Save text to storage saves up to 256 KB of text as a new plain text file, only in the buckets you choose for that agent. It never replaces an existing file. Read permitted stored text reads only the text files you allow.

Set up an agent

Keep a file from a ticket

Open the ticket's Stored files panel and choose Save a ticket file to Storage. Pick the file, a bucket and a name. NodeHub stores it as a new file and links it back to the ticket.

Limits

  • Storage by planFree includes 1 GB. Each paid member adds 10 GB, shared by the team. See Plans & billing.
  • File sizeA single file can be up to 1 GB.
  • Your workspaceStorage shows what is used, what is reserved by uploads in progress, your workspace's capacity and its largest file size.