Skip to main content
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.
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.

​
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

1

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.
2

Select the workflows

Tick the checkbox of every workflow you want to copy. You can pick one or several.
3

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.
4

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.
5

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.
6

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.
7

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.
8

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.

​
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: No workflow is renamed in the process. On a replace, the destination workflow keeps its own name — the very name that paired the two.
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.

​
What gets copied

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:
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.

​
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.
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.

​
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:
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.

​
After cloning

1

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.
2

Review the channels

If Jelou created a channel that did not exist in the destination, review its configuration before going to production.
3

Test the flow

Use the tester in the destination project to check the workflow responds the way you expect.
4

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.

​
Frequently asked questions

No. Cloning only reads the source project. Its workflows, its channels and its configuration stay intact.
No. The Clone to list only shows projects from your own company.
No. The project you have open is not listed as a destination.
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.
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.
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.
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.
No. Clone mode only appears in the Workflows section of the sidebar.
Either you have not chosen a destination project, or validation found something that prevents the copy. Check the messages in red in the modal.

​
Next steps

Create a project

Create a project from scratch or clone a whole one with its configuration.

Publish versions

Publish the copied workflow in the destination project.

AI Routing

Understand how Jelou decides which workflow handles each message.

Test your workflows

Check the copied flow before publishing it.