Connector Outlet

Description

This example demonstrates how to use an outlet connector to control where connections leave a node. Outlet-based patterns are helpful when a node has multiple exit paths, multiple logical outputs, or a layout where edge routing needs a dedicated anchor.

In a real product, outlet connectors help keep graphs readable. Instead of attaching every edge to the same generic point, you can expose a clearer structure for branching, fan-out behavior, and more predictable routing.

This becomes important in workflow builders, automation editors, and low-code tools where users need to understand exactly how work moves from one step to the next.

Example

What this solves

• Cleaner fan-out from a single node.
• More explicit exit points for branching logic.
• Better readability when many edges leave the same step.

If your nodes represent actions, conditions, or service calls with multiple outcomes, outlet connectors are usually a better fit than a single shared port.

Related docs

• Node Outlet Directive
• Connection Component
• Connection Rules
• Limiting Connections Example