> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/component-builder/layout-and-customization/copy-paste-component-settings.md).

# Copy / Paste component settings

## Overview

The Avonni Components Package comes with a handy copy/paste feature. This lets you effortlessly copy settings from one component and apply them to another. It makes setting up components faster and easier, helping you avoid mistakes. This feature is especially useful for quickly creating similar screen flows by replicating settings across components.

## Step-by-Step Guide

1. **Select the component** whose configuration you want to copy by clicking on it.
2. Click on **Copy** from the dropdown menu located next to the "Open Component Builder" button
3. **Drag another same component** into your screen flow
4. Click on **Paste** from the dropdown menu located next to the "Open Component Builder" button
5. Confirm to paste your previously copied inputVariables configuration into this component.

{% @arcade/embed url="<https://app.arcade.software/share/YdU4jjS2KMJbGTerWrnt>" flowId="YdU4jjS2KMJbGTerWrnt" %}

{% hint style="info" %}
You can copy/paste configurations into the same screen flow or another one.
{% endhint %}


---

# 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.avonnicomponents.com/flow/component-builder/layout-and-customization/copy-paste-component-settings.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.