Node-based automation / Interface study

Less setup.
More flow.

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.

Status routing / illustrative workflow
● Interactive example
Illustrative event-based branching workflowAn event enters a status check. Matching events go to send notice then log result. Other events go to queue review then log result. Use the controls below to highlight either route. TRIGGEREvent receivedStarts the routing check DECISIONCheck statusSeparate output ports MATCHEDSend noticeNotify a recipient UNMATCHEDQueue reviewHold for a person OUTCOMELog resultSuccessful route OUTCOMELog resultReview route YESNO
Workflow in reading order
  1. Trigger: Event received
  2. Decision: Check event status
  3. Matched: Send notice → log result
  4. Unmatched: Queue review → log result

A real workflow has a beginning. A decision. And a result.

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.

SEMANTIC SHAPES / 01

Type-aware nodes.

Trigger, decision, action and outcome each have recognizable visual cues. Each node keeps the same underlying spacing, type scale and radius.

ROUTING CLARITY / 02

Ports with a job.

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

The workflow is the hero. Not a pile of cards.

For product marketing, show one believable solution and let the user understand it before introducing complex diagrams or additional features.

Does this represent an actual connected automation?

No. The workflow is a self-contained design specimen. It is intentionally marked illustrative to avoid suggesting unsupported integrations or outcomes.

Does the branch control run the workflow?

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.

How does the canvas behave on smaller screens?

At narrower widths, the desktop diagram is replaced by an ordered text sequence; the active route summary and controls remain accessible.

Design study / 03

Make the flow
make sense.

Back to library ↗