> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/appmixer-studio-features/visual-features/copying-objects.md).

# Copying objects

In the previous section, you learned how to select multiple objects and, thus, save time while adjusting and organising complex flows. Now, you'll learn how to copy & paste objects to boost your performance even more.

{% embed url="<https://youtu.be/eLeAlXVFppw>" %}
Copying objects in a flow
{% endembed %}

For anyone who's used a computer in the past 20 years, the instructions will be pretty easy to understand: ⌘ Cmd + C to copy an object, ⌘ Cmd + V to paste an object.

![⌘ Cmd + C to copy an object, ⌘ Cmd + V to paste an object](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-MfDVanNdK1zkMJOCQGz%2F-MfDWpqqAfGv8aB6Z_FN%2Fgif-8-1.gif?alt=media\&token=fc97f640-4523-4074-9f22-820d748e0977)

We see you laughing! Well, you will be thankful once you start building a complex flow and will start saving time copying & pasting the objects in the designer. At least, that's what we hope for. 🙂

[Next, we'll show you the Zoom in/out feature](/kb/appmixer-studio-features/visual-features/zooming-in-out.md). Stay tuned.


---

# 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.appmixer.com/kb/appmixer-studio-features/visual-features/copying-objects.md?ask=<question>&goal=<user_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.