Skip to content

Document Loader

The Document Loader brings files and folders from Google Drive into a workflow as document objects. Put it near the beginning of an ingestion flow, then send the loaded documents to a splitter or vector store to make their content searchable.

  • Category: Document Loader
  • Purpose: Loads files from Google Drive and converts them to documents
  • Inputs: trigger, input_documents, plus authentication fields
  • Outputs:
  • documents - Loaded documents
  • stats - Processing statistics
  • metadata_report - Metadata summary
  • Configuration:
  • Google Drive Links: One file or folder URL per line (required). Folder links process every eligible file inside
  • Authentication Method: service_account (robot account, correct for unattended workflows) or oauth2 (personal account, requires token refresh). Default service_account
  • Service Account JSON: Contents of the key file downloaded from Google Cloud. Visible only when Service Account is selected
  • Client ID / Client Secret: OAuth2 credentials. Visible only when OAuth2 is selected
  • Text Files / JSON / Word Documents / PDF / CSV: File types to process. Enable only what you need — CSV and JSON convert tabular data to text, which usually adds noise
  • Min Content Length: Default 100. Files shorter than this are skipped
  • Max File Size (MB): Default 100
  • Quality Threshold: 0.0–1.0, step 0.1, default 0.5. Documents scoring below the threshold are discarded
  • Enable Document Storage: Default off. Stores documents for reuse in later runs
  • Remove Duplicates: Default on. Drops duplicate documents based on content similarity
  • Usage: Requires setup on the Google Cloud side — enabling the Drive API, creating a service account, downloading its key, and sharing the target folder with that account.