Skip to content

Connectors

Copy page

A connector is a standing link between a data source you own and a Divinci workspace. Once connected it ingests into a RAG vector (and optionally the fine-tuning pipeline), on demand or on a recurring schedule, without anyone re-uploading files.

Fourteen providers ship today. They differ in one way that matters more than any other — how you connect them — and that decides how much of the job the CLI can do.

| Shape | Providers | Connect from | | --- | --- | --- | | Config-only — the connector is its configuration; no secret to hand over | Web Crawl, WordPress | ✅ CLI, API, web app | | Credential — you paste a key/secret we validate before storing | AWS S3, Cloudflare R2, Google Cloud Storage, Recall.ai, Practice Better, Local Files | API, web app | | OAuth redirect — the provider's own consent screen | Google Drive, Gmail, Google Calendar, Dropbox, Notion, Zoom | Web app (a human must click Allow) |

A connection processes into rag, into fine-tuning, or both. Selecting fine-tuning always adds RAG — the SFT pipeline consumes RAG-processed chunks, so it cannot run alone.

If a connector's target vector is attached to a published release, chunk writes to it are rejected. The rejections are recorded, not thrown, so the sync reports success and nothing new becomes retrievable — the single most common "it ran but changed nothing" report.

Use draft-and-swap (--swap on the CLI, swapOnSuccess in the API/web form): the sync ingests into a fresh draft vector and atomically repoints your live release(s) at it only once the run succeeds. Both the web-crawl and WordPress forms default it on for exactly this reason.

Set autoSync with a cadence in minutes (15-minute floor, default 1440 = daily):

Terminal window
divinci connectors settings wordpress --auto-sync on --cadence 1440

How a change reaches us differs by provider:

| Mechanism | Providers | Latency | | --- | --- | --- | | Push webhook | Google Drive, Gmail, Google Calendar (per-connection watch channels, auto-renewed), Zoom (app-level) | near real-time | | Polling | everything else — and any webhook provider whose channel lapsed | the connection's cadence |

A failed webhook registration degrades to polling rather than to silence.

  • RAG Knowledge Base — the vectors these connectors ingest into.
  • MCP tool catalogconnector_list, connector_sync, connector_status and friends for agentic IDEs.
  • divinci rag crawl — a one-shot crawl with no recurring connector behind it.