- Enterprise Search Guide: other versions:
- Getting started
- Prerequisites
- Ingestion
- Web crawler
- Connectors
- Native connectors
- Connector clients
- Elastic connector framework
- Workplace Search connectors
- Using connectors
- Known issues
- Troubleshooting
- Document level security
- Logs
- Security
- Content syncs
- Sync rules
- Content extraction
- Reference: Azure Blob Storage
- Reference: Confluence
- Reference: Dropbox
- Reference: GitHub
- Reference: Gmail
- Reference: Google Cloud Storage
- Reference: Google Drive
- Reference: Jira
- Reference: Microsoft SQL
- Reference: MongoDB
- Reference: MySQL
- Reference: Network drive
- Reference: OneDrive
- Reference: Oracle
- Reference: PostgreSQL
- Reference: S3
- Reference: Salesforce
- Reference: ServiceNow
- Reference: SharePoint Online
- Reference: SharePoint Server
- Reference: Slack
- Ingestion APIs
- Ingest pipelines
- Document enrichment with ML
- ELSER text expansion
- Indices, engines, content sources
- Programming language clients
- Behavioral analytics
- Search UI
- App Search and Workplace Search
- Search Applications
- Enterprise Search server
- Run using Docker images
- Run using downloads (packages)
- Enterprise Search server known issues
- Troubleshooting
- Troubleshooting setup
- Monitoring
- Read-only mode
- Management APIs
- Monitoring APIs
- Read-only mode API
- Storage API
- Configuration
- Configuring encryption keys
- Configuring a mail service
- Configuring SSL/TLS
- Upgrading and migrating
- Upgrading self-managed deployments
- Upgrading from Enterprise Search 7.x
- Upgrading from Enterprise Search 7.11 and earlier
- Migrating from App Search on Elastic Cloud
- Migrating from App Search on Swiftype.com
- Migrating from self-managed App Search
- Logs and logging
- Known issues
- Troubleshooting
- Help, support, and feedback
- Release notes
- 8.10.4 release notes
- 8.10.3 release notes
- 8.10.2 release notes
- 8.10.1 release notes
- 8.10.0 release notes
- 8.9.2 release notes
- 8.9.1 release notes
- 8.9.0 release notes
- 8.8.2 release notes
- 8.8.1 release notes
- 8.8.0 release notes
- 8.7.1 release notes
- 8.7.0 release notes
- 8.6.2 release notes
- 8.6.1 release notes
- 8.6.0 release notes
- 8.5.3 release notes
- 8.5.2 release notes
- 8.5.1 release notes
- 8.5.0 release notes
- 8.4.3 release notes
- 8.4.2 release notes
- 8.4.1 release notes
- 8.4.0 release notes
- 8.3.3 release notes
- 8.3.2 release notes
- 8.3.1 release notes
- 8.3.0 release notes
- 8.2.3 release notes
- 8.2.2 release notes
- 8.2.1 release notes
- 8.2.0 release notes
- 8.1.3 release notes
- 8.1.2 release notes
- 8.1.1 release notes
- 8.1.0 release notes
- 8.0.1 release notes
- 8.0.0 release notes
- 8.0.0-rc2 release notes
- 8.0.0-rc1 release notes
- 8.0.0-beta1 release notes
- 8.0.0-alpha2 release notes
- 8.0.0-alpha1 release notes
Workplace Search connectors
editWorkplace Search connectors
editWorkplace Search connectors are connectors available directly within your Elastic deployment, through the Workplace Search product. No additional infrastructure is required. Workplace Search connector packages are open-code connector implementations you can deploy to your own infrastructure.
Workplace Search connectors (and connector packages) sync data sources to Workplace Search content sources. Create these content sources using the Workplace Search product within Kibana.
The following Workplace Search connectors are available:
- Box
- Confluence Cloud
- Confluence Cloud (Ruby connector package)
- Confluence Server
- Dropbox
- GitHub
- Gmail
- Google Drive
- Jira Cloud
- Jira Server
- Network drives (Python connector package)
- OneDrive
- Outlook (Python connector package)
- Salesforce
- ServiceNow
- SharePoint Online
- SharePoint Online (Ruby connector package)
- SharePoint Server (Python connector package)
- Slack
- Teams (Python connector package)
- Zendesk
- Zoom (Python connector package)
Availability and prerequisites
editWorkplace Search connectors were introduced in Elastic version 7.5.0.
Your Elastic deployment must include the following Elastic services:
- Elasticsearch
- Kibana
- Enterprise Search with at least 4GB RAM per zone
(A new Elastic Cloud deployment includes these services by default, however, you must increase the RAM for the Enterprise Search service. See Infrastructure requirements.)
While most Workplace Search connectors are generally available, some connectors may be available in beta or technical preview. Refer to the documentation for each connector, linked above.
Compatibility
editBecause Workplace Search tools are abstractions, they are designed to work well with other Workplace Search tools. Traditionally, Workplace Search connectors sync data to Workplace Search content sources, and you search those content sources using a search UI specific to Workplace Search.
However, you can now use additional Elastic tools with your Workplace Search documents. For example, you can search Workplace Search content sources using Elastic Search UI and its Workplace Search connector.
You can also access the Elasticsearch index underlying any Workplace Search content source. Using this technique, you can search and manage your Workplace Search documents using tools designed for Elasticsearch indices in addition to the tools designed for Workplace Search content sources.
Documentation
editFor all details about Workplace Search connectors, refer to the Workplace Search documentation:
Also, see the Search UI documentation to use Search UI with Workplace Search: