Skip to main content
Connectors pull content from your tools into Hadiq.io’s search index. Once connected, Hadiq.io continuously syncs in the background so search results reflect your latest data — no manual refreshes needed.

How connectors work

Hadiq.io takes a pre-indexing approach: content is fetched, chunked, embedded, and stored in a hybrid search index before any query is made. When you ask a question, Hadiq.io searches across the full index and returns cited answers in milliseconds. This is different from MCP connectors, which fetch live data at query time:

Available connectors

Hadiq.io supports 40+ connectors. Major integrations include:

Slack

Messages, threads, and channels

Google Drive

Docs, Sheets, Slides, and PDFs

Gmail

Emails and attachments

Confluence

Pages, spaces, and attachments

Jira

Issues, epics, and comments

GitHub

Pull requests and issues

GitLab

Merge requests and issues

Notion

Pages, databases, and wikis

Salesforce

Accounts, opportunities, and cases

HubSpot

Contacts, deals, and tickets

Zendesk

Tickets and help articles

SharePoint

Sites, libraries, and pages

Linear

Issues and projects

Asana

Tasks and projects

And more

Airtable, Dropbox, Slab, Guru, and 25+ others

Set up a connector

1

Go to Admin > Connectors

Open your Onyx instance and navigate to Admin Panel > Connectors.
2

Select a connector

Find the tool you want to connect and click it to open the setup form.
3

Authenticate

Depending on the connector, you’ll authorize via OAuth (you’ll be redirected to the source tool) or paste an API token or credentials directly.
4

Configure scope

Narrow down what gets indexed — specific channels, spaces, repos, or projects. Leave the scope fields empty to index everything the credential can access.
5

Save and wait for indexing

Click Save. Hadiq.io starts indexing immediately. Monitor progress on the connector’s status page under Admin > Connectors.

Permission syncing

Hadiq.io enforces the same access controls as the source system. When a user searches, they only see results from documents they have permission to access in the original tool. For example, if a Google Drive file is restricted to the Finance team, only Finance team members will see it in Hadiq.io search results — even if the connector was set up by an admin with broader access. Hadiq.io reads access control lists (ACLs) from each source and maps them to Hadiq.io users automatically. No manual permission configuration is needed.
Automatic per-document permission sync is available on the Enterprise plan and covers: Confluence, Jira, GitHub, Google Drive, Gmail, Slack, Salesforce, and SharePoint.
On non-Enterprise plans, you can still restrict what gets indexed by scoping the connector to specific channels, spaces, or projects. This controls what content enters the index, but per-document ACL syncing is not applied.