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

# Clone Connector

The Clone Connector feature allows you to create a copy of an existing deployed connector within the same workspace. Instead of recreating connector configurations manually, you can duplicate an existing connector, modify its configuration if required, and deploy it as a separate connector.

The cloned connector copies the original connector configuration, including environment variables, connection settings, and deployment configuration, while remaining independent from the source connector.

## Benefits

The Clone Connector feature helps you:

* Quickly create similar connectors without manual configuration.
* Reuse existing connector configurations across multiple integrations.
* Reduce deployment time and configuration errors.
* Test configuration changes without modifying the original connector.
* Create environment-specific connector instances.

## Supported Resources

Currently, cloning is supported only for **deployed connectors** within the same workspace.

## Permissions

The following roles can clone deployed connectors:

| Role              | Permission  |
| :---------------- | :---------- |
| Environment Admin | Full Access |
| Maintainer        | Full Access |

## How It Works

1. Navigate to the **Connectors** page.
2. Select a deployed connector.
3. Click **Clone**.
4. Review the cloned configuration.
5. Rename the connector if required.
6. Save the cloned connector.
7. Deploy the connector when ready.

The cloned connector is created in a **Stopped** state and does not begin processing data until it is explicitly deployed.

## What Gets Cloned

When a connector is cloned, Condense copies:

* Connector configuration
* Environment variable mappings
* Connector settings
* Technical configuration
* Deployment version (latest or selected historical version)

Sensitive values such as secrets remain securely managed and continue to be masked.

## Version Selection

While cloning a connector, you can choose to clone either:

* Latest deployed version
* A specific historical deployed version

This allows previously deployed connector versions to be reused without rebuilding the configuration.

## Naming Convention

By default, the cloned connector is assigned the following name:

```text theme={null}
<Original Connector Name>_Copy
```

The connector name can be modified before saving.

## Deployment

Saving the cloned connector creates a new connector configuration.

The connector is **not deployed automatically**.

To begin processing data:

1. Review the cloned configuration.
2. Update configuration values if required.
3. Click **Deploy**.

## Validation

The following validations are performed before the connector is created:

* Source connector must exist.
* Connector configuration must be valid.
* Connector name must be unique within the workspace.

## Common Errors

| Message          | Cause                                                       |
| :--------------- | :---------------------------------------------------------- |
| Cloning Failed   | Source connector no longer exists or cannot be accessed.    |
| Duplicate Name   | Another connector with the same name already exists.        |
| Clone Successful | Connector has been successfully created in a stopped state. |

## Best Practices

* Clone deployed connectors when creating similar integrations.
* Rename cloned connectors using meaningful names.
* Verify environment variables before deployment.
* Review connector configuration after cloning.
* Deploy the cloned connector only after validating the configuration.