Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.truagents.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Summary

File sets appear to be the main way TruAgents lets teams upload collections of files that can later support AI-assisted work with richer context. This is important because it means the product does not rely only on fields and prompts. It also has a place for reusable knowledge collections.

​
Who this is for

  • Teams enriching agent behavior with uploaded material
  • Admins or operators managing shared knowledge assets
  • Anyone trying to understand how supporting documents fit into the product model

​
What the current app suggests

The File Sets area appears to support:
  • uploading files into named collections
  • filtering by state
  • searching existing file sets
  • using those sets as reusable context rather than one-off uploads
The current campaign flow also suggests file sets can be attached directly to campaigns, which makes them part of operational campaign context rather than a detached knowledge library.

​
The right mental model

  • a file is one asset
  • a file set is the reusable collection
  • the product value is in the reusable context, not just raw storage

​
How file sets fit into campaigns

File sets appear to matter most when a team wants campaigns or agent-driven workflows to have reusable supporting context. That means file sets should be thought of as:
  • reusable context for campaigns
  • shared knowledge assets across workflows
  • distinct from audience or contact imports

​
What the file-set workflow implies

The current app suggests a file set can include:
  • basic identity like name and description
  • uploaded file previews
  • deeper chunked content behind the scenes for retrieval or inspection
Simple version: a file set is not just a folder. It is a named, reusable knowledge bundle.

​
Good file-set hygiene

  • name file sets clearly enough that another teammate can reuse them
  • keep knowledge collections distinct from contact-import files
  • attach file sets intentionally where campaign context actually needs them
  • review whether an outdated file set is still appropriate before reuse

​
Common misunderstandings to avoid

  • File sets should not be thought of as simple attachments.
  • They are not the same as contact imports or data sources.
  • They belong to the knowledge and context side of the product, not the audience-data side.
  • A file set being attached to a campaign does not mean the underlying knowledge is still current or relevant.