Search Connectors
Overview
A table of built-in content connectors that power the search capability of Moveworks AI Assistant. There are two types of built-in content connectors:
- Classic connectors: The long-standing connectors, available as part of your Moveworks subscription. They cover 35+ content systems and support up to 100K documents per connector. Some connectors support permission ingestion.
- Max Capacity connectors: The connectors used by the Max Capacity journey, available for nine content systems. They support up to 100M documents per connector, out-of-the-box permission ingestion, and improved freshness. In the Connectors page these connectors are labeled (Next Gen) — see the naming FAQ below. Available to all organizations. See Max Capacity Setup for setup details.
Please see the tables below for the specific content types supported.
Choosing Your Journey
The journey you use is decided by your content system.
- These nine systems are configured through the Max Capacity journey: Box, Confluence Cloud, Google Drive, Outlook, ServiceNow, SharePoint Online & OneDrive, Slack, Unily, and Zendesk.
- Every other system uses Classic Ingestion. Classic Ingestion is the default path and covers 35+ content systems.
Both journeys feed the same search experience. Content connected through either one is served in the Enterprise Search Plugin and the Enterprise Search Application.
How the journeys differ
These differences are useful to understand once you are set up.
Max Capacity caveats
The Max Capacity journey is newer, and a few capabilities are still on the way. The most common one to be aware of is granular filtering. Max Capacity scopes ingestion at the site, space, knowledge-base, drive, folder, or category level, plus created-date and modified-date filters. It does not yet support finer controls such as SharePoint library- or folder-level scoping, Confluence CQL, or ServiceNow query and article-type rules. If a system’s current setup depends on those, review the connector’s setup guide and its Known Limitations, and talk to your Moveworks account team before moving it.
FAQ
What are the different Content Types?
- Permissioned content ensures that employees only see the content authorized to them within the AI Assistant search experience.
- Public content will be shown to all employees within the AI Assistant search experience.
- Personal content is from private repositories, e.g. personal direct messages, personal calendar, etc, and is only accessible through user-granted authentication within the AI Assistant search experience.
What are the limits?
- Limits are applied within indexed search, which constrains the # of content items that can be searched.
- However, the limit is unlimited for live API search, which means the limit is set by the system’s retrieval setup, e.g. Notion Search API.
What are the various implementation approaches?
- Indexed: Refers to mirroring content and permissions to build an index for search.
- Live API: Refers to using the connectors own search api to retrieve content via user impersonated search.
What does Availability mean?
- Generally Available: Available now within the Moveworks AI Assistant experience.
- Limited Preview: Available if participating in the Limited Preview program (terms and conditions may apply). Please fill out the self-nomination form in Community and the Moveworks Product team will reach out to you with the next steps.
- Roadmap: Planned for the upcoming release but exact release quarter is to be determined. To learn more, join the Community to ask questions.
What if the content connector is not listed?
If the content connector is not listed, then Moveworks does not have a native content connector. There are two ways forward:
- To submit a request for a native connector, we recommend to submit the request the Ideas Portal.
- If you have developers who can build the integration, we recommend implementing a Content Gateway connector.
What is the “(Next Gen)” label on some connectors?
In the Connectors page, the connectors used by the Max Capacity journey are labeled “(Next Gen)” — for example, “Confluence (Next Gen)”. “Max Capacity” is the name of the journey, not the connector label. You configure the Max Capacity journey using these “(Next Gen)” connectors. ServiceNow and Zendesk are exceptions: their connectors have no suffix and serve both journeys.
Is “Enterprise Search” the same as “Max Capacity”?
No. Enterprise Search is the product — the Enterprise Search Plugin (conversational search inside the AI Assistant) and the Enterprise Search Application (a dedicated search surface in My Moveworks). Max Capacity is one of two setup journeys for connecting content systems. Content ingested through either journey is served by both surfaces. See Choosing Your Journey for the full picture.
Why do I see two connectors for the same system (for example, “Confluence” and “Confluence (Next Gen)”)? Which one do I pick?
For most systems that support both journeys, there are two distinct connectors: the Classic connector (used by Classic Ingestion) and the Max Capacity connector, shown as (Next Gen) in the Connectors page. Pick the connector that matches the journey you are setting up. ServiceNow and Zendesk are exceptions: those connectors are consolidated, so a single connector serves both journeys — note that a single consolidated connector cannot back a Classic configuration and a Max Capacity configuration at the same time.
Can I keep using Classic Ingestion? Will Classic connectors be deprecated?
Yes, you can keep using Classic Ingestion — it remains generally available and fully supported, and for many systems it is the only option. No deprecation date or migration deadline for Classic connectors has been announced.
My content system isn’t in the Max Capacity list — what should I do?
Use the Classic connector for that system; Classic Ingestion remains the correct and supported path, and the content it ingests is served in the Enterprise Search Plugin and Application just like Max Capacity content. If your system has no native connector at all, request one through the Ideas Portal or build your own integration with Content Gateway.
Is Confluence Data Center or Confluence Server supported on Max Capacity?
No. Max Capacity supports Confluence Cloud only. Confluence Data Center and Server deployments are not supported on Max Capacity — including Data Center instances placed behind a proxy. For Data Center or Server, use the Classic Confluence connector.
Why don’t I see the Max Capacity page in Moveworks Setup?
The Max Capacity journey is enabled for all organizations. You’ll find it in Moveworks Setup under Configure Search → Max Capacity. If you don’t see it there, contact your Moveworks account team.
I configured a Max Capacity connector, but employees don’t see the content in search. Why?
The three most common causes are: (1) the configuration’s Target Audience does not include those employees — for example, it is still “No users” or a small pilot group, (2) the first ingestion has not completed, so the content is not in the index yet, or (3) for live-search and personal-content connectors, employees have not authenticated through the Enterprise Search Application, or your organization does not have it enabled. Check the audience setting and ingestion status first; for live-search issues, confirm Enterprise Search Application access with your account team.