To retrieve your content and create a source, Coveo uses a connector, a module that establishes a connection with a specific type of repository. A connector extracts the desired data as well as the corresponding permissions, and stores it in your index.
Moreover, some connectors can use different content retrieval methods, depending on where the data is located and how you want Coveo to extract it. Once the content is retrieved, however, the indexing process is the same regardless of the connector or method used.
Coveo offers a variety of native and generic connectors that allow you to index virtually any content repository. You can also use the connectors created by Coveo’s partners or, if none of the existing connectors meets your needs, build your own connector. See the Connector Directory for a complete list of the available connectors.
Native connectors have been made by Coveo to index content from a specific repository. They’re the easiest to use, as Coveo has already determined what the source should index and designed a user interface for this connector. When creating such a source, all you typically have to do is provide connection information and check some boxes to fine-tune what will be indexed.
For example, you can use Coveo’s native connectors to index Confluence, Jira Software, Salesforce, and SharePoint content.
Native connectors support the latest cloud version of cloud repositories and some specific versions of on-premises repositories. Typically, you can choose from up to three content security options to determine who can access the indexed content through a search interface.
Generic connectors have been made by Coveo to index content from a certain type of repository, e.g., a database, a web application, a website, etc. They allow you to index any repository that doesn’t already have its own native connector, or even your own custom repository, as long as it meets certain requirements. Depending on the connector, you might need to provide Coveo with a configuration specifying the data and metadata that you want to index.
Content sources using a generic connector can also be created through a user interface. However, the process requires more skills than with sources using a native connector. The interface of a generic source typically contains a box in which you enter a code configuration indicating how Coveo should retrieve and index the desired content.
The most popular generic connectors are the Web, Sitemap, Generic REST API, and Database connectors. The Generic REST API connector is especially versatile, as it allows you to index virtually any content exposed through a REST API.
If none of the connector options above fit your needs, you can build your own connector, i.e., write a crawling program that retrieves your content and provides it to Coveo for indexing. To do so, use Coveo’s C# SDK and Push API.
Coveo can index the content of a variety of repositories. If the repository you want to index doesn’t appear in the tables below, you should use a generic connector or a custom-built connector to index it.
Native and Generic Connectors
|Adobe Experience Manager||Native||Coveo for Adobe integration|
|Amazon S3||Native||All Platform plans|
|Box Business||Native||All Platform plans|
|Confluence Cloud||Native||All Platform plans|
|Confluence Server1||Native||All Platform plans|
|Database2||Generic||Add-on to the Enterprise Platform plan|
|Dropbox Business||Native||All Platform plans|
|File2||Generic||Add-on to the Enterprise Platform plan|
|Gmail for Work||Native||All Platform plans|
|Google Drive for Work||Native||All Platform plans|
|Jira Software Cloud||Native||All Platform plans|
|Jira Software Server1||Native||All Platform plans1|
|Jive Cloud||Native||All Platform plans|
|Jive Server1||Native||All Platform plans1|
|Khoros Community||Native||All Platform plans|
|Microsoft Dynamics 365||Native||All Platform plans|
|OneDrive for Business||Native||All Platform plans|
|Push||Generic||All Platform plans|
|REST API||Generic||All Platform plans|
|RSS||Generic||All Platform plans|
|Salesforce||Native||Coveo for Salesforce integration|
|ServiceNow||Native||Coveo for ServiceNow integration|
|SharePoint Online||Native||All Platform plans|
|SharePoint Server1||Native||All Platform plans1|
|Sitecore||Native||Coveo for Sitecore integration|
|Sitemap1||Generic||All Platform plans1|
|Slack3||Native||All Platform plans|
|Native||All Platform plans|
|Web1||Generic||All Platform plans1|
|YouTube||Native||All Platform plans|
|Zendesk||Native||Coveo for Zendesk integration|
2: To make this content searchable, you must install the Coveo On-Premises Crawling Module.
3: The Slack connector requires the Enterprise Platform plan.
Other Indexable Repositories
Below are repositories that Coveo customers have indexed with the Generic REST API connector. However, the possibilities aren’t limited to this list. If you want to index a repository that doesn’t appear here, you can do so thanks to a generic connector. The Coveo Open-Source Connectivity Library contains JSON configuration examples and instructions to help you get started.
- Azure Active Directory
- Azure DevOps
- Docebo LMS
- Exchange Online
- GoMoxie Knowledgebase
- Google Sheets
- LinkedIn Learning
- Skilljar LMS
- Stack Overflow
- Workplace from Facebook
Support for Older System Versions
Coveo connectors only support system versions that are actively maintained by their vendor. When a vendor announces that a version is at end-of-life, Coveo stops support for this version. This means Coveo no longer actively maintains and tests the connector with this version.
However, a connector can generally still be used with a system version for which support has been dropped. You therefore don’t have to upgrade to a newer version to continue to index your content.