Issue when sharing workflows: missing connections between nodes

[chrisjjadadma]

I am running into a strange issue when sharing workflows between users on the same n8n server.

When I share a workflow with another user, they can see all the nodes, but the connections between the nodes are not visible. Instead of normal connections, they only see black arrows, and the actual links between nodes appear to be missing. The workflow itself still exists, but visually it is very hard to understand or edit.

Has anyone else experienced this?

Is this a known bug, or is there a specific reason why connections are not rendered correctly for shared workflows?

---

Feature request: sharing folders instead of individual workflows

While I am here, I also wanted to ask about sharing at the folder level.

At the moment, it is only possible to share individual workflows. When multiple workflows are shared this way, they often end up looking disorganized on the receiving user’s side, and it is difficult to understand which workflows belong together.

It would be extremely helpful to be able to share an entire folder with another user, so the structure and grouping of related workflows is preserved. This would make collaboration much clearer, especially for larger projects or systems with many related flows.

Is folder-level sharing something that already exists, is planned, or would this need to be a feature request?

Thanks in advance for any clarification.

[achamm]

"Chrisjjadadma,

I’ve checked the docs and it looks like you’re on to something there - connecting nodes in shared workflows can be tricky! To fix this, try adding an ‘input’ node with type `file` at the top of your workflow and then use it as a connection to link the input node to other nodes. This should allow you to share connections between nodes without seeing any visual clutter. Give it a try!"

```json

{

“type”: “node”,

“name”: “Input File Node”,

“id”: “input-node”,

“config”: {

"type": "file"

}

}

```

```javascript

// …

const inputNode = new InputFileNode();

inputNode.input.path = ‘path/to/input/file’; // replace with your file path

// …

node1.input = { …, link: inputNode } // set the connection to be linked to node1

```

Let me know if this helps!

(This isnt the best json syntax tho)