Busabase

Attachments & Assets

Store files and multimodal content alongside your records.

Attachments & Assets

Attachment fields let records carry images, audio, video, and documents. Files are content-addressed and de-duplicated, so the same asset is stored once and reused everywhere.

The deduped Assets library — every file stored once and reused everywhere.

The deduped Assets library — every file stored once and reused everywhere.

Editing a file's content

Once Busabase has extracted a file's text, you (or your AI agent) can fix a typo, update a paragraph, or correct a value directly — without re-uploading the whole file. Point at the exact text to replace and what to replace it with, and Busabase makes the edit and opens it as a change request, exactly like any other change: someone reviews the diff before it merges.

A couple of things to know:

  • The edit only works on a file that's in exactly one place in your workspace — if the same file is mounted in more than one Drive or Skill, Busabase asks you to sort that out first, so the edit isn't ambiguous about which copy it applies to.
  • The text you're replacing has to match exactly once — if it appears more than once, be more specific (include a bit more surrounding text) or ask for every occurrence to be replaced at once.

Reviewing a proposed content change — the same diff view used for every change request.

Reviewing a proposed content change — the same diff view used for every change request.

See also: Core Concepts · Quick Start · Change Requests

On this page