# Duplicate a workflow

Duplicate a workflow when you want to reuse its structure while keeping future changes separate. This is useful for testing a revised prompt, adapting a process to another source, or creating an experimental branch without editing the original.

The duplicate is a separate workflow. Its definition can resemble the original, but the original's successful runs and execution baseline should not be treated as the duplicate's history.

## Create the copy

1. Find the original in the Workflows list or open its detail page.
2. Choose **Duplicate** from its available actions.
3. Open the new workflow and give it a clear name.
4. Review its trigger and enabled state before allowing automatic execution.
5. Replace source connections, destinations, document selections, and app-specific values as needed.
6. Validate and run a small example.

A copied connection reference still points at the referenced connection until you change it. Duplication is not a way to copy credentials into a different workspace. Access checks continue to apply.

## Review actions carefully

An unchanged write step can send the duplicate's results to the same destination as the original. A copied schedule or event trigger can also cause both workflows to process similar inputs. Keep the duplicate manual or disabled while developing it, and use a separate test destination when appropriate.

Inspect natural keys, record types, source names, and output naming. Two workflows can intentionally contribute to one dataset, but that should be a deliberate decision rather than an accidental consequence of copying.

## Decide how to promote the change

Once the copy works, decide whether it replaces the original, remains a separate process, or should be converted into a reusable recipe. Changing a duplicate does not update the original or its apps automatically. Update any consuming app binding explicitly and verify its data view.

If you only need to return a single workflow to a previous saved definition, use [versions](/docs/workflows/versions). If multiple workflows should follow a shared upgrade path, use [reusable recipes](/docs/workflows/reusable-recipes) instead of maintaining many unrelated copies.