You can clone an existing integration to create an exact copy for making, auditing, or testing changes. It works best when you want to keep all your configurations and mappings while using a new connection. Remember, cloning is done at the integration level, not the flow level. You can't clone one flow; you'll have to clone the entire integration. You can still change a flow; this restriction just means that if you want to manage or test a flow using Integration Lifecycle Management, you must clone the entire integration. Don't forget that you can leverage concurrencies and multiple connections to help your integrations run smoothly.
- Learn about Integration Lifecycle Management
- Manage integration lifecycles
- Back up an integration with a snapshot
- Clone an integration
- Create and pull changes from one integration to another
- Review changes within a pull or revert
- Merge changes after a pull
- Revert changes
Important: Cloning is always done at the integration level, not the flow level.
You must have Manage access to the specific integration to create a clone. To use the pull feature, first create a clone in one of two ways using the existing clone functionality:
Clone using the Clone integration button
You can clone an integration using the Clone integration button. You’ll need to reconfigure your connections and, possibly, your flows. You can clone an original integration multiple times and merge direct clones.
Clone using the ZIP file
You can clone an integration using a downloaded integration ZIP file. If you don't have access to the production environment or the integration, you can upload an integration ZIP file sent to you to install the integration as a clone.
Please sign in to leave a comment.