---
title: "Copy and paste app elements"
slug: "copy-and-paste-app-elements"
tags: ["App Editor (Route)", "Widget", "Widgets"]
updated: 2025-10-01T15:52:01Z
published: 2025-10-01T15:52:01Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Copy and paste app elements

*Here's how to migrate content between multiple apps.*

## Purpose

After you start building multiple apps in Tulip, you may find that you need to copy content from one app to another.

*For example, you may upload an image to one app, but realize it is also relevant to another app.*

Or, you may create a button with a series of Triggers in one app, and need to copy that to another app.

Fortunately, Tulip has multiple options for migrating content in the Chrome browser.

When migrating content from one app to another, **we recommend that you open each app in a separate tab in the same window of Chrome.**

## Images

You can copy and paste images between different apps using CTRL+C and CTRL+V on Windows, and CMD+C and CMD+V on Mac.

## Widgets

You can copy buttons, shapes and text Widgets between apps as well.

When you copy a button, the associated Triggers and variables will also be copied to the new app.

If there's already an existing Variable in the second app with the same name and type as the one referenced by the copied trigger, the trigger will automatically reference the variable that already exists in the second app.

## Triggers

You can cut, copy and paste Triggers within an app and into a separate app.

The only requirement is that they are tied to the same object. For example, button triggers can only be pasted into other buttons.

You can cut and copy triggers using the icons next to the trigger in the Side Pane:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Copy_Paste%20Content%20Within%20Apps%20And%20Between%20Apps_201222830.png)

You can also copy triggers within the Trigger Editor by clicking **Copy**.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Copy_Paste%20Content%20Within%20Apps%20And%20Between%20Apps_201224191.png)

After that, the Trigger will be stored on your clipboard. You will need to select the button or step where you would like to paste the trigger, and then hit CTRL+V or CMD+V.

This will open the Trigger Editor. Click **Save** and the trigger will be tied to the new button or step.

## Steps

Learn about copying steps [here](https://support.tulip.co/docs/steps#duplicate-a-step).

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have solved a similar topic!

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.

**Widgets**

**Widgets**are the elements that make up a specific **App Step.**Widgets can display information to users, collect user input, or trigger app logic.

*Common widgets include: Interactive Tables, Number inputs, Machine attribute widgets, and more.*

**Variable**

**Variables**are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.

**Side Pane** **(Context Pane)**

The**Side Pane**is the configuration pane on the right side of the **App Editor**where steps, apps, and widgets can be configured. **Triggers**can be added to adjust widget behavior.![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Context%20Pane.png)

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.

**Steps**

A view your users will see within an application. **Steps** can be viewed chronologically or in whatever order best fits your process.

Steps can be grouped into **Step Groups**to manage and organize your app Steps.