Connectors Overview

​

Available Connectors

Google Workspace

Drive, Docs, Sheets, Slides, Gmail, and Google Chat

Google Ads

Account structure, campaigns, ad groups, keywords, and live reports

Microsoft 365

OneDrive, SharePoint, Outlook, Calendar, and Teams

Atlassian

Confluence wikis and JIRA issues

Slack

Messages, threads, and file attachments

GitHub

Repositories, issues, pull requests, and discussions

HubSpot

Contacts, companies, deals, and activities

Darwinbox

Employee directory, org data, holidays, ATS jobs, and HR workflow actions

Notion

Pages, databases, and workspace content

Fireflies

Meeting transcripts, summaries, and action items

Linear

Issues, projects, and documents

ClickUp

Tasks and documents

IMAP Email

Email messages and attachments

Nextcloud

Files and documents from a Nextcloud instance

Paperless-ngx

OCR’d documents, tags, and custom fields

Filesystem

Local files and directories

Web

Crawl and index any public website

​

How Connectors Work

1. Authentication: You provide credentials (API keys, OAuth tokens, or service accounts) that grant Omni read-only access to the data source.
2. Initial Sync: The connector performs a full sync of all accessible content. This may take minutes to hours depending on the amount of data.
3. Incremental Updates: After the initial sync, the connector periodically checks for new or updated content and syncs only the changes.
4. Permission Inheritance: Users only see search results for content they have access to in the original data source.

​

Security

• Read-only indexing: Connector syncs read data from your source systems. Some connectors can additionally expose approved, user-authorized write actions to the AI assistant.
• Credential storage: All credentials are encrypted at rest
• Permission sync: Access controls from source systems are respected in Omni

​

What’s Next