How to transfer Workflows between Projects?

[Vadorequest]

The way n8n works is very odd in regards to projects and sharing them.

I’m on a n8n Sustainable Use License + n8n Enterprise License

When I sync my n8n to GitHub, it stores something like this:

{
“id”: “NbvMUmioFDw1qF9P”,
“name”: “p2 - test2”,
“nodes”: ,
“connections”: {},
“settings”: {
“executionOrder”: “v1”
},
“triggerCount”: 0,
“versionId”: “20ba358d-4e8c-447b-bbf9-2b21d98e5963”,
“owner”: {
“type”: “team”,
“teamId”: “pjt9Z3eUcWjvgDSx”,
“teamName”: “p1”
}
}

Changing the owner in the file and using “n8n Pull” doesn’t change the ownership.

I would like to better understand how this works behind the wheel, and why can’t I do something as simple as changing ownership of a workflow?

Also, I would typically not want any workflow to belong to any individual, and force users to create workflows within Projects, if possible.

Here is a video:

• n8n version: 1.44.1
• Database (default: SQLite): No idea
• n8n EXECUTIONS_PROCESS setting (default: own, main): No idea
• Running n8n via (Docker, npm, n8n cloud, desktop app): Cloudron
• Operating system: Ubuntu 22.04

---

P.S: I couldn’t use a “Code Block”, as it displays “500 error” when trying to save.

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Vadorequest]

Edited main post with requested info

[krynble]

hello @Vadorequest

Today we’ll have a release that will allow you to change the ownership of workflows from the UI, the 3 dots menu will now display a “Move” action that would allow you to do so.

But to the point of your question, n8n uses the owner information only on the first pull, so when a workflow is being first created with source control.

Once it already exists, if you change the owner attribute it won’t reflect with n8n because the way we built this is with the idea that the “Move” action would be a quick follow-up, and also because we want to keep ownership as is in case people manually move workflows from a project to another.

So I would suggest you try our new version coming out later today with the Move action and it should resolve this problem.

[acee-thesquad]

Hi! I tried this today (clicking 3 dots menu), but Move option isn’t on there. Any possible reason why?

n8n Version: 1.45.1
Running n8n via n8n cloud
Mac OS

[krynble]

Hi @acee-thesquad it has been released in version 1.46.0 - you should now see it in the workflow list as below.