Skip to main content

Files

The Files area is where teams manage the documents and document sources that power XY workflows. In practice, it behaves less like a generic file manager and more like a workspace for document intake, synced sources, and knowledge-base content.

Interface Overview

The current experience usually includes:

  • an All documents view
  • tabs for connected storage sources such as Google Drive and OneDrive
  • upload actions for bringing new files into XY
  • sync actions for refreshing connected cloud sources

Common file sources

Direct upload

Teams can upload documents directly into XY when they want a file available right away.

Connected storage

When Google Drive or OneDrive is connected, users can work from those sources inside the Files area instead of re-uploading everything manually.

This is especially helpful when your organization already stores SOPs, forms, payer rules, or intake documents in shared cloud folders.

What teams use Files for

  • giving workflows access to source documents
  • building a knowledge base from trusted files
  • reviewing what has been uploaded or synced
  • keeping document sources organized by where they came from

Sync and source management

For connected storage sources, users may see source-specific actions such as syncing files from that provider.

Typical flow:

  1. Connect the storage provider in Integrations.
  2. Open the matching source tab in Files.
  3. Sync the source.
  4. Use those files in workflows or knowledge-base experiences.

Using files inside workflows

Files often support workflows in one of two ways:

As workflow input

A workflow reads information from a file, such as a scanned document, spreadsheet, or reference form.

As knowledge and reference material

An agent or assistant uses files such as SOPs, policies, and templates to answer questions or make better decisions.

Best practices

  • Start with a small, trusted set of folders or files.
  • Use clear file and folder names so teams can find the right content quickly.
  • Separate source documents from reference material when possible.
  • Revisit connected sources over time so workflows only use the content you still trust.