Connectors
Connects to what you already run.
Your knowledge stays where it lives. Connectors run inside your infrastructure, keep content in sync, and carry each source’s permissions across.
- Ready today
- 27 connectors
- Custom
- Anything with an API, database or export
- Permissions
- Carried from each source
- Runs in
- Your infrastructure
In short
DeepVox connectors link on-premise AI to the systems that hold your knowledge, such as SharePoint, Google Drive, Confluence, Slack, Jira and Salesforce. They run in your environment, sync continuously and respect each source’s permissions, so answers only use content a person is allowed to see.
Documents & files
Google Drive
Docs, Sheets and Slides · PDFs and uploaded files · Shared drives
Details →SharePoint
Sites and pages · Document libraries · Lists
Details →OneDrive
Personal and shared files · Office documents · PDFs
Details →Box
Folders and files · Shared collaboration spaces · PDFs and Office documents
Details →Dropbox
Folders and files · Team spaces · PDFs and Office documents
Details →Network file shares
SMB and NFS shares · Scanned documents (OCR) · Legacy Office files and PDFs
Details →Wikis & knowledge bases
Notion
Pages and sub-pages · Databases · Team wikis
Details →Confluence
Spaces and pages · Attachments · Comments
Details →BookStack
Shelves, books and chapters · Pages · Attachments
Details →XWiki
Wiki spaces and pages · Attachments · Structured application data
Details →Guru
Cards and collections · Verified knowledge · Boards
Details →Email & chat
Outlook / Exchange
Mailboxes you approve · Shared mailboxes · Attachments
Details →Gmail
Mailboxes you approve · Labels · Attachments
Details →Microsoft Teams
Channels you approve · Messages and files · Meeting transcripts where enabled
Details →Slack
Public and approved private channels · Threads · Shared files
Details →Tickets & work
Jira
Issues and comments · Projects and epics · Attachments
Details →ServiceNow
Incidents and requests · Knowledge articles · Change records
Details →Zendesk
Tickets and conversations · Help Center articles · Macros
Details →GitHub
Repositories and READMEs · Issues and pull requests · Wikis
Details →Asana
Projects and tasks · Comments · Attachments
Details →CRM & business systems
Salesforce
Accounts, contacts and opportunities · Cases · Notes and attachments
Details →HubSpot
Contacts and companies · Deals · Tickets and notes
Details →SAP
Business documents and master data via APIs · Purchase orders and invoices · Reports
Details →Dynamics 365
Accounts, contacts and cases · Opportunities · Notes and activities
Details →Databases & APIs
PostgreSQL
Tables and views you approve · Text columns for search · Structured fields for filters
Details →SQL Server
Tables and views you approve · Text columns for search · Structured fields for filters
Details →REST APIs
Any internal or vendor API · JSON records · Webhooks for change events
Details →FAQ
Questions, answered.
Do connectors respect our existing permissions?
Yes. Each connector carries the source system’s permissions, so answers only use content the person can already open.
What if our system isn’t listed?
If it has an API, a database or an export, we build a connector during customization, and the code is yours.
Do we need to move our data?
No. Content stays in the source system; the connector syncs an index inside your infrastructure.
Related
Knowledge & retrieval
Cited answers over connected content.
Learn more →Access control
Permissions end to end.
Learn more →Deployment
Where the connectors run.
Learn more →Start with two weeks of evidence, not a sales call.
A fixed-price discovery sprint, credited against whatever comes next. Or write to sales@deepvox.ai.