Type-aware nodes.
Trigger, decision, action and outcome each have recognizable visual cues. Each node keeps the same underlying spacing, type scale and radius.
Node-based automation / Interface study
This is how an automation product can tell a credible story: a starting event, a decision, two possible routes and a visible outcome. The sample workflow below is illustrative—not a claim about available integrations.
Unlike random node posters, this diagram starts from one input, fans out from two intentional decision ports, and shows distinct outcomes. All connections are defined, and the story survives on mobile without horizontal page scrolling.
Trigger, decision, action and outcome each have recognizable visual cues. Each node keeps the same underlying spacing, type scale and radius.
One input; two outgoing routes. No pile-up of unrelated edges on a single anchor. Branch focus changes without redrawing the entire diagram.
02 / Design before decoration
For product marketing, show one believable solution and let the user understand it before introducing complex diagrams or additional features.
No. The workflow is a self-contained design specimen. It is intentionally marked illustrative to avoid suggesting unsupported integrations or outcomes.
No. It highlights one branch of the flow and updates an accessible text summary. It does not call a backend, contact a service or execute an action.
At narrower widths, the desktop diagram is replaced by an ordered text sequence; the active route summary and controls remain accessible.
Design study / 03