Connectors
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.
The three connector shapes
Section titled “The three connector shapes”| 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) |
Every connector
Section titled “Every connector”Two things every connector shares
Section titled “Two things every connector shares”Pipelines (targetTypes)
Section titled “Pipelines (targetTypes)”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.
The live-vector guard
Section titled “The live-vector guard”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.
Recurring sync
Section titled “Recurring sync”Set autoSync with a cadence in minutes (15-minute floor, default 1440 =
daily):
divinci connectors settings wordpress --auto-sync on --cadence 1440How 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.
See also
Section titled “See also”- RAG Knowledge Base — the vectors these connectors ingest into.
- MCP tool catalog —
connector_list,connector_sync,connector_statusand friends for agentic IDEs. divinci rag crawl— a one-shot crawl with no recurring connector behind it.