Connector directory

A source is a virtual container holding all items related to a repository such as your company website, database, or SharePoint system. This content is searchable through a search interface.

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 them 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, the indexing process remains the same regardless of the connector or method used.

Connector types

Coveo offers a variety of native and generic connectors that let you 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

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

Generic connectors are created by Coveo to index content from various types of repositories, such as databases, web applications, and websites. They let you index any repository that doesn’t have a native connector, including custom repositories, as long as it meets certain requirements.

Content sources that use a generic connector are configured through a user interface. Some sources, such as the REST API and Database sources, require you to enter a code configuration. This configuration specifies what content to index and how to retrieve it. While this process is more complex and requires greater expertise compared to using sources with a native connector, Coveo can help simplify the initial steps. When adding a source, the feature may suggest a sample code configuration from the Coveo GitHub Connectivity Library for use with a specific generic connector.

Given their versatility, you may find that several of these connectors can be used to index the same repository. Deciding which one to use typically comes down to considerations like available content security options and content retrieval methods. Refer to a connector’s Source key characteristics section for this information and for the complete list of connector features.

The most popular generic connectors are the Web, Sitemap, REST API, GraphQL API, and Database connectors. See the entire list of generic connectors offered by Coveo.

Custom-built connectors

If none of the connector options above fit your needs, you can build your own connector, that is, 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.

To get started with your connector project, see the C# SDK, Push API, and Connector building best practices documentation.

Connector directory

The Native and generic connectors table lists all the native and generic connectors Coveo offers. If the repository you want to index doesn’t appear in this table, follow these steps:

  1. In the Add a source of content panel, use the Search for a specific source or an application to index box to check if Coveo recommends a generic connector for the repository you want to index.

  2. If Coveo doesn’t recommend a generic connector, compare the Source key characteristics tables to determine which one best fits for your repository.

  3. As a last resort, consider building a custom connector. Contact your Coveo representative for more information and guidance.

Suggest a source and Upgrade license options

Don’t hesitate to use the Suggest a source option in the Add a source of content panel to request a new connector that meets your needs. Coveo is always on the lookout to index popular and emerging systems.

The source you want to use may be greyed out in the Add a source of content panel, either because you need access to the Crawling Module (crawlingmodule) or because the source isn’t included in your license. Click Upgrade license and select the corresponding option to have your license upgraded.

Native and generic connectors

Connector Type Content retrieval method Available in

Amazon S3

Native

Cloud

All Platform plans

Box Business

Native

Cloud

All Platform plans

Catalog

Generic

Push

Ecommerce extension

Confluence Cloud

Native

Cloud

All Platform plans

Confluence Data Center

Native

On-premises

N/A (available as an option of the Enterprise Platform plan)

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Database

Generic

Cloud

All Platform plans

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Dropbox Business

Native

Cloud

All Platform plans

File

Generic

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Google Drive for Work

Native

Cloud

All Platform plans

GraphQL API

Generic

Cloud

All Platform plans

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Jira Software Cloud

Native

Cloud

All Platform plans

Jira Software Data Center

Native

On-premises

N/A (available as an option of the Enterprise Platform plan)

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Jive Cloud

Native

Cloud

All Platform plans

Jive Server

Native

On-premises

N/A (available as an option of the Enterprise Platform plan)

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Khoros Community

Native

Cloud

All Platform plans

Microsoft Dynamics 365

Native

Cloud

All Platform plans

Push

Generic

Push

All Platform plans

REST API

Generic

Cloud

All Platform plans

Crawling Module

Enterprise Platform plan with Crawling Module add-on

RSS

Generic

Cloud

All Platform plans

Salesforce

Native

Cloud

Coveo for Salesforce integration

SAP

Native

Cloud

Coveo for SAP integration

ServiceNow

Native

Cloud

Coveo for ServiceNow integration

SharePoint Online

Native

Cloud

All Platform plans

SharePoint Server

Native

On-premises

N/A (available as an option of the Enterprise Platform plan)

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Sitecore

Native

Push

Coveo for Sitecore integration

Sitemap

Generic

Cloud

All Platform plans

Crawling Module

Enterprise Platform plan with Crawling Module add-on

Slack

Native

Cloud

Enterprise Platform plan

Web

Generic

Cloud

All Platform plans

Crawling Module

Enterprise Platform plan with Crawling Module add-on

YouTube

Native

Cloud

All Platform plans

Zendesk

Native

Cloud

Coveo for Zendesk integration

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.