Transform node into an "end-node" (mock-up included)

The idea is:

Introduce a toggle in the Node Settings (next to “Retry On Fail” and “Execute Once”) that allows users to designate any node as an End Node.Visually, this would:
Remove the “+” (Add Node) connector from the right side of the node.
Add a red/pink lightning bolt icon to the right side of the node, creating a clear visual symmetry with the orange “Trigger” lightning bolt on the left.
Clearly signal that this is a terminal point in the workflow logic.

My use case:

When building large, complex workflows. especially those with multiple If branches, Switch nodes, or Error Triggers, it can be difficult to see at a glance if a branch is intentionally finished or if it’s still “under construction.”
I want to be able to “close” a branch so that:
Collaborators immediately know no further nodes are expected there.
Visual noise is reduced by removing the dangling “+” button on finished terminal nodes.
Audits are faster; I can scan the canvas and see exactly where every logic path ends.

I think it would be beneficial to add this because:

Visual Symmetry: It provides a satisfying “bookend” to the workflow (Orange Bolt = Start, Red Bolt = End).
Improved Scannability: In the current UI, an “end” looks exactly like a “middle” that just hasn’t been connected yet. This feature makes the developer’s intent explicit.
Clean UI: Removing the “+” icon on terminal nodes makes the canvas look much more polished and “finished” for documentation or client hand-overs.
Low Friction: By making it a toggle in the Settings tab (as shown in my mockup), it doesn’t clutter the main parameter view or require a new node type.

Any resources to support this?

I have attached two mockups to demonstrate the implementation:
Visual Comparison: Showing the difference between the current “Original” look and the proposed “End Node” visual.
Settings UI: A mockup of the “End-node” toggle added to the node’s settings panel.

Are you willing to work on this?

Yes, absolutely. I am looking to contribute to the actual implementation of this feature, not just the design. I am ready to help with the frontend logic required for the settings toggle and the CSS/SVG adjustments on the canvas to handle the new terminal state. I’d love to sync with a maintainer on the best way to structure the PR.

Open for feedback about this proposal, lets make it perfect!

إعجاب واحد (1)

Voted. The visual symmetry with the Trigger lightning bolt is a good intuition - it makes the flow easier to read at a glance. One edge case to think about: what happens when a node marked as “end” is in the middle of a partially built workflow? Probably just stop execution there and ignore any downstream connections that still exist? If that behavior is explicit and toggleable (e.g. easy to remove the end-node designation), it could also be useful for debugging - temporarily stopping a workflow at a specific node without deleting the rest.

إعجاب واحد (1)

Appreciate the feed, and yes definitely it could help with debugging as well.