Feature Request

Provide logs or detailed error messages for failed PDF import scenarios. Currently, when an import fails, there is no visibility into the reason, making troubleshooting difficult. This should include clear failure reasons (e.g., missing H1 tags) and optionally a downloadable log. Additionally, consider avoiding credit consumption when the import does not generate any output.

Our customers would like Eddy to search the Images or its metadata such as "Alt Text" to fetch the answers from the images. Many of our customers use images to represent important data in the articles. They would like Eddy to search the image content and provide the answer.

Provide the ability to fetch and apply predefined article templates in Document360 via MCP. This would ensure consistent and structured content creation across articles.

It would be great if we can have a link of all the pages in our help center for LLM that contains the same page in txt with the markdown of the content. This makes it much easier for an LLM to read and therefore it is likely that they will include it more in the sources and, consequently, many more users will come to their site. Example: • normal version= https://docs.stripe.com/no-code/payment-links • .txt version for LLMs= https://docs.stripe.com/llms.txt

Our use case is to use the chatbot with the content access provided only to API documentation workspace. Chatbot is also required to provide information for the API documentation workspace. Currently, we are unable to choose the API documentation workspace in the content access section for the chatbot. It would be great if we have an option to choose the API documentation workspace in the content access.

To enable AI Assistive search inside the Freshdesk and Freshservice extensions, On reply to tickets in freshservice and freshdesk extensions, we can use algolia search to search the knowledge base, we can enable Eddy here to help the users capitalize on their purchased AI Assistive search add-on.

Customer has requested for a possible integration or availability to Microsoft Copilot Studio Services, which can ideally help them build their own chatbot to read through their site.

As a user, I have connected Jira (PRD),source code (Gitlab / Github), and then now connect with Document360 for cross verifying / references against the current implementation. With new requirements, Claude can make the new changes in respective file changes in repo, and at the same time it can also create a new drafted content page of the existing feature or new implementation and push that for review process before publishing the page.

Implement an integration between Document360 and version control systems like Git and Azure DevOps to enable automatic generation of documentation based on code repositories. This feature would allow Document360 to: Read source code: Access and analyze code directly from Git or ADO repositories. Generate documentation: Automatically create and update documentation based on the code structure, comments, and metadata, ensuring that documentation stays in sync with the latest code changes. Support multiple languages: Recognize and support documentation generation for various programming languages and frameworks.

It would be great if the custom page content is also included in Eddy search results.