Connectors reference

Bundata supports 35+ source connectors and multiple destination connectors for ingestion and delivery of smart bites. This page is a reference list; for setup and use, see the product guides.

Source connectors (examples)

ConnectorAuthTypical use
Amazon S3IAM role, access keyBuckets and prefixes; contracts, invoices, policy docs. See AWS.
Azure Blob StorageKey, managed identityContainers; same as S3. See Azure.
Google Cloud StorageService account, keyBuckets; same as S3. See GCP.
SharePointOAuth, app registrationSites, libraries, folders. Internal docs and policies.
ConfluenceAPI token, OAuthSpaces and pages. Knowledge base and runbooks.
Google DriveOAuthMy Drive, shared drives. Shared documents.
BoxOAuthFolders and files.
SalesforceOAuthAttachments, content. CRM and contract attachments.
ZendeskAPI, OAuthTickets, articles. Support and KB content.

Additional connectors (databases, messaging, other SaaS) may be available depending on your plan. Check the Platform connector picker or contact support for the full list.

Destination connectors (examples)

ConnectorUse
Vector CatalogDefault; write smart bites and embeddings to a collection for Vector Search and agents.
Amazon S3Write JSON/parquet for backup, analytics, or custom pipelines.
Azure Blob StorageSame as S3.
Google Cloud StorageSame as S3.

Custom or partner destinations may be available; see product docs.

Parameters (general)

  • Source — Connection details (endpoint, bucket/container/path), credentials (key, OAuth client, IAM role), and scope (prefixes, folders, filters).
  • Destination — Connection details, credentials, and target (collection ID, bucket/prefix, path).
  • File types — Source connectors typically respect supported file types. Unsupported files are skipped or reported in run results.

Auth patterns

  • API key — Stored securely; used in connector config. Rotate periodically. See Authentication.
  • OAuth — User or app authorizes access; tokens are stored and refreshed by Bundata where supported.
  • IAM / managed identity — For AWS, Azure, GCP; least-privilege roles for read (source) or write (destination). See cloud-specific docs: AWS, Azure, GCP.

Limits

  • Connector-specific limits (e.g. max objects per run, rate limits imposed by the third party) may apply. See Limits and quotas and connector-specific docs.
  • Source lineage — Preserve document ID and path in connector output so smart bites remain traceable. See Vector Catalog: Lineage.