> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/piping.md). # Piping In surveys having multiple questions its sometimes needed to re-use or quote respondent's answers to a previous answered questions or answers. This process is called piping. \ \ ngSurvey supports two types of piping * [Text / Data piping](/form-management/form-designer/piping/text-data-piping.md) to pipe the respondent answers as plain text into labels or survey content. * [Carry Forward / Carry on Answers](/form-management/form-designer/piping/carry-forward-answers.md) to pipe the actual respondent answers into another question and allow these answers to be selected again from that new question. Carry forward answers are usually used with multiple selection questions where you first want to ask the respondent to choose among a set of multiple answers and then ask a more specific question about only the answers that have been selected in the multiple selection question. * [Javascript piping](/form-management/form-designer/piping/javascript-piping.md) to pipe output of custom javascript code. --- # 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.ngsurvey.com/form-management/form-designer/piping.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.