> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/knowledge-bot/functional-documentation/functional-capabilities/data-sources/data-sources-listing.md).

# Data Sources listing

The data sources listing section displays all materials linked to the current Knowledge Bot. This interface allows users to manage and monitor the content that the chatbot references when generating responses. Items are ordered by the most recent update date, descending.&#x20;

<figure><img src="/files/YFLHp9k4k2m1K1Okm7gM" alt=""><figcaption></figcaption></figure>

For each data source, the following details are shown:&#x20;

* **Data Source**: The name of the material, helping identify its origin.&#x20;
* **File/URL**: Displays the name of the uploaded document or the URL of the scraped webpage / Confluence / SharePoint. This allows user to quickly recognize the specific files or pages that have been incorporated into the chatbot's knowledge base.&#x20;
* **Status**: Indicates the current processing status of each item:&#x20;
  * **Success**: The material has been processed successfully and is ready for use.&#x20;
  * **Pending**: Processing is ongoing; the user must wait until it is complete.&#x20;
  * **Not Refreshed**: The material was not replaced or updated successfully through recurrency or manual update.&#x20;
  * **Fail**: The material could not be processed. &#x20;
* **Actions available**:&#x20;
  * **File details**: Open the details of the data source. &#x20;
  * **Replace**: Allows modification or replacement of the data source.&#x20;
  * **Delete**: Removes the data source if it is no longer relevant.&#x20;

Users can also search for specific materials. For hierarchical sources such as Confluence or SharePoint, pages are displayed in a tree view that reflects their structure from Confluence / SharePoint.&#x20;

Folders in Confluence or SharePoint do not have individual detail pages; they serve only to replicate the structure visually.&#x20;

<figure><img src="/files/joFPWfCUg9U5lTStB4RN" alt=""><figcaption></figcaption></figure>

Processing statuses influence available actions:&#x20;

* If **Success**, all options are available.&#x20;
* If **Pending**, no actions can be performed until processing is complete.&#x20;
* If **Not Refreshed**, all options are available
* If **Fail**, users can Replace or Delete, and a tooltip will explain the failure reason. In this case, the details page is unavailable as no data has been ingested.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ixhello.com/knowledge-bot/functional-documentation/functional-capabilities/data-sources/data-sources-listing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
