> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/creating-flows/building-a-new-flow/copy-paste-of-form-content.md).
# Copy-pasting form content
Cut, copy, and paste work whenever your have a group, step, question, or variable selected: within flows, or even between flows.
### Copying and pasting items
When an item is focused, there is a sub-menu that will allow you to copy/cut an item. Alternatively, you can right-click the item.
This is available on groups, steps, and questions.
Once an item is copied, you can paste by right clicking the target area and:
When pasting content that depends on answers from other parts of a flow, you’ll need to guide the Formsort studio on how to handle those dependencies. This process is called **mapping input variables**.
### Mapping input variables
If you paste a flow slice that contains variables—such as [templated labels](/variable-templating.md) or questions that rely on conditional logic—you'll be prompted to map those variables to existing answers in your flow.
Flow slices that contain only static content (like informational text or images) can be pasted without any additional configuration.
When mapping input variables, you’ll have a few options:
### Create new answer
Adds a new question to the beginning of the pasted slice to collect the required input from the responder.
### Map to existing answer
If your flow already collects an answer of the correct type, you can map the variable to that existing answer—no new question needed.
This process is great for creating duplicate instances of a question.
---
# 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.formsort.com/creating-flows/building-a-new-flow/copy-paste-of-form-content.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.
