Skip to main content
Destinations are target systems where enriched metadata and document data can be exported. While Data Connectors bring documents into the platform, Destinations push enriched data out to vector databases, document management systems, and databases for downstream applications.

Supported Destinations

PostgreSQL

Relational database with vector support for hybrid search.

SharePoint

Enrich original documents with metadata columns in Microsoft 365.

OneDrive

Push enriched documents and metadata to OneDrive libraries.

Amazon S3

Write enriched output to S3 buckets.

Google Cloud Storage

Write enriched output to GCS buckets.

Qdrant

Serve curated chunks to RAG pipelines via slice export.

Configuration Details

See the Integrations Overview for the complete matrix of sources, destinations, and supported file types.
To export a data slice into a vector database (e.g. Qdrant) for RAG pipelines, use client.data_slice.export_vdb(...). See Data Slices.

Export Options

Export Processing:
  • Small Exports (< 100 files): Processed synchronously with immediate results
  • Large Exports (≥ 100 files): Processed in the background with progress tracking via tracker_id

How Destinations Work

1

Create a Destination

Configure the target system with the required credentials.
2

Select Export Options

Choose what data to export (file-level, chunk-level, specific tags).
3

Choose Metadata Format

Decide between column store (separate columns) or JSON store (single JSON column).
4

Run Export

The platform sends enriched data to your destination system.

Python SDK


API Reference

Create Destination

Create a new destination

List Destinations

List all your destinations

Delete Destination

Remove a destination

Export to Destination

Export enriched data to a destination