Is it possibile to share an error workflow across projects?
So that I can define one and share it to whatever workflow no matter in which project is.
Currently from current workflow settings I can only select a workflow as error workflow from within the project the current workflow is.
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!
The error workflow can be shared with the other users that have access to different projects as any other workflow, Sharing | n8n Docs. That is, a workflow can be shared with the users, not with projects.
Hi Ihor, thanks for your reply. But whenever I try to share a workflow within a project the popup dialog says " This workflow is owned by the X project which currently has N members with access to this workflow.". According to the doc you shared it seems only the creator of a workflow can share it. I’m sure I created this specific workflow, but it seems the owner now is the project.
I’m running into the same issue as @emac3. We have 3 different project folders with one folder containing utility workflows like our error handling workflows. Unfortunately we’re not able to assign our error handling workflow in projectfolder A to act as the error handling to a workflow in projectfolder b or c as it doesn’t show up in the drop down menu when selecting an error workflow.
exactly as @Erhan_Ozturk said, we’d like to have an utility project from where we can share an error workflow with other workflows in different projects
I see what you mean now. Once a workflow has moved to a project it becomes available to the members of that projects only and cannot be shared across other projects. If the workflow is outside of any project it can be shared with other instance members.
In other words, a project creates an isolated environment and its workflows are automatically shared amongst the project members.
The concept of a project is different from folder (that some other vendors have).
I believe the concept of folders (in addition to projects) is being discussed in n8n too. However, sharing a workflow between many projects is rather a new feature.