Add or Edit a Source Using One of the Available Connectors
- Amazon S3 Source
- Box (Personal) Source
- Box Business Source
- Confluence Cloud Source
- Confluence Self-Hosted Source
- Database Source
- Dropbox (Personal) Source
- Dropbox Business Source
- Exchange Enterprise Source
- Exchange Online (Personal) Source
- File System Source
- Generic REST API Source
- Gmail for Work Source
- Gmail (Personal) Source
- Google Drive (Personal) Source
- Google Drive for Work Source
- Jira Software Cloud Source
- Jira Software Self-Hosted Source
- Jive Cloud Source
- Jive Server Source
- Khoros Community Source
- Microsoft Dynamics 365 Source
- OneDrive for Business Source
- OTCS Source
- Push Source
- RSS Source
- Salesforce Source
- ServiceNow Source
- SharePoint Online Source
- SharePoint Online Legacy Source
- SharePoint Server Source
- Sitecore Source
- Sitemap Source
- Twitter Source
- Web Source
- YouTube Source
- Zendesk Source
Add or Edit a Push Source
You may want to make searchable some content of a type for which a specific connector isn’t yet available. In such a case, members of the Administrators and Content Managers built-in groups can take advantage of the Coveo Push API to index this content in a Push source (see Push API).
You have valuable content in an on-premises content management system (CMS) developed in-house. One of your developers can create a crawler to get this content and push it to your Coveo Cloud organization.
Before you can push content to Coveo Cloud, you must create a Push type source to which the content will be sent.
Add or Edit a Push Source
If not already in the Add/Edit a Push Source panel, access the panel:
To add a source, in the main menu, under Content, select Sources > Add Source button > Push.
To edit a source, in the main menu, under Content, select Sources > source row > Edit in the Action bar.
In the Configuration tab, enter appropriate values for the available parameters:
A descriptive name for the content of your source under 255 characters (not already in use for another source in this organization).
A developer coding a crawler to push content in this source will need this name to get the corresponding
Push API URL
Available only when you edit the source, the input contains the URL you must use to add and update an item in your source (see Adding and Managing Items and Permissions in a Push Source). The URL has the following form:
The URL that you can Copy to clipboard contains your
source IDwhich are required parameters for all operations regarding your Push source (see Push API to test API calls).
Character optical recognition (OCR)
Check this box if you want Coveo Cloud to extract text from image files or PDF files containing images (see Enable Optical Character Recognition). OCR-extracted text is processed as item data, meaning that it’s fully searchable and will appear in the item Quick View (see Search Result Quick View).
When adding a source, if you have more than one logical (non-Elasticsearch) index in your organization, select the index in which the retrieved content will be stored (see Leverage Many Coveo Indexes). If your organization only has one index, this drop-down menu isn’t visible and you have no decision to make.
When you create the source, we recommend selecting the Create an API key check box to easily get an API key with appropriate privileges to authorize a process to send information to the source. This option is available at source creation only.
In this case, your crawler process must push item permissions along with the content (see Managing Security Identities in a Security Identity Provider).
In the Access tab, determine whether each group and API key can view or edit the source configuration (see Understanding Resource Access):
In the Access Level column, select View or Edit for each available group.
On the left-hand side of the tab, if available, click Groups or API Keys to switch lists.
If you remove the Edit access level from all the groups of which you’re a member, you won’t be able to edit the source again after saving. Only administrators and members of other groups that have Edit access on this resource will be able to do so. To keep your ability to edit this resource, you must grant the Edit access level to at least one of your groups.
Optionally, consider editing or adding mappings (see Adding and Managing Source Mappings).
You can only manage mapping rules once you build the source (see Refresh, Rescan, or Rebuild Sources).
Click Add Source/Save when you want to save your source configuration.
If you selected the Create an API key check box:
In the Your Key dialog that appears, click Copy to copy the API key value to the clipboard, and click OK.
The Your Key dialog appears only once and is the only place where you can see and copy the key value.
If you fail to copy (or lose) the key value, the workaround is to manually create a new API key by selecting only the View and Edit check boxes for the Sources privileges of the Content service (see Add an API Key). In this case, you should also disable or delete the original unused API key (see Disable/Enable an API Key or Delete an API Key).
An API key is an alphanumeric string that looks like the following:
The key appears on the Administration Console API Access page and its name is your source name followed by
Paste the API key value with the source name to a safe location of your choice so you can later securely communicate this information to the person who manages the crawling process.
Click Add Source/Save when you want to add/save your Push source configuration.