It would help if there was a node for: Visual routing/organization in large workflows (no visible connection line between them) - “Portal Entry” and “Portal Exit” .
My use case:
I build large and complex workflows in n8n for work. I modularize whenever it makes sense, but in many cases splitting into too many sub-workflows makes the overall solution harder to understand and maintain.
To keep the canvas organized, I often use the No Operation node as a “bridge”. Even with this approach, large workflows quickly become visually messy: connections cross over each other, run through other blocks, and the workflow turns into “spaghetti” that’s difficult to read and maintain.
Any resources to support this?
No external resources, just real-world usage from managing large workflows. This concept is similar to “portals” or “jump links” used in other visual editors to reduce edge/line clutter.
Are you willing to work on this?
I’m willing to help with requirements and happy to collaborate in any way that helps move it forward, such as UX suggestions, testing, and feedback.
Proposal
Node: Portal Entry
A node that receives an incoming connection (a “teleport in” point).
It lets me select/define the target Portal Exit by name/ID.
Multiple Portal Entry nodes could point to the same Portal Exit.
It should display a small label under the node showing the destination: “Destination: [Portal Exit name]”.
Node: Portal Exit
A node that represents the “teleport out” destination.
It would have a configurable color/label.
That color would automatically apply to all Portal Entry nodes linked to that Exit, so it’s easy to - identify which Entry goes where.
Expected visual behavior
There would be no visible line drawn between Portal Entry and Portal Exit.
I would only see: normal connections from logic block → Portal Entry and normal connections from Portal Exit → destination block
This would make large workflows much cleaner, avoiding long crossing lines across the canvas.
Benefits
Significantly reduces visual clutter in large workflows
Easier to read and maintain
Less need to use “No Operation” nodes as bridges
Color/label enables fast visual navigation
Thanks for considering this feature request — and thank you to everyone contributing to n8n!
I regularly build large, complex n8n workflows. While I modularize where it makes sense, splitting everything into sub-workflows often makes the overall system harder to understand and maintain.
To keep the canvas readable, I currently use No Operation nodes as visual bridges, but once workflows grow, connections still cross over each other and create a lot of visual noise (“spaghetti”), making the workflow difficult to read and maintain.
I’d like to propose a visual routing concept, similar to portals or jump links used in other visual editors.
Proposed Nodes
Portal Entry
Receives an incoming connection (“teleport in”)
Lets me select a target Portal Exit by name/ID
Multiple Portal Entry nodes can point to the same Portal Exit
Displays a small label: Destination: <Portal Exit name>
Portal Exit
Represents the “teleport out” destination
Has a configurable label and color
That color is automatically applied to all linked Portal Entry nodes, making it easy to see which entries connect where
Expected Visual Behavior
No visible connection line between Portal Entry and Portal Exit
Normal connections only:
Logic → Portal Entry
Portal Exit → next logic
This avoids long lines running across the canvas and crossing other nodes
Benefits
Significantly reduces visual clutter in large workflows
Improves readability and long-term maintainability
Reduces reliance on NoOp nodes as visual bridges
Color + labels enable fast visual navigation
Additional Notes
No external references this request comes purely from real-world experience managing large n8n workflows
This would be a visual/UX feature only, not changing execution behavior
I’m happy to help further with:
UX suggestions
Requirement refinement
Testing and feedback
Thanks for considering this, and thanks to everyone contributing to n8n it’s a powerful platform, and this would make working at scale even better.
The Portal Entry/Exit idea is super nice, and it would solve a real readability problem in large workflows.
It would let you structure the canvas into clear “sections” and jump between them without long connection lines crossing everything, while avoiding splitting into sub workflows just for visual reasons.
So you keep the logic in one place, but you hide the long distance wiring which is exactly what’s missing when a workflow grows.
Summary
It would make large workflows much more readable by visually separating sections without forcing people to create sub workflows only to avoid spaghetti connections.