> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/infobridge-wb-matrix-only/9.-data-transformations/extract-comments.md).
# Extract Comments
Inforiver facilitates collaborative reporting with its advanced comments feature. [Learn more about adding comments in Inforiver](/working-with-inforiver/8.-commenting-and-collaboration/comments.md). Comments allow users to capture background details and perspectives that are not available in the data source and enrich your reports. You can extract and capture comments in Infobridge, enabling you to cascade comments into target reports.
Extract comments in Infobridge
The cell level comments are captured in a new "Comment" column that is added to the query. You will also be able to extract housekeeping fields like the updated by user, date/time at which the comment was added, and the thread status. The assignee is also displayed.
Comments captured in Infobridge
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.inforiver.com/infobridge-wb-matrix-only/9.-data-transformations/extract-comments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
