For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Getting Started
    • Welcome to Moveworks
    • Roadmap & Release Notes
    • Moveworks Best Practices
    • Labs
    • Professional Services
    • Support
  • AI Assistant
    • AI Assistant Overview
    • Capabilities
    • Web Experiences
    • Analytics & Performance
  • Enterprise Search
    • Overview
    • Agentic RAG Overview
    • Content Ingestion Platform
    • Profile Boosting
    • Retrieval
    • Permissions Platform
    • Built-in Content Connectors
      • Axero
      • Brainstorm QuickHelp
      • Atlassian Confluence
      • Freshservice
      • GitHub
      • Google Drive
      • Interact
      • LumApps
      • ManageEngine
      • Notion
      • Salesforce
      • ServiceNow
      • Microsoft Sharepoint
      • Slack
      • Staffbase
      • Unily
      • WordPress
      • Workday
    • Build your own Content Connectors
    • Configure Search
    • Configure Enterprise Search
    • Vetted Content
    • Writing AI-Ready KB Articles
    • Document Chunking and Snippetization Overview
  • Productivity Boost
    • Overview
    • Configure Productivity Boost
    • Quick GPT
    • Calendar Management
    • Brief Me
DeveloperAcademyCommunityStatus
On this page
  • Overview
  • Lumapps Knowledge Structure
  • How do we ingest knowledge articles?
  • URL
  • Integration Scope
  • End user experience
  • Case 1: Bot finds a relevant knowledge article
  • Case 2: Bot doesn’t find any relevant knowledge article
Enterprise SearchBuilt-in Content Connectors

LumApps

||View as Markdown|
Was this page helpful?
Edit this page
Previous

ManageEngine

Next
Built with

Overview

With the LumApps content connector, Moveworks Enterprise Search enables the Moveworks AI Assistant to answer user’s questions directly in chat, by understanding the questions and responding instantly with answers containing the most relevant content, links to knowledge base articles or files, or links to external articles taken from trusted knowledge sources.

Lumapps Knowledge Structure

How do we ingest knowledge articles?

Our knowledge engine makes relevant snippets from the knowledge articles in less than a second, using Moveworks’ natural language understanding and similarity scoring.

We store the snippzetized articles in our enterprise cache, which can be served to users based on the inquiry.

We are currently fetching all the pages along with its meta data such as URL, Id, Author details, Status using the below API.

URL

https://go-cell-002.api.lumapps.com/_ah/api/lumsites/v1/content/list?lang=en

Integration Scope

LumApps hosts knowledge under different pages and sub-pages, which acts a container that hold different widgets.

These are some widgets types available on the LumApps platform: HTML, introduction text, image, video, comments, user lists, etc.

As LumApps doesn’t return responses in an HTML format, we create an HTML file and after analyzing the response, we can only ingest the intro and HTML widget content into the created HTML file.

So we ingest only:

  1. Intro widget
  2. HTML widget

After creating an HTML file we store it in our cache, our knowledge ingestion engine works on identifying HTML tags and creating relevant knowledge base article snippets.

End user experience

Whenever a user makes an inquiry there are two cases which can occur:

Case 1: Bot finds a relevant knowledge article

Case 2: Bot doesn’t find any relevant knowledge article