Duplicate a Connector

You can now duplicate an existing connector instead of rebuilding one from scratch.

How to duplicate a connector

From either the connectors list or a connector's detail page, click Duplicate to open a guided two-step flow:

Step 1 — Confirm connector details. Review and edit the new connector's name, credentials, and ingestion settings. The name is prefilled as <original name> Copy.
Step 2 — Choose what to bring along. Pick which configured streams and datasets to duplicate. Each is prefilled as <original name> Copy and is fully editable before you submit. You can remove any datasets you don't want in the new connector.

Submitting creates a brand-new connector with fresh datasets. Your original connector stays untouched, and dataset mappings are preserved on the copy.

Optional backfill

After duplication, you can optionally kick off a backfill for the new datasets right away.

Safe retries

Retries are safe:

If something hiccups mid-duplication, clicking Duplicate again won't create ghost copies.
Any per-dataset failures are reported so you can see exactly what succeeded and retry just what didn't.

Extension mappings on duplicated datasets

If your source connector includes datasets from a provider that supports custom extension mappings (such as Google Analytics 4), each cloned dataset keeps the source's extension mapping selection by default. During the dataset-edit step of the wizard, you can attach a different mapping, switch to another, or clear the mapping for any individual cloned dataset before the duplicate is created. Shared mappings are protected from accidental overwrite during duplication. See Build a Native Provider Dataset for details on managing extension mappings from the dataset modal.

Availability

Available today for stream and report-style connectors.