Cloning duplicates your existing app without making any changes to the source app. This can be useful in a number of situations: For example, if you created an app against your staging API and now you want to deploy against your production API. You can clone your staging app, change the base URLs. Now you have two apps, one for each environment.
Another example is for releasing new app features. When your app is in production, you can’t make changes to it (this might break existing integrations). Instead, you clone your existing app, make changes to the new app. Once you publish your new app, users can use that to create new integrations. You can then migrate integrations from the old app to the new one.
In the Apps menu in your dashboard, you can view all existing apps. When you hover above an app you can view a menu at the top right corner as shown below.
When you click the Clone option, the Clone App popup appears in front of you as shown below.
When you clone an app, all the activities (actions & triggers) inside the app are cloned automatically. To make things easier, you can change the existing base URL(s). Let’s say you created an app and tested it on your staging server (https://api.staging.example.com). Now you want to deploy the app on production, so you clone the app and point it to your production server by changing the base URL to https://api.example.com.
Base URL: Base URL points to a server. It could point to a staging server or a live server. To learn more about Base URL and how to configure one, click here. You can configure multiple base URLs with your app to support multiple abilities of an app, not necessarily on the same server.
The cloned app is set to draft by default, a lock icon appears at the bottom right corner with the app icon as shown below.
Besides, cloning app you also clone actions and triggers. To learn how to clone them, click here.