Clone an existing integration to create a copy of its flows, APIs, and tools for making, auditing, or testing changes, in the same environment or in another environment. The clone and the original are directly related, so after cloning you can pull changes between them in either direction. For the integrations and resources you can clone, see Supported integrations and resources. After you clone, you configure the clone's connections, and you may need to set up lookup caches and topics.
Important: For Integration Lifecycle Management, cloning is done at the integration level, not the flow level. You can't clone one flow; you must clone the entire integration. You can still change a flow; however, to manage or test a flow using Integration Lifecycle Management, you must clone the entire integration.
Prerequisites
Before you begin, confirm the following:
- Permission — You have Manage access to the integration, or you're an account owner or administrator. See Manage user roles & permissions to an account.
- Target environment — To clone into another environment, the target environment is active, and you have Manage access or above in both the source and target environments.
Clone an integration
- Select an environment at the top of the page. If you only have one environment, you won't see any other environments available.
- Go to Home, and then select the integration.
-
In the integration header, select Clone integration.
-
On the Clone integration page, enter the details:
- Name — Enter a unique name for the clone that you can identify later. You can rename your integration tile or flow outside of the cloning process.
-
Environment — Select your environment. Only active environments you have Manage access to (or above) are visible. If you clone into another environment, you complete the clone's setup in that environment, either right after cloning or later. See Create and manage multiple environments.
- Review the list of all items contained in the new integration. This includes flows, APIs, tools, and any other integration components.
- Select Clone integration.
Result: A success message asks whether you want to configure your cloned integration now or later. If you cloned to a different environment, you're asked whether you want to switch to that environment to configure the integration. The cloned integration contains all flows, APIs, and tools from the original.
Configure the cloned integration
Connections aren't copied from the original integration, so you must configure them for the clone. If the clone stays in the same environment as the original, integrator.io preselects the connection used in the original flows during configuration. If you cloned into a different environment, you can select an existing connection in that environment or create a new one.
-
For each connection, select Configure, provide the required connection details, and test the connection. See Connector solutions for help with specific connectors.
Tip: Choose a different connection for each connection in the original integration. If you select the same connection for two of them, a later pull can fail at merge. See Connections.
- For each lookup cache, either reuse an existing lookup cache in the same environment or clone it. A cloned lookup cache keeps its entries only in the same environment and under 5 MB with Include data when lookup cache is cloned or downloaded selected; otherwise, repopulate it before you run any flows. See Lookup caches.
Result: After you configure your connections, the Integration details page opens and shows all of your flows. From here, you can turn flows on and off, schedule or run them, and modify their field mappings.
Topics in a cloned integration
To process messages already in a topic, set Start from to All retained messages on each subscription before you turn the flow on for the first time, or replay messages after. For what cloning carries for topics, see Topics.
Clone using a 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 that someone sent you to install the integration as a clone. A clone installed from a ZIP file isn't linked to the original integration, so you can't pull changes between them.