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

# Clone existing workflows

> Copy one or more workflows into another project in your company without rebuilding them.

Once you have a workflow that works, there is no need to rebuild it in another project. You can select the workflows you want and copy them into another project in your company: Jelou carries over the full canvas, the inputs, the training questions and the AI Routing route.

This is the usual way to move a flow from a test environment into production, to replicate an implementation for another brand, or to reuse a flow you already solved.

<Note>
  This copies **individual workflows** between projects that already exist. If what you want is to create a new project out of another one, with its whole configuration, use **Clone existing** when [creating a project](/en/guides/getting-started/create-project).
</Note>

## Before you start

* You need permission to **create workflows** in the project. Without it, the icon does not appear.
* The option is unavailable in read-only mode and while you are reviewing a published version.
* The destination must be **another** project in your company. The project you currently have open is not listed.

## Clone the workflows

<Steps>
  <Step title="Turn on clone mode">
    In the sidebar, in the **Workflows** section, click the clone-workflows icon next to the **+**.

    The list switches to selection mode: every workflow shows a checkbox and the per-row action menus are hidden.
  </Step>

  <Step title="Select the workflows">
    Tick the checkbox of every workflow you want to copy. You can pick one or several.
  </Step>

  <Step title="Open the clone modal">
    The button at the foot of the sidebar changes to **Clone workflow** or **Clone workflows** depending on how many you ticked. It stays disabled until you select at least one.
  </Step>

  <Step title="Choose the destination project">
    Under **Clone to**, select the project you want to copy the workflows into. The field has a search box, handy when your company has many projects.
  </Step>

  <Step title="Review the validation">
    As soon as you pick the destination, Jelou checks the selection and tells you what will happen before touching anything:

    * If something prevents the copy, it shows in red and the confirm button stays disabled.
    * If there are only warnings, they show in amber and you can carry on.
    * If there is nothing to report, no message appears.
  </Step>

  <Step title="Decide whether to go to the destination project">
    When nothing is blocking the copy, the **Go to the destination project when the clone finishes** checkbox appears, ticked by default. Untick it if you would rather stay where you are.
  </Step>

  <Step title="Confirm">
    Click **Clone** with the number of selected workflows. While it runs, the button reads **Cloning...** and both the destination project and the checkbox are frozen, so the operation cannot change halfway through.
  </Step>

  <Step title="Done">
    You will see a confirmation notification when it finishes. If you left the checkbox ticked, Jelou takes you to the destination project's workflow list.
  </Step>
</Steps>

## How each workflow's destination is decided

Jelou pairs each workflow by its **name**, as it is called today in each project. That is what determines what happens to it:

| Situation in the destination project | What Jelou does                                                             |
| ------------------------------------ | --------------------------------------------------------------------------- |
| No workflow carries that name        | **Creates** it, keeping the original's name                                 |
| Exactly one carries that name        | **Replaces** it: the destination's content is overwritten with the source's |
| More than one carries that name      | **Blocks the copy**, because it cannot tell which one to point at           |

No workflow is renamed in the process. On a replace, the destination workflow keeps its own name — the very name that paired the two.

<Warning>
  Replacing overwrites the content of the workflow that was already in the destination project. Before confirming, read the warning in the modal: it names exactly which workflow will be overwritten.
</Warning>

## What gets copied

| Item                  | How it lands in the destination project                                                                                 |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Each channel's canvas | Nodes, their connections and their configuration are copied                                                             |
| Inputs                | Copied as they are                                                                                                      |
| Training questions    | Copied as they are                                                                                                      |
| AI Routing route      | Created or updated to point at the copied workflow                                                                      |
| Channels              | Paired by type. If the source workflow has a channel of a type that does not exist in the destination, Jelou creates it |
| Human agent handoffs  | Keep their assignment configuration                                                                                     |
| Database nodes        | Keep pointing at the same databases in your company                                                                     |

The source project is never modified: cloning only reads from it.

## What you have to set up again

Some nodes travel with their structure and connections intact but lose the reference that was tied to the source project. The node stays on the canvas, in place and connected, but you have to pick the resource again:

| Node                                                 | What is kept                        | What you have to do                                                                                                                                             |
| ---------------------------------------------------- | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| HSM template                                         | Its outputs and connections         | Pick the template again                                                                                                                                         |
| Message with a WhatsApp Flow                         | The node and its connections        | Pick the flow again, plus the screen and data if you were using them                                                                                            |
| AI Agent                                             | Its prompt, its model and its tools | Load its knowledge again: the sources arrive empty and file reading is switched off                                                                             |
| Messages that redirect to another workflow on expiry | The message and its buttons         | If the workflow it redirected to did not travel in the selection and does not exist in the destination, the redirect on expiry is switched off. Set it up again |

<Warning>
  Review these nodes **before publishing** in the destination project. An HSM template or WhatsApp Flow node with no resource selected fails at runtime, and an AI Agent without its knowledge will answer without the information you expected.
</Warning>

## Variables and secrets

Variables and secrets are **not copied**. The nodes that use them still look them up by name in the destination project, so they have to exist there before you clone.

<Warning>
  If a workflow uses a variable or a secret that does not exist in the destination project, the copy is blocked and the modal tells you which name is missing. Create it in the destination project first, then try again.
</Warning>

## What can prevent the clone

These are the cases that block the copy. In all of them, the modal's message names the workflow or resource involved so you know what to fix:

| Reason                                         | What it means                                                                                                      |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Missing variable or secret                     | The workflow uses a variable or secret that is not in the destination project                                      |
| Ambiguous name in the destination              | The destination project has several workflows with the same name and there is no way to pick which one to point at |
| Repeated names in your selection               | You selected several workflows with the same name, so they cannot all be paired                                    |
| Reference to a workflow that is not travelling | A node calls another workflow that is neither in your selection nor in the destination project                     |
| Ambiguous reference                            | A node calls another workflow by name and the destination has several with that name                               |
| Reference to a deleted workflow                | A node calls a workflow that no longer exists                                                                      |
| Duplicate channels of the same type            | The source or the destination workflow has more than one channel of the same type, so pairing would be ambiguous   |
| Workflow outside the source project            | The selected workflow does not belong to the project you are cloning from                                          |

<Tip>
  If one workflow calls another, include them in the same selection. That way the reference resolves among the workflows travelling together instead of depending on what already exists in the destination.
</Tip>

## After cloning

<Steps>
  <Step title="Set up the pending nodes again">
    Open the HSM template and WhatsApp Flow nodes and pick the matching resource in the destination project. If the workflow has an AI Agent, load its knowledge again.
  </Step>

  <Step title="Review the channels">
    If Jelou created a channel that did not exist in the destination, review its configuration before going to production.
  </Step>

  <Step title="Test the flow">
    Use the [tester](/en/guides/getting-started/tester) in the destination project to check the workflow responds the way you expect.
  </Step>

  <Step title="Publish in the destination project">
    The copy lands on the destination project's canvas, but it is not published on its own. Publish a version there so it starts serving. See [publish versions](/en/guides/getting-started/publicar-versiones).
  </Step>
</Steps>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Is the source project modified?">
    No. Cloning only reads the source project. Its workflows, its channels and its configuration stay intact.
  </Accordion>

  <Accordion title="Can I clone into a project from another company?">
    No. The **Clone to** list only shows projects from your own company.
  </Accordion>

  <Accordion title="Can I clone into the project I am already in?">
    No. The project you have open is not listed as a destination.
  </Accordion>

  <Accordion title="What happens if the clone fails halfway through?">
    Jelou rolls back everything it had written up to that point, including any workflows and channels it had created. The destination project is left as it was and you can try again.
  </Accordion>

  <Accordion title="Can the overwritten workflow be recovered?">
    Replacing overwrites the workflow on the destination project's canvas, so its previous canvas content cannot be recovered from there. What does not change on its own is production: replacing publishes nothing, so the version already published in the destination keeps serving until you publish the replacement. That gives you room to review the result first — and if in doubt, rename the source workflow so a new one is created instead of overwriting.
  </Accordion>

  <Accordion title="Why is my HSM template or WhatsApp Flow node left unselected?">
    Because the template and the flow are tied to the source project, so the reference does not carry over. The node keeps its place and its connections, so all you have to do is pick the resource again in the destination project.
  </Accordion>

  <Accordion title="Is the AI Agent's knowledge copied?">
    No. The node arrives with its prompt, its model and its tools, but the knowledge sources arrive empty and file reading is switched off. Load them again in the destination project.
  </Accordion>

  <Accordion title="Can I clone tools or marketplace apps?">
    No. Clone mode only appears in the **Workflows** section of the sidebar.
  </Accordion>

  <Accordion title="Why is the confirm button disabled?">
    Either you have not chosen a destination project, or validation found something that prevents the copy. Check the messages in red in the modal.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Create a project" icon="folder-plus" href="/en/guides/getting-started/create-project">
    Create a project from scratch or clone a whole one with its configuration.
  </Card>

  <Card title="Publish versions" icon="rocket" href="/en/guides/getting-started/publicar-versiones">
    Publish the copied workflow in the destination project.
  </Card>

  <Card title="AI Routing" icon="route" href="/en/guides/getting-started/ai-routing">
    Understand how Jelou decides which workflow handles each message.
  </Card>

  <Card title="Test your workflows" icon="flask" href="/en/guides/getting-started/tester">
    Check the copied flow before publishing it.
  </Card>
</CardGroup>