Articles in this section

Clone an integration

Cloning an integration creates a complete copy — flows, APIs, tools, mappings, groups, and more — that you can change without touching the original. Clone when you want to test changes against a working baseline, promote an integration from a development environment to production, or reuse a working configuration as the start of something new. This article explains what a clone does and doesn't carry over, how to create one, and how to finish setting it up afterward.

To clone a single flow instead, see Clone a flow. To copy an integration app's flows, see Clone integration app flows with the template utility.

Prerequisites: You must have Manage all permissions on the integration, and Manage access or higher to the environment you're cloning into. See Manage user roles & permissions to an account.

What a clone carries over

You can't clone a shared integration or a shared flow.

Carried over Not carried over Carried over with conditions
Flows, exports, imports, lookups, scripts, APIs, and tools Connection credentials — you configure each connection in the clone Lookup cache data — only if Include data when lookup cache is cloned or downloaded was selected on the original cache, the total size of the integration's lookup caches is under 5 MB, and the clone is in the same environment
Mappings, transformations, filters, and hooks Each flow's schedule and next run time — cloned flows don't run until you schedule or run them Topics — see below
Branching and routing logic
Flow groups and group assignments

Topics are never duplicated within an environment. A clone in the same environment keeps publishing to and listening on the original topics. A clone in a different environment gets each topic's configuration — name, description, and retention — created and registered there, unless a topic with that configuration already exists, in which case the clone uses it. The clone fails if creating its topics would put the target account over its topic limit. Messages and subscription positions are never copied. See Clone an integration for Integration Lifecycle Management (ILM).

If the integration references its resources by aliases, the clone keeps the aliases and needs less reconfiguration; see Create and manage aliases to reference resources in scripts.

Clone an integration

  1. Go to Home home-icon.png, and check that you're in the environment you expect: its name appears at the top right of the page. If your account has one environment, no name is shown.
  2. Select the integration's Actions elipses-button.png > Clone integration.
  3. Enter a Name that you'll be able to tell apart from the original, and optionally a Description.
  4. Select the Environment to clone into. Only active environments you have Manage access or higher to are listed. See Create and manage multiple environments.
  5. Review the components listed under the form — flows are shown under their groups — and then select Clone integration.

A message confirms the clone and asks whether to configure it now or later; if the clone is in a different environment, it also asks whether to switch to that environment.

Configure the clone

Connection credentials aren't copied, so the cloned flows can't run until each connection is set up. If the clone is in the same environment as the original, integrator.io preselects the original flow's connection, and you can keep it or choose another. If the clone is in a different environment, choose an existing connection there or create a new one.

  • For each connection, select Configure, enter its details, and test it. For an application's specific settings, see Connector solutions.
  • For each lookup cache, either reuse an existing cache — available only when the clone is in the same environment — or clone it, subject to the conditions in What a clone carries over.

When every connection is configured, the integration opens with its flows listed. From there you can turn flows on, schedule or run them, and adjust mappings; see Schedule or run flows and Modify field mappings.